Subscribe
Accepted Solution

SMSP 6.0 (and 6.1): Error During Backup Raw DB

I'm trying to get an SMSP 6.0 environment to work, but I keep failing with the error "Error During Backup Raw DB". Can anybody help me with this?

The environment (SharePoint 2010) is as follows (all servers Windows Server 2008 R2):

t-app-smsp91: SMSP Media and Manager Server, SMSP 6.0.

t-sql-shp91: SQL Server 2008 R2 (Std Ed.) with SnapDrive 6.3.1R1, SMSQL 5.1P2 and SMSP Member Agent 6.0P1.

t-shp-app91: WFE (application server) with Central Admin, SMSP Member and Control Agent 6.0P1.

t-shp-app93: WFE (application server for Search) with SnapDrive 6.3.1R1, SMSP Member and Control Agent 6.0P1.

t-shp-web91: WFE server with SMSP Member and Control Agent 6.0P1.

The SQL server has 21 LUNs connected to it to support the 238 content databases, mounted under C:\RemoteStorage\T-SQL-SHP91\, and laid out as follows:

Mountpoint

No. of databases

LUN Size (GB)

Volume Size (GB)

ConfigData

2

25

62

ConfigLog

25

62

Data01

12

500

1200

Log01

30

75

Data02

30

100

250

Log02

20

50

Data03

32

100

250

Log03

20

50

Data04

33

100

250

Log04

20

50

Data05

32

100

250

Log05

20

50

Data06

34

100

250

Log06

20

50

Data07

34

100

250

Log07

20

50

Data08

33

100

250

Log08

20

50

MasterDb

(System databases)

3

119

TempDb

1

112 GB

(119 - shares with MasterDb)

SnapInfo

(SnapInfo folders)

10

25

The databases originate from a SharePoint 2007 environment that is in dire need of an update (although this environment, having all databases on one LUN and using SMSP 2.0.1, is still running and creating backups). Data01 contains one very big Content Database (although not in this test environment) as well as the other databases SharePoint requires (Search, MySite, Profile, StateService, SyncDB, PortalDB and Logging), hence the disparity in LUN sizes. We have already renamed one database that used the 'ë' character in the name.

The databases were divided over the 8 LUNs on advice of a NetApp SMSP specialist, who indicated that, due to limitations of the VSS Writer, no more than 35 databases per volume are supported (as of SMSP 6.1).

We started out with SMSP6.1 and SMSQL 5.2P1, but downgraded first to SMSQL 5.1P2 on account of https://communities.netapp.com/message/74416#74416, and then downgraded SMSP to 6.0 as well, so as to have the same configuration we have running in another environment that is working well. In all cases we ran into the following errors.

On the SMSP Server:

Errors: Error During Backup Raw DB: Backup DB Error :SharePoint_Config

Backup service database StateServiceDB exception. (APException: Error During Backup Raw DB: Backup DB Error :StateServiceDB) , [ExceptionType:FromMemberAgentException]

Error During Backup Raw DB: Backup DB Error :WSS_Content_PortalDB

(…)

[Listing all 233 content databases]

Backup service database ProfileDB exception. (APException: Error During Backup Raw DB: Backup DB Error :ProfileDB) , [ExceptionType:FromMemberAgentException]

Backup service database SyncDB exception. (APException: Error During Backup Raw DB: Backup DB Error :SyncDB) , [ExceptionType:FromMemberAgentException]

Backup service database SocialDB exception. (APException: Error During Backup Raw DB: Backup DB Error :SocialDB) , [ExceptionType:FromMemberAgentException]

On the server running the agent used in backup:

In the SMSP Event Log:

Backup service database ProfileDB exception. (APException: Error During Backup Raw DB: Backup DB Error :ProfileDB) , [ExceptionType:FromMemberAgentException]

Backup service database SyncDB exception. (APException: Error During Backup Raw DB: Backup DB Error :SyncDB) , [ExceptionType:FromMemberAgentException]

Backup service database SocialDB exception. (APException: Error During Backup Raw DB: Backup DB Error :SocialDB) , [ExceptionType:FromMemberAgentException]

error during backup raw db: backup db error :sharepoint_config

These errors are repeated for all databases.

On the SQL Server:

In the SMSP Event Log (and SQL Server Report in SMSP Manager):

[Huge command line with all databases iterated in it]

ErrorMessage:

Pipeline State Changed to Failed:

An Unexpected Error occured while executing new-backup.

Details: Cannot invoke this function because the current host does not implement it.

Additionally, in the Job report file in C:\Program Files\NetApp\SnapManager for SharePoint\VaultClient\jobs\FB20121115140540\DB\reports\15-11-2012_14.07.47_new-backup.txt.log

[14:08:14.0387401]: System.Management.Automation.Host.HostException: Cannot invoke this function because the current host does not implement it.

   at System.Management.Automation.Internal.Host.InternalHostRawUserInterface.ThrowNotInteractive()

   at System.Management.Automation.Internal.Host.InternalHostUserInterface.PromptForChoice(String caption, String message, Collection`1 choices, Int32 defaultChoice)

   at System.Management.Automation.MshCommandRuntime.InquireHelper(String inquireMessage, String inquireCaption, Boolean allowYesToAll, Boolean allowNoToAll, Boolean replaceNoWithHalt)

   at System.Management.Automation.MshCommandRuntime.DoShouldContinue(String query, String caption, Boolean supportsToAllOptions, Boolean& yesToAll, Boolean& noToAll)

   at System.Management.Automation.MshCommandRuntime.ShouldContinue(String query, String caption)

   at System.Management.Automation.Cmdlet.ShouldContinue(String query, String caption)

   at SMSQLPSSnapIn.SMSQLBackup.ShouldContinue(String query, String caption)

   at SMSQLPSSnapIn.SMSQLBackup.Process()[System.Management.Automation.Host.HostException]

[14:08:14.4137545]: Failed.

It is possible to make a backup of the databases using SMSQL, so the problem must be in SMSP.

Does anybody have any suggestions? I'm out of ideas.

Re: SMSP 6.0 (and 6.1): Error During Backup Raw DB

We seem to have found the cause of the problem: the administrator installing the Windows side of things installed an out-dated version of SnapDrive, version 6.3.0. The LUNs on the SQL server were created using this version of SnapDrive. When the error was discovered upon install of SMSP, SnapDrive was updated to 6.3.1R1, but subsequent test with SMSP resulted in the Backup Raw DB error. Only when the LUNs were recreated using the updated version of SnapDrive, did the backup work normally.