SMSQL 5.0R1 Clone from Archived Backup fails with Error Code: 0xc004095a Unable to find remote backup ID ('0') for mounting LUN in snapshot copy on secondary.

[mrettl]

Community,

I am using  SMSQL 5.0R1 to Backup my SQL2007 Server and DFM 4.0 with Protection  Manager.

I  have created a Database and let create SMSQL Dataset with a simple  Backup Policy - SnapVault to a NearStore Filer (everything is licensed  correctly, including SMSQL and FlexClone License on the NearStore).  ONTAP Version is 7.3.2P2 on all Filers.

In PM I have added a ressource pool  to the Dataset and PM initiates the three SnapVault relationships (DB,  Log and SnapInfo). Everything is running fine so far, my Dataset is  comformant.

Backing  up Databases also runs smoothly including the update of the SnapVault  relation.

BUT  when I use the "Clone Wizard" in SMSQL to create a clone from an  ARCHIVED BACKUP, SMSQL aborts with the error:

Connecting to SQL Server [DSQL02]  for restore SQL Server version checking...
Getting database backup  information from SnapInfo file...
Mounting LUN in snapshot copy from  data set...
Getting remote backup ID for dataset  [SnapMgr_SQLServer_DSQL02] with Backup Version [1271286452]...
Backup Version: 1271286452
Backup  Description: 04-15-2010_01.07.11
Backup Fully Propagated: True
Backup  Status: Success
Unable to find remote backup, aborting...

Error Code:  0xc004095a
Unable to find remote backup ID ('0') for mounting LUN in  snapshot copy on secondary.

Now, I was investigating the backups  and snapshots with SDCLI:

C:\>sdcli  dataset backup_list -dn SnapMgr_SQLServer_DSQL02
Backup  Information for dataset "SnapMgr_SQLServer_DSQL02"
BackupID : 14354
Backup  Version: 1271286557
Node Name :Backup
Node Id :2
Backup  Retention type: daily
BackupID : 14352
Backup Version: 1271286557
Node  Name: Primary data
Node Id :1
Backup Retention type: unlimited
BackupID : 14353
Backup Version:  1271286452
Node Name :Backup
Node Id :2
Backup Retention type:  daily
BackupID : 14351
Backup Version: 1271286452
Node  Name: Primary data
Node Id :1
Backup Retention type: unlimited
The  operation completed successfully.

C:\>sdcli dataset get_backup_location -dn  SnapMgr_SQLServer_DSQL02 -i 14352
BackupId:14352
Primary Snapshot Copy Name:sqlinfo__dsql02_04-15-2010_01.07.11__daily
Primary Qtree Name:sissi:/dsql02_sinfo/sinfo
Secondary Snapshot  Copy Name:
Secondary Qtree Name:

C:\>sdcli dataset get_backup_location -dn  SnapMgr_SQLServer_DSQL02 -i 14353
BackupId:14353
Primary Snapshot Copy Name:sqlsnap__dsql02_04-15-2010_01.07.11__daily
Primary Qtree Name:sissi:/dsql02_log2/log2
Secondary Snapshot Copy  Name:2010-04-14 23:09:24  daily_krusty_SnapMgr_SQLServer_DSQL02_backup_5.-.log2
Secondary  Qtree Name:krusty:/SnapMgr_SQLServer_DSQL02_backup_5/log2

BackupId:14353
Primary  Snapshot Copy Name:sqlsnap__dsql02_04-15-2010_01.07.11__daily
Primary Qtree Name:franz:/dsql02_db2/db2
Secondary Snapshot Copy  Name:2010-04-14 23:09:22  daily_krusty_SnapMgr_SQLServer_DSQL02_backup_3.-.db2
Secondary Qtree  Name:krusty:/SnapMgr_SQLServer_DSQL02_backup_3/db2
The operation  completed successfully.

Has anyone seen this behaviour before? There are  some BURTs on this error but they say that the operation fails if the  baseline snapshot is missing or the LUN on the source is unavailable.  But this is not the fact in my case.

Kind regards,

Matthias

[stephen_swanstrom]

Matthias,

I was wondering if you were ever able to come to a resolution with this issue.  I am experiencing a similar issue when trying to restore an archived snapshot back to production.  I get a very similar message from SMSQL but am able to obtain the information from sdcli without any issues.  Furthermore, I was able to complete this restore a week ago and now it's failing.

Thanks,

Stephen

[qzhang]

but am able to obtain the information from sdcli without any issues

What information you are able to obtain without any issue?

Thanks,

-Qing

[stephen_swanstrom]

The issue is very similar to what Matthias described in the first post.  This is what I get from SMSQL:

[11:57:16.142]  Restoring LUN from archived backup...

[11:57:16.159]  Getting remote backup ID for dataset [SnapMgr_SQLServer_WCOSTSQL1] with Backup Version [1276720113]...

[11:57:31.294]  Backup Version: 1276720113

[11:57:31.295]  Backup Description: 06-16-2010_14.28.10

[11:57:31.296]  Backup Fully Propagated: True

[11:57:31.297]  Backup Status: Success

[11:57:31.781]  Unable to find remote backup, aborting...

[11:57:31.790]  Error Code: 0xc004095a  Unable to find remote backup ID ('0') for mounting LUN in snapshot copy on secondary.

But from sdlci:

C:\Windows\system32>sdcli dataset backup_list -dn SnapMgr_SQLServer_WCOSTSQL1

Backup Information for dataset "SnapMgr_SQLServer_WCOSTSQL1"

BackupID : 459

Backup Version: 1276720191

Node Name :Primary data

Node Id :1

Backup Retention type: unlimited

BackupID : 461

Backup Version: 1276720191

Node Name :Backup

Node Id :2

Backup Retention type: unlimited

C:\Windows\system32>sdcli dataset get_backup_location -dn SnapMgr_SQLServer_WCOSTSQL1 -i 461

BackupId:461

Primary Snapshot Copy Name:sqlinfo__wcostsql1_06-16-2010_14.28.10

Primary Qtree Name:csnafa03:/wcostsql1_mssqlserver_snapinfo/snapinfo

Secondary Snapshot Copy Name:dfpm_wlvdfm1.5593.1276720374

Secondary Qtree Name:csnans05:/dfpm_SnapMgr_SQLServer_WCOSTSQL1_SV_1272574704_3252/snapinfo

The operation completed successfully.

[qzhang]

So sdcli dataset backup_list did not list the backup you want to use for the clone. Because of that, the error would be expected. The remote backup may already expire in DFM.

Thanks,

-Qing

[lagenevoise]

I solved a close issue with the 5.1P1

But in my case The isuue, with the snapshot created before the update, is not fixed. 

Regards

[abhisek]

Are you still getting the same issue after P1 updation ?

Regards,

Abhishek

[lagenevoise]

Dear Abhishek

Yes with P1 the bug was fixed.

Regards

[abhisek]

So you are no longer seeing the issue.

Thanks,

Abhishek