1 Reply Latest reply: Feb 21, 2013 2:40 PM by martin.fisher RSS

SnagManager for SQL Cloning Failures

DKJMM2012
Currently Being Moderated

Using VMware 5.0 connected to (2)2040s connected via FCP. SnapManager for SQL 5.2.0.996 and Snapdrive 6.4.2.

 

Trying refresh PR to QA but get the message below.

 

I contacted support for Netapp and VMware but say that it a resignaturing problem.  VMware has a command that will allow for snapshots to be resignatured automatically "# esxcfg-advcfg -s 1 /LVM/EnableResignature". The only problem is that any lun that is identified as a snapshot will be resignature every time and when that happens I will lose access to any VM that is on the snapshot and will have to reinventory.

 

Has anyone run into this issue and found a different solution to freshing PR to QA?

Thanks in Advance

 

[17:06:47.681]  Retrieving ONTAP virtual disks information...
[17:06:53.402] 
[17:06:53.403]  *** RESTORE DATABASE TO ALTERNATE LOCATION

[17:06:53.403]  Querying installed SQL Server instances on [2K5-SQL-PR1]...
[17:06:53.403]  Allocating ODBC environment handle...
[17:06:53.403]  Setting environment attribute...
[17:06:53.403]  Setting SQLBrowseConnect option...
[17:06:53.403]  SQLBrowseConnect...
[17:06:53.405]  Parsing SQLBrowseConnect server string...
[17:06:53.405]  *** SnapManager for SQL Server Report

[17:06:53.405]  Restore Time Stamp: 02-21-2013_17.06.44
[17:06:53.405]  Restore Host: 2K5-SQL-PR1
[17:06:53.405]  Restore as database: new database destination name(s)
[17:06:53.405]  Restore to server: new SQL Server destination(s)
[17:06:53.405]  Restore From Other: No
[17:06:53.405]  Restore Old Host: 2K5-SQL-PR1
[17:06:53.405]  Restore Old Instance: VDISK__E&F
[17:06:53.405]  Restore filegroup: All
[17:06:53.405]  Restore Full Backup Set: 02-20-2013_19.01.31
[17:06:53.405]  Multiple Database Sharing Single Virtual Disk:
[17:06:53.405] 
[17:06:53.405]  Database 1 : apcodirect : 2K5-SQL-PR1
[17:06:53.405]  Database selected for restore: Yes
[17:06:53.405]  Restore to server: 2K5-SQL-QA1
[17:06:53.405]  Restore as database: apcodirect2212013
[17:06:53.405]  Leave database operational: Yes
[17:06:53.405]  Total Logs Applied = 0
[17:06:53.405] 
[17:06:53.405]  Database 2 : apcoforms : 2K5-SQL-PR1
[17:06:53.405]  Database selected for restore: No
[17:06:53.405] 
[17:06:53.405]  Database 3 : Applog : 2K5-SQL-PR1
[17:06:53.405]  Database selected for restore: No
[17:06:53.405] 
[17:06:53.405]  Database 4 : DealersOnline : 2K5-SQL-PR1
[17:06:53.405]  Database selected for restore: No
[17:06:53.405] 
[17:06:53.405]  Database 5 : DNN_ECRewards : 2K5-SQL-PR1
[17:06:53.405]  Database selected for restore: No
[17:06:53.405] 
[17:06:53.405]  Database 6 : DotNetNuke : 2K5-SQL-PR1
[17:06:53.405]  Database selected for restore: No
[17:06:53.405] 
[17:06:53.405]  Database 7 : ECRewards : 2K5-SQL-PR1
[17:06:53.405]  Database selected for restore: No
[17:06:53.405] 
[17:06:53.405]  Database 8 : LicenseOld : 2K5-SQL-PR1
[17:06:53.405]  Database selected for restore: No
[17:06:53.405] 
[17:06:53.405]  Database 9 : licensesDBPR : 2K5-SQL-PR1
[17:06:53.405]  Database selected for restore: No
[17:06:53.405] 
[17:06:53.405]  Database 10 : MenuVantage : 2K5-SQL-PR1
[17:06:53.406]  Database selected for restore: No
[17:06:53.406] 
[17:06:53.406]  Database 11 : OnlineReconciliation : 2K5-SQL-PR1
[17:06:53.406]  Database selected for restore: No
[17:06:53.406] 
[17:06:53.406]  Database 12 : Rates : 2K5-SQL-PR1
[17:06:53.406]  Database selected for restore: No
[17:06:53.406] 
[17:06:53.406]  Database 13 : ratingservices : 2K5-SQL-PR1
[17:06:53.406]  Database selected for restore: No
[17:06:53.406] 
[17:06:53.406]  Database 14 : SELLU_DATA : 2K5-SQL-PR1
[17:06:53.406]  Database selected for restore: No
[17:06:53.406] 
[17:06:53.406]  Database 15 : svcMonitor : 2K5-SQL-PR1
[17:06:53.406]  Database selected for restore: No
[17:06:53.406] 
[17:06:53.406]  Stream-based backup restore: No
[17:06:53.406]  Keep Replication: No
[17:06:53.406]  Run DBCC CHECKDB: No
[17:06:53.406]  Leave database attached after DBCC: No
[17:06:53.406]  Restore to alternate location using writable snapshot - Database clone: Yes
[17:06:53.406]  Clone on available SnapMirror destination volume: No
[17:06:53.406]  Change clone database paths based on new database name: No
[17:06:53.406]  Mount Point Directory: C:\Program Files\NetApp\SnapManager for SQL Server\SnapMgrMountPoint
[17:06:53.406]  Create database clone: Yes
[17:06:53.406]  Restore database(s) even if database(s) are online: No
[17:06:53.406]  Recover database without restoring: No
[17:06:53.406]  Create transaction log backup before restore: N/A


