Solution Details Date - 04/2011
Affected Product & Version - SharePoint APM
Affected Module & Version - N/A
OS Version - N/A
Application Information - N/A
Description:
- The NetVault SharePoint APM user's guide has a step by step procedure on doing a Disaster Recovery when there is a total failure or a migration of the SQL server that is part of a SharePoint farm.
- Instead of following all steps described on the Sharepoint APM user's guide to complete the DR, the customer decides to migrate all databases from the failed or old SQL server to a different SQL Server and creates a SQL Server Alias from the old server to the new SQL Server.
Symptoms:
- The Microsoft SharePoint Application recognizes the SQL Server Alias and continues to work fine.
-The NetVault SharePoint APM fails to complete the backups that were completing fine before the events above.
- As seen on the following sample of the NetVault Binary Logs, the Sharepoint APM is following the SQL Server Alias but it is failing to login to the new SQL server, that now holds the databases that were migrated from the old server.
Information 2011/04/12 09:15:57 146 Data Plugin SHARK1 Cannot open database "SharePoint_AdminContent_f521fde8-6bb2-4fba-a62c-67844080807a" requested by the login. The login failed....
Warning 2011/04/12 09:15:59 146 Data Plugin SHARK1 STSADM failed
The solution is to make sure that all configuration and pre-requisites that were required by the NetVault Sharepoint APM for the older SQL Server also applies to the new SQL Server to where the SQL Server Alias is currently pointing to.
Find below some of the Configurations needed for the new SQL Server , amongst all other configurations required by the NetVault SharePoint APM:
The following pre-requisites are required for small farm SharePoint deployments:
- Domain user account that has the following configuration
- Member of the Administrators group on each server on which SharePoint Setup is run
-Member of the following SQL Server security roles:
- Securityadmin
- Dbcreator
- Directory for Temporary Files which will store the temporary backup
packages created by STSADM. For small farms you must use Universal
Naming Convention (UNC) share paths such as:
\\machine_name\SPbackup
so that the SQL Server database and search components are written to the same location. This directory must be created and all the servers in the SharePoint farm (Including the new SQL Server to where the SQL Server Alias is currently pointing to) must be able to access it.
In addition, verify that Change and Read are granted to the domain account user.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center