Subscribe
Accepted Solution

Snapvault relationships not updating in either 4.0 or version 4.1

[ Edited ]

Hi All,

I use SC 4.0p1 to backup a DB2 DB.  We have the SC jobs configured to protect the database through the use of  to OnCommand (latest version).  I am attempting to test with a server cloned from production that upgrading from 4.0 to 4.1 will not introduce any problems.  The OnCommand dataset is conffigured to mirror then vault the data.  Since standing up this test server (identical to production), the mirrors update, but the vaults don't update correctly.  Each vault relationship is configured like this:

ATLFAS02:/vol/snap_q/-                                                                        ATLFAS02:/vol/snap_q_vault/default                                                                 Snapvaulted    00:03:30   Idle

ATLFAS02:/vol/snap_q/q0                                                                       ATLFAS02:/vol/snap_q_vault/q0                                                                      Snapvaulted    71:47:43   Idle

In the log of the production server that is updating the vaults properly, I see this:

[2014-08-21 19:00:59,398] INFO: STORAGE-03045: Protection Manager dataset modify successful for dataset [snapcreator_OLADB01]

########## Running Protection Manager Backup Version Create for dataset snapcreator_OLADB01 ##########

[2014-08-21 19:01:00,225] INFO: STORAGE-05004: Creating Protection Manager driven backup of dataset [snapcreator_OLADB01] on storage controller [CDCFAS02].

[2014-08-21 19:01:00,225] INFO: Creating Protection Manager Backup Version for volume oladb01_q dataset snapcreator_OLADB01

[2014-08-21 19:01:00,225] INFO: STORAGE-05015: Added member [CDCFAS02:/oladb01_q/-] of dataset [snapcreator_OLADB01] to Protection Manager backup version.

[2014-08-21 19:01:00,225] INFO: STORAGE-05015: Added member [CDCFAS02:/oladb01_q/q0] of dataset [snapcreator_OLADB01] to Protection Manager backup version.

[2014-08-21 19:01:00,225] INFO: Creating Protection Manager Backup Version for volume oladb01_r dataset snapcreator_OLADB01

[2014-08-21 19:01:00,225] INFO: STORAGE-05015: Added member [CDCFAS02:/oladb01_r/-] of dataset [snapcreator_OLADB01] to Protection Manager backup version.

[2014-08-21 19:01:00,225] INFO: STORAGE-05015: Added member [CDCFAS02:/oladb01_r/q0] of dataset [snapcreator_OLADB01] to Protection Manager backup version.

[2014-08-21 19:01:00,225] INFO: Creating Protection Manager Backup Version for volume oladb01_s dataset snapcreator_OLADB01

[2014-08-21 19:01:00,225] INFO: STORAGE-05015: Added member [CDCFAS02:/oladb01_s/-] of dataset [snapcreator_OLADB01] to Protection Manager backup version.

[2014-08-21 19:01:00,225] INFO: STORAGE-05015: Added member [CDCFAS02:/oladb01_s/q0] of dataset [snapcreator_OLADB01] to Protection Manager backup version.

[2014-08-21 19:01:00,225] INFO: Creating Protection Manager Backup Version for volume oladb01_t dataset snapcreator_OLADB01

[2014-08-21 19:01:00,225] INFO: STORAGE-05015: Added member [CDCFAS02:/oladb01_t/-] of dataset [snapcreator_OLADB01] to Protection Manager backup version.

[2014-08-21 19:01:00,225] INFO: STORAGE-05015: Added member [CDCFAS02:/oladb01_t/q0] of dataset [snapcreator_OLADB01] to Protection Manager backup version.

Notice that SC is adding protection for the - and q0 relationships.

On the test server that I have set up, if I run a SC job, I see this:

########## Running Protection Manager Backup Version Create for dataset snapcreator_SNAP ##########

[2014-08-21 16:41:43,678] INFO: STORAGE-05004: Creating Protection Manager driven backup of dataset [snapcreator_SNAP] on storage controller [CDCFAS11].

[2014-08-21 16:41:43,678] INFO: Creating Protection Manager Backup Version for volume snap_q dataset snapcreator_SNAP

[2014-08-21 16:41:43,678] INFO: STORAGE-05015: Added member [CDCFAS11:/snap_q/-] of dataset [snapcreator_SNAP] to Protection Manager backup version.

[2014-08-21 16:41:43,678] INFO: Creating Protection Manager Backup Version for volume snap_r dataset snapcreator_SNAP

[2014-08-21 16:41:43,678] INFO: STORAGE-05015: Added member [CDCFAS11:/snap_r/-] of dataset [snapcreator_SNAP] to Protection Manager backup version.

[2014-08-21 16:41:43,678] INFO: Creating Protection Manager Backup Version for volume snap_s dataset snapcreator_SNAP

[2014-08-21 16:41:43,678] INFO: STORAGE-05015: Added member [CDCFAS11:/snap_s/-] of dataset [snapcreator_SNAP] to Protection Manager backup version.

[2014-08-21 16:41:43,678] INFO: Creating Protection Manager Backup Version for volume snap_t dataset snapcreator_SNAP

[2014-08-21 16:41:43,678] INFO: STORAGE-05015: Added member [CDCFAS11:/snap_t/-] of dataset [snapcreator_SNAP] to Protection Manager backup version.

As you can see, it is only adding the - relationships.  As a result, the q0 vaults are not updating.  Not realizing that it was not working properly, I upgraded my test SC server to 4.1P2 and still have the identical problem.

Any thoughts on why this is not working correctly?

Thanks

Michael

Re: Snapvault relationships not updating in either 4.0 or version 4.1

Never mind.  Just ignore me.  It's Friday.  It's always the little details that get you.  I double checked my dataset and noticed a subtle mistake.  I corrected it and all seems fine.  I think I've successfully validated that the 4.0 to 4.1 upgrade doesn't break anything for me.  Thanks!