[17:06:53.406]  WARNING: SnapManager does not create transaction log backup before the restore for "restore to alternate location using writable snapshot".
[17:06:53.419]  Create a transaction log backup before this operation if you want to restore a database to its most recent state.

[17:06:53.419]  Abort restore if transaction log backup before restore unsuccessful: N/A
[17:06:53.419]  Run Command before the current operation: No
[17:06:53.419]  Run Command after the current operation: No
[17:06:53.419] 
[17:06:53.419]  *** PREPARING RESTORE

[17:06:53.419]  Verifying the selection of backup data set...

[17:07:30.674]  *** RETRIEVE SNAPMANAGER BACKUP INFORMATION

[17:07:30.716]  Querying backup database set SnapInfo file path...
[17:07:42.465]  Get log snapshot list from virtual disk [Y]: ...
[17:07:52.761]  Initializing SnapManager server on remote machine [2K5-SQL-QA1]...
[17:07:52.763]  Remote server [2K5-SQL-QA1] is connected successfully.

[17:07:52.791]  *** SNAPMANAGER MOUNT BY RESTORE (CLONE) JOB ENDED AT: [02-21-2013 16.50.11]
Unknown Error, Error Code: 0xc0041057
*** SnapManager for SQL Server Report

[17:10:21.331]  Restore Time Stamp: 02-21-2013_17.06.44
Restore Host: 2K5-SQL-PR1
Restore as database: new database destination name(s)
Restore to server: new SQL Server destination(s)
Restore From Other: No
Restore Old Host: 2K5-SQL-PR1
Restore Old Instance: VDISK__E&F
Restore filegroup: All
Restore Full Backup Set: 02-20-2013_19.01.31
Multiple Database Sharing Single Virtual Disk:

Database 1 : apcodirect : 2K5-SQL-PR1
Database selected for restore: Yes
Restore to server: 2K5-SQL-QA1
Restore as database: apcodirect2212013
Leave database operational: Yes
Total Logs Applied = 0

