We have an SAP server who's running SnapManager for Oracle with the following volumes and qtrees mounted via NFS:
linuxsap:~ # snapdrive storage show -all
NFS device: netapp2:/vol/DEV_ORA_SAP/DEV_ORACLE mount point: /oracle (non-persistent)
NFS device: netapp2:/vol/DEV_SAPDATA mount point: /sapdata (non-persistent)
NFS device: netapp2:/vol/DEV_ORA_SAP/DEV_ORIGLOGA mount point: /origlogA (non-persistent)
NFS device: netapp2:/vol/DEV_ORA_SAP/DEV_ORIGLOGB mount point: /origlogB (non-persistent)
NFS device: netapp2:/vol/DEV_ORA_SAP/DEV_USRSAP mount point: /sap (non-persistent)
NFS device: netapp2:/vol/DEV_MIRRLOG/DEV_MIRRLOGA mount point: /mirrlogA (non-persistent)
NFS device: netapp2:/vol/DEV_MIRRLOG/DEV_MIRRLOGB mount point: /mirrlogB (non-persistent)
NFS device: netapp2:/vol/DEV_ARCHLOG mount point: /oraarch (non-persistent)
SnapManager for SAP is configured for using Protection Manager to do a SnapVault update after the backup (snapshot) of SnapManager for SAP:
SnapVault relations:
netapp2> snapvault status
Snapvault is ON.
Source Destination State Lag Status
netapp2:/vol/DEV_ARCHLOG/- netapp1:/vol/VAULT_DEV_ARCHLOG/SV_DEV_ARCHLOG Source 28:48:56 Idle
netapp2:/vol/DEV_MIRRLOG/DEV_MIRRLOGA netapp1:/vol/VAULT_DEV/DEV_MIRRLOGA Source 31:19:08 Idle
netapp2:/vol/DEV_MIRRLOG/DEV_MIRRLOGB netapp1:/vol/VAULT_DEV/DEV_MIRRLOGB Source 28:49:17 Idle
netapp2:/vol/DEV_ORA_SAP/DEV_ORACLE netapp1:/vol/VAULT_DEV/DEV_ORACLE Source 31:19:05 Idle
netapp2:/vol/DEV_ORA_SAP/DEV_ORIGLOGA netapp1:/vol/VAULT_DEV/DEV_ORIGLOGA Source 28:49:17 Idle
netapp2:/vol/DEV_ORA_SAP/DEV_ORIGLOGB netapp1:/vol/VAULT_DEV/DEV_ORIGLOGB Source 31:19:06 Idle
netapp2:/vol/DEV_ORA_SAP/DEV_USRSAP netapp1:/vol/VAULT_DEV/DEV_USRSAP Source 31:19:08 Idle
netapp2:/vol/DEV_SAPDATA/- netapp1:/vol/VAULT_DEV/smsap_linuxsap_dev_netapp2_DEV_SAPDATA Source 28:49:17 Idle
Protection Manager config:
C:\Users\Administrator>dfpm backup list smsap_linuxsap_dev
Backup Id Backup Version Retention Type Retention Duration (in seconds) Node Name Description Properties(Name=Value)
--------- --------------------- -------------- --------------------------------- -------------------- ----------------------------------- -------------------------
86261 19 Nov 2012 16:45:30 daily 604800 Backup D_A_20121119164414CET
86245 19 Nov 2012 16:45:30 daily 604800 Primary data D_A_20121119164414CET
86243 19 Nov 2012 16:36:52 daily 604800 Backup D_A_20121119163535CET
86241 19 Nov 2012 16:36:52 daily 604800 Primary data D_A_20121119163535CET
86209 19 Nov 2012 15:05:54 daily 604800 Backup D_A_20121119150439CET
86207 19 Nov 2012 15:05:54 daily 604800 Primary data D_A_20121119150439CET
86164 19 Nov 2012 13:38:48 daily 604800 Primary data D_A_20121119133728CET
86155 19 Nov 2012 13:27:18 daily 604800 Primary data D_A_20121119132607CET
86120 19 Nov 2012 12:03:54 daily 604800 Primary data D_A_20121119120239CET
86093 19 Nov 2012 11:05:35 daily 604800 Primary data D_A_20121119110424CET
86065 19 Nov 2012 09:59:04 daily 604800 Primary data D_A_20121119095749CET
84599 16 Nov 2012 22:02:03 daily 604800 Primary data D_A_20121116220036CET
82811 13 Nov 2012 22:02:13 daily 604800 Primary data D_A_20121113220040CET
C:\Users\Administrator>dfpm dataset list smsap_linuxsap_dev
Id Name Protection Policy Provisioning Policy Application Policy Storage Service
---------- --------------------------- --------------------------- ------------------- --------------------------- ---------------
4605 smsap_linuxsap_dev SMSAP DEV Back up
C:\Users\Administrator>dfpm dataset status smsap_linuxsap_dev
Id Name Resource Status Conformance Status Protection Status Space DR Status
---------- --------------------------- ----------------- -------------------- -------------------- ---------- ---------------
4605 smsap_linuxsap_dev normal conformant protected No Provisioning Policy
C:\Users\Administrator>dfpm dataset list -R smsap_linuxsap_dev
Id Name Protection Policy Provisioning Policy Relationship Id State Status Hours Source Destination
---------- --------------------------- --------------------------- ------------------- --------------- ------------ ------- ----- ---------------------------- ----------------------------
4605 smsap_linuxsap_dev SMSAP DEV Back up 5030 snapvaulted idle 31.6 netapp2:/DEV_MIRRLOG/DEV_MIRRLOGA netapp1:/VAULT_DEV/DEV_MIRRLOGA
4605 smsap_linuxsap_dev SMSAP DEV Back up 5032 snapvaulted idle 31.6 netapp2:/DEV_ORA_SAP/DEV_ORIGLOGB netapp1:/VAULT_DEV/DEV_ORIGLOGB
4605 smsap_linuxsap_dev SMSAP DEV Back up 5034 snapvaulted idle 29.1 netapp2:/DEV_ORA_SAP/DEV_ORIGLOGA netapp1:/VAULT_DEV/DEV_ORIGLOGA
4605 smsap_linuxsap_dev SMSAP DEV Back up 5036 snapvaulted idle 29.1 netapp2:/DEV_MIRRLOG/DEV_MIRRLOGB netapp1:/VAULT_DEV/DEV_MIRRLOGB
4605 smsap_linuxsap_dev SMSAP DEV Back up 5040 snapvaulted idle 31.6 netapp2:/DEV_ORA_SAP/DEV_ORACLE netapp1:/VAULT_DEV/DEV_ORACLE
4605 smsap_linuxsap_dev SMSAP DEV Back up 5041 snapvaulted idle 29.1 netapp2:/DEV_SAPDATA/- netapp1:/VAULT_DEV/smsap_linuxsap_dev_netapp2_DEV_SAPDATA
4605 smsap_linuxsap_dev SMSAP DEV Back up 5042 snapvaulted idle 31.6 netapp2:/DEV_ORA_SAP/DEV_USRSAP netapp1:/VAULT_DEV/DEV_USRSAP
The problem is that Protection Manager is only updating 1 of the qtrees of a volume. Like you can see in the DEV_ORA_SAP volume, only 1 relation is updated.
We have already created the relationship manually and automatically with Protection Manager but the result is still the same.
We cannot use a Volume relationship as we use SnapManager for SAP to create the backups. SMSAP is configured to protect the backups. As we create only 3 volume relations, SMSAP will not run as he is not finding the relationships for the qtrees.
What do we need to do to have a successful SnapVault update after a backup with SMSAP.