Database 2 : apcoforms : 2K5-SQL-PR1
Database selected for restore: No

Database 3 : Applog : 2K5-SQL-PR1
Database selected for restore: No

Database 4 : DealersOnline : 2K5-SQL-PR1
Database selected for restore: No

Database 5 : DNN_ECRewards : 2K5-SQL-PR1
Database selected for restore: No

Database 6 : DotNetNuke : 2K5-SQL-PR1
Database selected for restore: No

Database 7 : ECRewards : 2K5-SQL-PR1
Database selected for restore: No

Database 8 : LicenseOld : 2K5-SQL-PR1
Database selected for restore: No

Database 9 : licensesDBPR : 2K5-SQL-PR1
Database selected for restore: No

Database 10 : MenuVantage : 2K5-SQL-PR1
Database selected for restore: No

Database 11 : OnlineReconciliation : 2K5-SQL-PR1
Database selected for restore: No

Database 12 : Rates : 2K5-SQL-PR1
Database selected for restore: No

Database 13 : ratingservices : 2K5-SQL-PR1
Database selected for restore: No

Database 14 : SELLU_DATA : 2K5-SQL-PR1
Database selected for restore: No

Database 15 : svcMonitor : 2K5-SQL-PR1
Database selected for restore: No

Stream-based backup restore: No
Keep Replication: No
Run DBCC CHECKDB: No
Leave database attached after DBCC: No
Restore to alternate location using writable snapshot - Database clone: Yes
Clone on available SnapMirror destination volume: No
Change clone database paths based on new database name: No
Mount Point Directory: C:\Program Files\NetApp\SnapManager for SQL Server\SnapMgrMountPoint
Create database clone: Yes
Restore database(s) even if database(s) are online: No
Recover database without restoring: No
Create transaction log backup before restore: N/A

WARNING: SnapManager does not create transaction log backup before the restore for "restore to alternate location using writable snapshot".
Create a transaction log backup before this operation if you want to restore a database to its most recent state.

Abort restore if transaction log backup before restore unsuccessful: N/A
Run Command before the current operation: No
Run Command after the current operation: No

Validating SQL Server to be restored to...
Querying installed SQL Server instances on [2K5-SQL-QA1]...
Allocating ODBC environment handle...
Setting environment attribute...
Setting SQLBrowseConnect option...
SQLBrowseConnect...
Parsing SQLBrowseConnect server string...

Connecting to SQL Server instance [2K5-SQL-QA1] for restore SQL Server version checking...
Mounting SnapInfo Drive...
Mounting Snapshot [sqlinfo__2k5-sql-pr1_02-20-2013_19.01.31__daily] for LUN [Y] of Computer [2K5-SQL-PR1]
SnapManager will mount the snapshot [sqlinfo__2k5-sql-pr1_02-20-2013_19.01.31__daily] using available drive letter; otherwise, it will use directory C:\Program Files\NetApp\SnapManager for SQL Server\SnapMgrMountPoint if no drive letter is available.
WARNING: Unable to get available drive letter
[17:10:21.810]  Using default mount point directory [C:\Program Files\NetApp\SnapManager for SQL Server\SnapMgrMountPoint\MPDisk001]
[17:12:27.671]  [SnapDrive Error]: Failed to mount backup sqlinfo__2k5-sql-pr1_02-20-2013_19.01.31__daily. Reasons Failed to mount disk (Disk Id <6000C294-aee3-3789-c0d0-724b01b05b67>) in Backup <bc5a5e5a-31a6-4d06-9807-7c8bb753d466>. Server Error: <Mounting the backup sqlinfo__2k5-sql-pr1_02-20-2013_19.01.31__daily failed with following reason: One or more mount requests did not succeed. Please check vSphere Client for any error messages.>. .

(SnapDrive Error Code: 0xc0041057)

More Like This

  • Retrieving data ...