Subscribe

SnapCreator not protecting (snapvault) relationship in OnCommand Dataset

[ Edited ]

Hi All,

Ok SC experts, my problems with this server backup job has been very time consuming to resolve and I could really use some help figuring out why it's not working properly.  I have version SC4.0p1 set to work with OnCommand 5.2R1 to protect a dataset which is a mirror to vault.  There are 4 mirror relationships to mirror 4 server luns: K, L, M, N.  Then it vaults 8 relationships: k/-, k/q0, l/-,l/q0, etc.  When I look in the logs of SC, I see it adding for protection all relationships except cdcola2_l/q0.  As a result, that particular relationship does not update.  This process have been working for months and there has only been 1 change.

Beginning last week, I noticed that the L mirror / vault relationships on the controllers weren't setup correctly anymore.  I have no clue how they broke and could not figure out how to resolve it.  So, as an easy fix (I thought), I took the l mirror and vaults (l/- and l/q0) out of the dataset in OnCommand.  I did not make any changes to the server config in SC.  I logged onto the controller and deleted the vault relationships.  At that point, the mirror was fine, so didn't have to destroy it.  I then recreated the vault relationships identical to how they were prior to the beginning of this problem.  I waited hours for OnCommand to discover the newly created vault relationships as external.  It never did and had to work with support for a few days getting to get the right person who had the knowledge to resolve it.  Finally this Monday afternoon, support was able to get OnCommand to import the relationships and I imported them back into the dataset.  I ran a backup and thought everything was fine until I realized that the q0 still had a lag on it today.

Here is a snippet of my SC log to show you what I mean what SC is not doing:

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

[2014-08-05 18:01:52,361] INFO: STORAGE-05004: Creating Protection Manager driven backup of dataset [snapcreator_CDCOLA2] on storage controller [CDCFAS02].

[2014-08-05 18:01:52,361] INFO: Creating Protection Manager Backup Version for volume cdcola2_k dataset snapcreator_CDCOLA2

[2014-08-05 18:01:52,361] INFO: STORAGE-05015: Added member [CDCFAS02:/cdcola2_k/-] of dataset [snapcreator_CDCOLA2] to Protection Manager backup version.

[2014-08-05 18:01:52,361] INFO: STORAGE-05015: Added member [CDCFAS02:/cdcola2_k/q0] of dataset [snapcreator_CDCOLA2] to Protection Manager backup version.

[2014-08-05 18:01:52,361] INFO: Creating Protection Manager Backup Version for volume cdcola2_l dataset snapcreator_CDCOLA2

[2014-08-05 18:01:52,361] INFO: STORAGE-05015: Added member [CDCFAS02:/cdcola2_l/-] of dataset [snapcreator_CDCOLA2] to Protection Manager backup version.

[2014-08-05 18:01:52,361] INFO: Creating Protection Manager Backup Version for volume cdcola2_m dataset snapcreator_CDCOLA2

[2014-08-05 18:01:52,361] INFO: STORAGE-05015: Added member [CDCFAS02:/cdcola2_m/-] of dataset [snapcreator_CDCOLA2] to Protection Manager backup version.

[2014-08-05 18:01:52,361] INFO: STORAGE-05015: Added member [CDCFAS02:/cdcola2_m/q0] of dataset [snapcreator_CDCOLA2] to Protection Manager backup version.

[2014-08-05 18:01:52,361] INFO: Creating Protection Manager Backup Version for volume cdcola2_n dataset snapcreator_CDCOLA2

[2014-08-05 18:01:52,361] INFO: STORAGE-05015: Added member [CDCFAS02:/cdcola2_n/-] of dataset [snapcreator_CDCOLA2] to Protection Manager backup version.

[2014-08-05 18:01:52,361] INFO: STORAGE-05015: Added member [CDCFAS02:/cdcola2_n/q0] of dataset [snapcreator_CDCOLA2] to Protection Manager backup version.

For every drive except L, you see the - and the q0.

I'm attacking the full log for analysis, but I don't see any errors in it.  I'd greatly appreciate it if someone is able to help today because I need to ensure this server is backing up properly.

Thanks

Michael

Re: SnapCreator not protecting (snapvault) relationship in OnCommand Dataset

I cannot figure out how to add the log file, so here is the contents of it:

########## Detecting Data ONTAP mode for CDCFAS02 ##########

[2014-08-05 18:00:04,266] INFO: STORAGE-03031: System version details of [CDCFAS02].

[2014-08-05 18:00:04,266] DEBUG: <system-get-version/>

[2014-08-05 18:00:04,266] DEBUG: <system-get-ontapi-version/>

[2014-08-05 18:00:04,266] INFO: STORAGE-03032: System version details of [CDCFAS02] finished successfully.

########## Agent validation ##########

[2014-08-05 18:00:04,500] INFO: Agent validation completed successfuly for agent cdcola2:9090

########## Plugin validation ##########

[2014-08-05 18:00:04,515] INFO: Plugin validation completed successfuly for plugin db2

[2014-08-05 18:00:04,515] INFO: Removing log CDCOLA2.debug.20140429180003.log

[2014-08-05 18:00:04,515] INFO: Removing log CDCOLA2.out.20140429180003.log

########## PRE APPLICATION QUIESCE COMMANDS ##########

[2014-08-05 18:00:04,515] INFO: Pre application quiesce commands are not defined

########## PRE APPLICATION QUIESCE COMMANDS FINISHED SUCCESSFULLY  ##########

[2014-08-05 18:00:04,515] INFO: Application auto discovery is not enabled skipping .

[2014-08-05 18:00:04,531] INFO: Validate volume is not enabled skipping validate volume task.

########## Application Quiesce ##########

[2014-08-05 18:00:25,903] DEBUG: [cdcola2:9090 (4.0.0.1)] db2::setENV finished successfully

[2014-08-05 18:00:25,903] INFO: [cdcola2:9090 (4.0.0.1)] Quiescing databases

[2014-08-05 18:00:25,903] INFO: [cdcola2:9090 (4.0.0.1)] Quiescing database copsola2

[2014-08-05 18:00:25,903] DEBUG: [cdcola2:9090 (4.0.0.1)] Executing SQL sequence:

connect to copsola2;

set write suspend for database;

connect reset;

[2014-08-05 18:00:25,903] DEBUG: [cdcola2:9090 (4.0.0.1)] Q29tbWFuZCBbIkM6XFNRTExJQlxCSU5cZGIyY21kLmV4ZSIgLWMgLXcgLWkgIkM6XFNRTExJQlxCSU5cZGIyLmV4ZSIgLXR2ZiBDOlxET0NVTUV+MVxVU0VSSUR+MS5DRENcTE9DQUxTfjFcVGVtcFw0dWh6dEc2SVl0LnNjXSBmaW5pc2hlZCB3aXRoCmV4aXQgY29kZTogWzBdCnN0ZG91dDogWwxjb25uZWN0IHRvIGNvcHNvbGEyDQoNCiAgIERhdGFiYXNlIENvbm5lY3Rpb24gSW5mb3JtYXRpb24NCg0KIERhdGFiYXNlIHNlcnZlciAgICAgICAgPSBEQjIvTlQgOC4yLjYNCiBTUUwgYXV0aG9yaXphdGlvbiBJRCAgID0gVVNFUklEDQogTG9jYWwgZGF0YWJhc2UgYWxpYXMgICA9IENPUFNPTEEyDQoNCg0Kc2V0IHdyaXRlIHN1c3BlbmQgZm9yIGRhdGFiYXNlDQpEQjIwMDAwSSAgVGhlIFNFVCBXUklURSBjb21tYW5kIGNvbXBsZXRlZCBzdWNjZXNzZnVsbHkuDQoNCmNvbm5lY3QgcmVzZXQNCkRCMjAwMDBJICBUaGUgU1FMIGNvbW1hbmQgY29tcGxldGVkIHN1Y2Nlc3NmdWxseS4NCg0KXQpzdGRlcnI6IFtd

[2014-08-05 18:00:25,903] INFO: [cdcola2:9090 (4.0.0.1)] Quiescing database copsola2 finished successfully

[2014-08-05 18:00:25,903] INFO: [cdcola2:9090 (4.0.0.1)] Quiescing database scanola

[2014-08-05 18:00:25,903] DEBUG: [cdcola2:9090 (4.0.0.1)] Executing SQL sequence:

connect to scanola;

set write suspend for database;

connect reset;

[2014-08-05 18:00:25,903] DEBUG: [cdcola2:9090 (4.0.0.1)] Q29tbWFuZCBbIkM6XFNRTExJQlxCSU5cZGIyY21kLmV4ZSIgLWMgLXcgLWkgIkM6XFNRTExJQlxCSU5cZGIyLmV4ZSIgLXR2ZiBDOlxET0NVTUV+MVxVU0VSSUR+MS5DRENcTE9DQUxTfjFcVGVtcFxza2ZreFdEVkN3LnNjXSBmaW5pc2hlZCB3aXRoCmV4aXQgY29kZTogWzBdCnN0ZG91dDogWwxjb25uZWN0IHRvIHNjYW5vbGENCg0KICAgRGF0YWJhc2UgQ29ubmVjdGlvbiBJbmZvcm1hdGlvbg0KDQogRGF0YWJhc2Ugc2VydmVyICAgICAgICA9IERCMi9OVCA4LjIuNg0KIFNRTCBhdXRob3JpemF0aW9uIElEICAgPSBVU0VSSUQNCiBMb2NhbCBkYXRhYmFzZSBhbGlhcyAgID0gU0NBTk9MQQ0KDQoNCnNldCB3cml0ZSBzdXNwZW5kIGZvciBkYXRhYmFzZQ0KREIyMDAwMEkgIFRoZSBTRVQgV1JJVEUgY29tbWFuZCBjb21wbGV0ZWQgc3VjY2Vzc2Z1bGx5Lg0KDQpjb25uZWN0IHJlc2V0DQpEQjIwMDAwSSAgVGhlIFNRTCBjb21tYW5kIGNvbXBsZXRlZCBzdWNjZXNzZnVsbHkuDQoNCl0Kc3RkZXJyOiBbXQ==

[2014-08-05 18:00:25,903] INFO: [cdcola2:9090 (4.0.0.1)] Quiescing database scanola finished successfully

[2014-08-05 18:00:25,903] INFO: [cdcola2:9090 (4.0.0.1)] Quiescing database cdcola2

[2014-08-05 18:00:25,903] DEBUG: [cdcola2:9090 (4.0.0.1)] Executing SQL sequence:

connect to cdcola2;

set write suspend for database;

connect reset;

[2014-08-05 18:00:25,903] DEBUG: [cdcola2:9090 (4.0.0.1)] Q29tbWFuZCBbIkM6XFNRTExJQlxCSU5cZGIyY21kLmV4ZSIgLWMgLXcgLWkgIkM6XFNRTExJQlxCSU5cZGIyLmV4ZSIgLXR2ZiBDOlxET0NVTUV+MVxVU0VSSUR+MS5DRENcTE9DQUxTfjFcVGVtcFwzdXVDdDVRUzg2LnNjXSBmaW5pc2hlZCB3aXRoCmV4aXQgY29kZTogWzBdCnN0ZG91dDogWwxjb25uZWN0IHRvIGNkY29sYTINCg0KICAgRGF0YWJhc2UgQ29ubmVjdGlvbiBJbmZvcm1hdGlvbg0KDQogRGF0YWJhc2Ugc2VydmVyICAgICAgICA9IERCMi9OVCA4LjIuNg0KIFNRTCBhdXRob3JpemF0aW9uIElEICAgPSBVU0VSSUQNCiBMb2NhbCBkYXRhYmFzZSBhbGlhcyAgID0gQ0RDT0xBMg0KDQoNCnNldCB3cml0ZSBzdXNwZW5kIGZvciBkYXRhYmFzZQ0KREIyMDAwMEkgIFRoZSBTRVQgV1JJVEUgY29tbWFuZCBjb21wbGV0ZWQgc3VjY2Vzc2Z1bGx5Lg0KDQpjb25uZWN0IHJlc2V0DQpEQjIwMDAwSSAgVGhlIFNRTCBjb21tYW5kIGNvbXBsZXRlZCBzdWNjZXNzZnVsbHkuDQoNCl0Kc3RkZXJyOiBbXQ==

[2014-08-05 18:00:25,903] INFO: [cdcola2:9090 (4.0.0.1)] Quiescing database cdcola2 finished successfully

[2014-08-05 18:00:25,903] INFO: [cdcola2:9090 (4.0.0.1)] Quiescing database olabatch

[2014-08-05 18:00:25,903] DEBUG: [cdcola2:9090 (4.0.0.1)] Executing SQL sequence:

connect to olabatch;

set write suspend for database;

connect reset;

[2014-08-05 18:00:25,903] DEBUG: [cdcola2:9090 (4.0.0.1)] Q29tbWFuZCBbIkM6XFNRTExJQlxCSU5cZGIyY21kLmV4ZSIgLWMgLXcgLWkgIkM6XFNRTExJQlxCSU5cZGIyLmV4ZSIgLXR2ZiBDOlxET0NVTUV+MVxVU0VSSUR+MS5DRENcTE9DQUxTfjFcVGVtcFw3SWNyU0d2Uld0LnNjXSBmaW5pc2hlZCB3aXRoCmV4aXQgY29kZTogWzBdCnN0ZG91dDogWwxjb25uZWN0IHRvIG9sYWJhdGNoDQoNCiAgIERhdGFiYXNlIENvbm5lY3Rpb24gSW5mb3JtYXRpb24NCg0KIERhdGFiYXNlIHNlcnZlciAgICAgICAgPSBEQjIvTlQgOC4yLjYNCiBTUUwgYXV0aG9yaXphdGlvbiBJRCAgID0gVVNFUklEDQogTG9jYWwgZGF0YWJhc2UgYWxpYXMgICA9IE9MQUJBVENIDQoNCg0Kc2V0IHdyaXRlIHN1c3BlbmQgZm9yIGRhdGFiYXNlDQpEQjIwMDAwSSAgVGhlIFNFVCBXUklURSBjb21tYW5kIGNvbXBsZXRlZCBzdWNjZXNzZnVsbHkuDQoNCmNvbm5lY3QgcmVzZXQNCkRCMjAwMDBJICBUaGUgU1FMIGNvbW1hbmQgY29tcGxldGVkIHN1Y2Nlc3NmdWxseS4NCg0KXQpzdGRlcnI6IFtd

[2014-08-05 18:00:25,903] INFO: [cdcola2:9090 (4.0.0.1)] Quiescing database olabatch finished successfully

[2014-08-05 18:00:25,903] INFO: [cdcola2:9090 (4.0.0.1)] Quiescing databases finished successfully

########## Application Quiesce finished successfully ##########

########## POST APPLICATION QUIESCE COMMANDS ##########

[2014-08-05 18:00:25,903] INFO: Post application quiesce commands are not defined

########## POST APPLICATION QUIESCE COMMANDS FINISHED SUCCESSFULLY  ##########

########## PRE NTAP COMMANDS ##########

[2014-08-05 18:00:25,919] INFO: Pre ntap commands are not defined

########## PRE NTAP COMMANDS FINISHED SUCCESSFULLY ##########

########## Generating Info ASUP on CDCFAS02 ##########

[2014-08-05 18:00:26,340] INFO: STORAGE-01001: Creating autosupport message with event id [0], category [Backup Started], description [INFO: Snap Creator Framework 4.0p1 Backup for cdcola2 ACTION: backup POLICY: daily Plugin: db2 Supported Volumes: cdcola2_k,cdcola2_l,cdcola2_m,cdcola2_n, Started], level [INFO], hostname [winmgmt [cdcola2:9090]].

[2014-08-05 18:00:26,340] DEBUG: <ems-autosupport-log>

    <computer-name>winmgmt [cdcola2:9090]</computer-name>

    <event-id>0</event-id>

    <event-source>SNAPCREATOR</event-source>

    <app-version>Snap Creator Framework 4.0p1</app-version>

    <category>Backup Started</category>

    <event-description>INFO: Snap Creator Framework 4.0p1 Backup for cdcola2 ACTION: backup POLICY: daily Plugin: db2 Supported Volumes: cdcola2_k,cdcola2_l,cdcola2_m,cdcola2_n, Started</event-description>

    <log-level>6</log-level>

    <auto-support>false</auto-support>

</ems-autosupport-log>

[2014-08-05 18:00:26,340] INFO: STORAGE-01002: Creating autosupport message with event id [0], category [Backup Started], description [INFO: Snap Creator Framework 4.0p1 Backup for cdcola2 ACTION: backup POLICY: daily Plugin: db2 Supported Volumes: cdcola2_k,cdcola2_l,cdcola2_m,cdcola2_n, Started], level [INFO], hostname [winmgmt [cdcola2:9090]] finished successfully.

[2014-08-05 18:00:26,340] INFO: ASUP finished successfully on CDCFAS02

########## Running Snapshot copy Rename on Primary devices ##########

[2014-08-05 18:00:26,340] INFO: Skipping Snapshot copy rename

########## File system plug-in not defined. Skipping file system quiesce ##########

########## SNAPSHOT CREATE COMMANDS ##########

[2014-08-05 18:01:12,393] INFO: [cdcola2:9090 (4.0.0.1)] Executing Snapshot create  command ["D:/Program Files/NetApp/SnapDrive/sdcli" snap create -m cdcola2 -s cdcola2-daily_20140805180003 -D K: L: M: N: -u no] on cdcola2

[2014-08-05 18:01:12,393] DEBUG: [cdcola2:9090 (4.0.0.1)] Executing command ["D:/Program Files/NetApp/SnapDrive/sdcli" snap create -m cdcola2 -s cdcola2-daily_20140805180003 -D K: L: M: N: -u no]

[2014-08-05 18:01:12,393] TRACE: Command ["D:/Program Files/NetApp/SnapDrive/sdcli" snap create -m cdcola2 -s cdcola2-daily_20140805180003 -D K: L: M: N: -u no] finished with

exit code: [0]

stdout: [Initializing...CDCOLA2 : Checking policies

CDCOLA2 : Checking access control

CDCOLA2 : Preparing LUNs for Snapshot creation

CDCOLA2 : Ready to create snapshot copy

CDCOLA2 : Creating a Snapshot for the LUN

The operation completed successfully.

]

stderr: []

[2014-08-05 18:01:12,393] DEBUG: [cdcola2:9090 (4.0.0.1)] Command ["D:/Program Files/NetApp/SnapDrive/sdcli" snap create -m cdcola2 -s cdcola2-daily_20140805180003 -D K: L: M: N: -u no] finished successfully with message

[Initializing...CDCOLA2 : Checking policies

CDCOLA2 : Checking access control

CDCOLA2 : Preparing LUNs for Snapshot creation

CDCOLA2 : Ready to create snapshot copy

CDCOLA2 : Creating a Snapshot for the LUN

The operation completed successfully.

]

[2014-08-05 18:01:12,393] INFO: Snapshot create  completed successfully

########## Snapshot copy create commands finished successfully ##########

[2014-08-05 18:01:12,564] INFO: Skipping SIS clone backup.

[2014-08-05 18:01:12,564] INFO: Skipping consistency group Snapshot copy

[2014-08-05 18:01:12,767] INFO: Skipping snapshot creation using ZAPI.

########## File system plug-in not defined. Skipping file system unquiesce ##########

########## PRE APPLICATION UNQUIESCE COMMANDS ##########

[2014-08-05 18:01:12,970] INFO: Pre application unquiesce commands are not defined

########## PRE APPLICATION UNQUIESCE COMMANDS FINISHED SUCCESSFULLY  ##########

########## Application Unquiesce ##########

[2014-08-05 18:01:19,444] DEBUG: [cdcola2:9090 (4.0.0.1)] db2::setENV finished successfully

[2014-08-05 18:01:19,444] INFO: [cdcola2:9090 (4.0.0.1)] Unquiescing databases

[2014-08-05 18:01:19,444] INFO: [cdcola2:9090 (4.0.0.1)] Unquiescing database copsola2

[2014-08-05 18:01:19,444] DEBUG: [cdcola2:9090 (4.0.0.1)] Executing SQL sequence:

connect to copsola2;

set write resume for database;

connect reset;

[2014-08-05 18:01:19,444] DEBUG: [cdcola2:9090 (4.0.0.1)] Q29tbWFuZCBbIkM6XFNRTExJQlxCSU5cZGIyY21kLmV4ZSIgLWMgLXcgLWkgIkM6XFNRTExJQlxCSU5cZGIyLmV4ZSIgLXR2ZiBDOlxET0NVTUV+MVxVU0VSSUR+MS5DRENcTE9DQUxTfjFcVGVtcFwyMW1BOGw4ZE1ULnNjXSBmaW5pc2hlZCB3aXRoCmV4aXQgY29kZTogWzBdCnN0ZG91dDogWwxjb25uZWN0IHRvIGNvcHNvbGEyDQoNCiAgIERhdGFiYXNlIENvbm5lY3Rpb24gSW5mb3JtYXRpb24NCg0KIERhdGFiYXNlIHNlcnZlciAgICAgICAgPSBEQjIvTlQgOC4yLjYNCiBTUUwgYXV0aG9yaXphdGlvbiBJRCAgID0gVVNFUklEDQogTG9jYWwgZGF0YWJhc2UgYWxpYXMgICA9IENPUFNPTEEyDQoNCg0Kc2V0IHdyaXRlIHJlc3VtZSBmb3IgZGF0YWJhc2UNCkRCMjAwMDBJICBUaGUgU0VUIFdSSVRFIGNvbW1hbmQgY29tcGxldGVkIHN1Y2Nlc3NmdWxseS4NCg0KY29ubmVjdCByZXNldA0KREIyMDAwMEkgIFRoZSBTUUwgY29tbWFuZCBjb21wbGV0ZWQgc3VjY2Vzc2Z1bGx5Lg0KDQpdCnN0ZGVycjogW10=

[2014-08-05 18:01:19,444] INFO: [cdcola2:9090 (4.0.0.1)] Unquiescing database copsola2 finished successfully

[2014-08-05 18:01:19,444] INFO: [cdcola2:9090 (4.0.0.1)] Unquiescing database scanola

[2014-08-05 18:01:19,444] DEBUG: [cdcola2:9090 (4.0.0.1)] Executing SQL sequence:

connect to scanola;

set write resume for database;

connect reset;

[2014-08-05 18:01:19,444] DEBUG: [cdcola2:9090 (4.0.0.1)] Q29tbWFuZCBbIkM6XFNRTExJQlxCSU5cZGIyY21kLmV4ZSIgLWMgLXcgLWkgIkM6XFNRTExJQlxCSU5cZGIyLmV4ZSIgLXR2ZiBDOlxET0NVTUV+MVxVU0VSSUR+MS5DRENcTE9DQUxTfjFcVGVtcFxYZkxicDc1QUIyLnNjXSBmaW5pc2hlZCB3aXRoCmV4aXQgY29kZTogWzBdCnN0ZG91dDogWwxjb25uZWN0IHRvIHNjYW5vbGENCg0KICAgRGF0YWJhc2UgQ29ubmVjdGlvbiBJbmZvcm1hdGlvbg0KDQogRGF0YWJhc2Ugc2VydmVyICAgICAgICA9IERCMi9OVCA4LjIuNg0KIFNRTCBhdXRob3JpemF0aW9uIElEICAgPSBVU0VSSUQNCiBMb2NhbCBkYXRhYmFzZSBhbGlhcyAgID0gU0NBTk9MQQ0KDQoNCnNldCB3cml0ZSByZXN1bWUgZm9yIGRhdGFiYXNlDQpEQjIwMDAwSSAgVGhlIFNFVCBXUklURSBjb21tYW5kIGNvbXBsZXRlZCBzdWNjZXNzZnVsbHkuDQoNCmNvbm5lY3QgcmVzZXQNCkRCMjAwMDBJICBUaGUgU1FMIGNvbW1hbmQgY29tcGxldGVkIHN1Y2Nlc3NmdWxseS4NCg0KXQpzdGRlcnI6IFtd

[2014-08-05 18:01:19,444] INFO: [cdcola2:9090 (4.0.0.1)] Unquiescing database scanola finished successfully

[2014-08-05 18:01:19,444] INFO: [cdcola2:9090 (4.0.0.1)] Unquiescing database cdcola2

[2014-08-05 18:01:19,444] DEBUG: [cdcola2:9090 (4.0.0.1)] Executing SQL sequence:

connect to cdcola2;

set write resume for database;

connect reset;

[2014-08-05 18:01:19,444] DEBUG: [cdcola2:9090 (4.0.0.1)] Q29tbWFuZCBbIkM6XFNRTExJQlxCSU5cZGIyY21kLmV4ZSIgLWMgLXcgLWkgIkM6XFNRTExJQlxCSU5cZGIyLmV4ZSIgLXR2ZiBDOlxET0NVTUV+MVxVU0VSSUR+MS5DRENcTE9DQUxTfjFcVGVtcFxfVHNUN19qTVc2LnNjXSBmaW5pc2hlZCB3aXRoCmV4aXQgY29kZTogWzBdCnN0ZG91dDogWwxjb25uZWN0IHRvIGNkY29sYTINCg0KICAgRGF0YWJhc2UgQ29ubmVjdGlvbiBJbmZvcm1hdGlvbg0KDQogRGF0YWJhc2Ugc2VydmVyICAgICAgICA9IERCMi9OVCA4LjIuNg0KIFNRTCBhdXRob3JpemF0aW9uIElEICAgPSBVU0VSSUQNCiBMb2NhbCBkYXRhYmFzZSBhbGlhcyAgID0gQ0RDT0xBMg0KDQoNCnNldCB3cml0ZSByZXN1bWUgZm9yIGRhdGFiYXNlDQpEQjIwMDAwSSAgVGhlIFNFVCBXUklURSBjb21tYW5kIGNvbXBsZXRlZCBzdWNjZXNzZnVsbHkuDQoNCmNvbm5lY3QgcmVzZXQNCkRCMjAwMDBJICBUaGUgU1FMIGNvbW1hbmQgY29tcGxldGVkIHN1Y2Nlc3NmdWxseS4NCg0KXQpzdGRlcnI6IFtd

[2014-08-05 18:01:19,444] INFO: [cdcola2:9090 (4.0.0.1)] Unquiescing database cdcola2 finished successfully

[2014-08-05 18:01:19,444] INFO: [cdcola2:9090 (4.0.0.1)] Unquiescing database olabatch

[2014-08-05 18:01:19,444] DEBUG: [cdcola2:9090 (4.0.0.1)] Executing SQL sequence:

connect to olabatch;

set write resume for database;

connect reset;

[2014-08-05 18:01:19,444] DEBUG: [cdcola2:9090 (4.0.0.1)] Q29tbWFuZCBbIkM6XFNRTExJQlxCSU5cZGIyY21kLmV4ZSIgLWMgLXcgLWkgIkM6XFNRTExJQlxCSU5cZGIyLmV4ZSIgLXR2ZiBDOlxET0NVTUV+MVxVU0VSSUR+MS5DRENcTE9DQUxTfjFcVGVtcFx4Nm02ZzA5bnlULnNjXSBmaW5pc2hlZCB3aXRoCmV4aXQgY29kZTogWzBdCnN0ZG91dDogWwxjb25uZWN0IHRvIG9sYWJhdGNoDQoNCiAgIERhdGFiYXNlIENvbm5lY3Rpb24gSW5mb3JtYXRpb24NCg0KIERhdGFiYXNlIHNlcnZlciAgICAgICAgPSBEQjIvTlQgOC4yLjYNCiBTUUwgYXV0aG9yaXphdGlvbiBJRCAgID0gVVNFUklEDQogTG9jYWwgZGF0YWJhc2UgYWxpYXMgICA9IE9MQUJBVENIDQoNCg0Kc2V0IHdyaXRlIHJlc3VtZSBmb3IgZGF0YWJhc2UNCkRCMjAwMDBJICBUaGUgU0VUIFdSSVRFIGNvbW1hbmQgY29tcGxldGVkIHN1Y2Nlc3NmdWxseS4NCg0KY29ubmVjdCByZXNldA0KREIyMDAwMEkgIFRoZSBTUUwgY29tbWFuZCBjb21wbGV0ZWQgc3VjY2Vzc2Z1bGx5Lg0KDQpdCnN0ZGVycjogW10=

[2014-08-05 18:01:19,444] INFO: [cdcola2:9090 (4.0.0.1)] Unquiescing database olabatch finished successfully

[2014-08-05 18:01:19,444] INFO: [cdcola2:9090 (4.0.0.1)] Unquiescing databases finished successfully

########## Application Unquiesce finished successfully ##########

########## POST APPLICATION UNQUIESCE COMMANDS ##########

[2014-08-05 18:01:48,913] INFO: [cdcola2:9090 (4.0.0.1)] Executing Post unapplication quiesce command [ping -n 30 localhost] on cdcola2

[2014-08-05 18:01:48,913] DEBUG: [cdcola2:9090 (4.0.0.1)] Executing command [ping -n 30 localhost]

[2014-08-05 18:01:48,913] TRACE: Command [ping -n 30 localhost] finished with

exit code: [0]

stdout: [

Pinging cdcola2.AcuityLightingGroup.com [127.0.0.1] with 32 bytes of data&colon;

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 127.0.0.1:

    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 0ms, Maximum = 0ms, Average = 0ms

]

stderr: []

[2014-08-05 18:01:48,913] DEBUG: [cdcola2:9090 (4.0.0.1)] Command [ping -n 30 localhost] finished successfully with message

[

Pinging cdcola2.AcuityLightingGroup.com [127.0.0.1] with 32 bytes of data&colon;

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 127.0.0.1:

    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 0ms, Maximum = 0ms, Average = 0ms

]

[2014-08-05 18:01:48,913] INFO: Post unapplication quiesce completed successfully

########## POST APPLICATION UNQUIESCE COMMANDS FINISHED SUCCESSFULLY  ##########

########## Generating Info ASUP on CDCFAS02 ##########

[2014-08-05 18:01:49,366] INFO: STORAGE-01001: Creating autosupport message with event id [0], category [Backup Completed], description [INFO: Snap Creator Framework 4.0p1 Backup for cdcola2 ACTION: backup POLICY: daily Plugin: db2 Supported Volumes: cdcola2_k,cdcola2_l,cdcola2_m,cdcola2_n, finished], level [INFO], hostname [winmgmt [cdcola2:9090]].

[2014-08-05 18:01:49,366] DEBUG: <ems-autosupport-log>

    <computer-name>winmgmt [cdcola2:9090]</computer-name>

    <event-id>0</event-id>

    <event-source>SNAPCREATOR</event-source>

    <app-version>Snap Creator Framework 4.0p1</app-version>

    <category>Backup Completed</category>

    <event-description>INFO: Snap Creator Framework 4.0p1 Backup for cdcola2 ACTION: backup POLICY: daily Plugin: db2 Supported Volumes: cdcola2_k,cdcola2_l,cdcola2_m,cdcola2_n, finished</event-description>

    <log-level>6</log-level>

    <auto-support>false</auto-support>

</ems-autosupport-log>

[2014-08-05 18:01:49,366] INFO: STORAGE-01002: Creating autosupport message with event id [0], category [Backup Completed], description [INFO: Snap Creator Framework 4.0p1 Backup for cdcola2 ACTION: backup POLICY: daily Plugin: db2 Supported Volumes: cdcola2_k,cdcola2_l,cdcola2_m,cdcola2_n, finished], level [INFO], hostname [winmgmt [cdcola2:9090]] finished successfully.

[2014-08-05 18:01:49,366] INFO: ASUP finished successfully on CDCFAS02

[2014-08-05 18:01:49,381] WARN: Configuration not enabled for snapvault!

########## Running Snapshot copy Rename on Secondary devices ##########

[2014-08-05 18:01:49,381] WARN: Configuration not enabled for snapvault!

########## Checking Protection Manager dataset snapcreator_CDCOLA2 ##########

[2014-08-05 18:01:49,834] INFO: STORAGE-02090: Listing Snapshot copies on volume [cdcola2_k].

[2014-08-05 18:01:49,834] DEBUG: <snapshot-list-info>

    <volume>cdcola2_k</volume>

    <terse>true</terse>

</snapshot-list-info>

[2014-08-05 18:01:49,834] INFO: STORAGE-02091: Listing Snapshot copies on volume [cdcola2_k] finished successfully.

[2014-08-05 18:01:50,239] INFO: STORAGE-02090: Listing Snapshot copies on volume [cdcola2_l].

[2014-08-05 18:01:50,239] DEBUG: <snapshot-list-info>

    <volume>cdcola2_l</volume>

    <terse>true</terse>

</snapshot-list-info>

[2014-08-05 18:01:50,239] INFO: STORAGE-02091: Listing Snapshot copies on volume [cdcola2_l] finished successfully.

[2014-08-05 18:01:50,816] INFO: STORAGE-02090: Listing Snapshot copies on volume [cdcola2_m].

[2014-08-05 18:01:50,816] DEBUG: <snapshot-list-info>

    <volume>cdcola2_m</volume>

    <terse>true</terse>

</snapshot-list-info>

[2014-08-05 18:01:50,816] INFO: STORAGE-02091: Listing Snapshot copies on volume [cdcola2_m] finished successfully.

[2014-08-05 18:01:51,362] INFO: STORAGE-02090: Listing Snapshot copies on volume [cdcola2_n].

[2014-08-05 18:01:51,362] DEBUG: <snapshot-list-info>

    <volume>cdcola2_n</volume>

    <terse>true</terse>

</snapshot-list-info>

[2014-08-05 18:01:51,362] INFO: STORAGE-02091: Listing Snapshot copies on volume [cdcola2_n] finished successfully.

[2014-08-05 18:01:51,581] INFO: STORAGE-05007: Retrieving Protection Manager dataset status for dataset [snapcreator_CDCOLA2].

[2014-08-05 18:01:51,581] DEBUG: <dataset-list-info-iter-start>

    <object-name-or-id>snapcreator_CDCOLA2</object-name-or-id>

</dataset-list-info-iter-start>

[2014-08-05 18:01:51,581] DEBUG: <dataset-list-info-iter-next>

    <maximum>1</maximum>

    <tag>dataset123980_4524</tag>

</dataset-list-info-iter-next>

[2014-08-05 18:01:51,581] WARN: STORAGE-05014: Protection Manager dataset [snapcreator_CDCOLA2] resource status should be normal.

[2014-08-05 18:01:51,581] DEBUG: <dataset-list-info-iter-end>

    <tag>dataset123980_4524</tag>

</dataset-list-info-iter-end>

[2014-08-05 18:01:51,581] INFO: STORAGE-05008: Retrieving Protection Manager dataset status for dataset [snapcreator_CDCOLA2] finished successfully.

[2014-08-05 18:01:51,628] INFO: STORAGE-03044: Protection Manager dataset modify for dataset [snapcreator_CDCOLA2]

[2014-08-05 18:01:51,628] DEBUG: <dataset-list-info-iter-start>

    <object-name-or-id>snapcreator_CDCOLA2</object-name-or-id>

</dataset-list-info-iter-start>

[2014-08-05 18:01:51,628] DEBUG: <dataset-list-info-iter-next>

    <maximum>1</maximum>

    <tag>dataset123981_12037</tag>

</dataset-list-info-iter-next>

[2014-08-05 18:01:51,628] DEBUG: <dataset-list-info-iter-end>

    <tag>dataset123981_12037</tag>

</dataset-list-info-iter-end>

[2014-08-05 18:01:51,628] INFO: STORAGE-03045: Protection Manager dataset modify successful for dataset [snapcreator_CDCOLA2]

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

[2014-08-05 18:01:52,361] INFO: STORAGE-05004: Creating Protection Manager driven backup of dataset [snapcreator_CDCOLA2] on storage controller [CDCFAS02].

[2014-08-05 18:01:52,361] INFO: Creating Protection Manager Backup Version for volume cdcola2_k dataset snapcreator_CDCOLA2

[2014-08-05 18:01:52,361] INFO: STORAGE-05015: Added member [CDCFAS02:/cdcola2_k/-] of dataset [snapcreator_CDCOLA2] to Protection Manager backup version.

[2014-08-05 18:01:52,361] INFO: STORAGE-05015: Added member [CDCFAS02:/cdcola2_k/q0] of dataset [snapcreator_CDCOLA2] to Protection Manager backup version.

[2014-08-05 18:01:52,361] INFO: Creating Protection Manager Backup Version for volume cdcola2_l dataset snapcreator_CDCOLA2

[2014-08-05 18:01:52,361] INFO: STORAGE-05015: Added member [CDCFAS02:/cdcola2_l/-] of dataset [snapcreator_CDCOLA2] to Protection Manager backup version.

[2014-08-05 18:01:52,361] INFO: Creating Protection Manager Backup Version for volume cdcola2_m dataset snapcreator_CDCOLA2

[2014-08-05 18:01:52,361] INFO: STORAGE-05015: Added member [CDCFAS02:/cdcola2_m/-] of dataset [snapcreator_CDCOLA2] to Protection Manager backup version.

[2014-08-05 18:01:52,361] INFO: STORAGE-05015: Added member [CDCFAS02:/cdcola2_m/q0] of dataset [snapcreator_CDCOLA2] to Protection Manager backup version.

[2014-08-05 18:01:52,361] INFO: Creating Protection Manager Backup Version for volume cdcola2_n dataset snapcreator_CDCOLA2

[2014-08-05 18:01:52,361] INFO: STORAGE-05015: Added member [CDCFAS02:/cdcola2_n/-] of dataset [snapcreator_CDCOLA2] to Protection Manager backup version.

[2014-08-05 18:01:52,361] INFO: STORAGE-05015: Added member [CDCFAS02:/cdcola2_n/q0] of dataset [snapcreator_CDCOLA2] to Protection Manager backup version.

[2014-08-05 18:01:52,361] DEBUG: <dp-backup-version-create>

    <backup-description>SnapCreator 4.0 Backup</backup-description>

    <dataset-name-or-id>snapcreator_CDCOLA2</dataset-name-or-id>

    <retention-type>daily</retention-type>

    <version-timestamp>1407276068</version-timestamp>

    <version-members>

        <version-member-info>

            <snapshot-unique-id>1407276068</snapshot-unique-id>

            <snapshot-name>cdcola2-daily_20140805180003</snapshot-name>

            <volume-name>CDCFAS02:/cdcola2_k</volume-name>

            <snapshot-contents>

                <snapshot-member-info>

                    <primary-name>CDCFAS02:/cdcola2_k/-</primary-name>

                </snapshot-member-info>

                <snapshot-member-info>

                    <primary-name>CDCFAS02:/cdcola2_k/q0</primary-name>

                </snapshot-member-info>

            </snapshot-contents>

        </version-member-info>

        <version-member-info>

            <snapshot-unique-id>1407276068</snapshot-unique-id>

            <snapshot-name>cdcola2-daily_20140805180003</snapshot-name>

            <volume-name>CDCFAS02:/cdcola2_l</volume-name>

            <snapshot-contents>

                <snapshot-member-info>

                    <primary-name>CDCFAS02:/cdcola2_l/-</primary-name>

                </snapshot-member-info>

            </snapshot-contents>

        </version-member-info>

        <version-member-info>

            <snapshot-unique-id>1407276068</snapshot-unique-id>

            <snapshot-name>cdcola2-daily_20140805180003</snapshot-name>

            <volume-name>CDCFAS02:/cdcola2_m</volume-name>

            <snapshot-contents>

                <snapshot-member-info>

                    <primary-name>CDCFAS02:/cdcola2_m/-</primary-name>

                </snapshot-member-info>

                <snapshot-member-info>

                    <primary-name>CDCFAS02:/cdcola2_m/q0</primary-name>

                </snapshot-member-info>

            </snapshot-contents>

        </version-member-info>

        <version-member-info>

            <snapshot-unique-id>1407276068</snapshot-unique-id>

            <snapshot-name>cdcola2-daily_20140805180003</snapshot-name>

            <volume-name>CDCFAS02:/cdcola2_n</volume-name>

            <snapshot-contents>

                <snapshot-member-info>

                    <primary-name>CDCFAS02:/cdcola2_n/-</primary-name>

                </snapshot-member-info>

                <snapshot-member-info>

                    <primary-name>CDCFAS02:/cdcola2_n/q0</primary-name>

                </snapshot-member-info>

            </snapshot-contents>

        </version-member-info>

    </version-members>

</dp-backup-version-create>

[2014-08-05 18:01:52,361] INFO: STORAGE-05005: Creating Protection Manager driven backup of dataset [snapcreator_CDCOLA2] on storage controller [CDCFAS02] finished successfully.

[2014-08-05 18:01:52,454] INFO: STORAGE-03017: Running Protection Manager backup start for dataset [snapcreator_CDCOLA2].

[2014-08-05 18:01:52,454] INFO: Starting Protection Manager backup

[2014-08-05 18:01:52,454] DEBUG: <dp-backup-start>

    <backup-description>Snap Creator Framework Initiated Backup</backup-description>

    <dataset-name-or-id>snapcreator_CDCOLA2</dataset-name-or-id>

    <retention-type>

        <dp-backup-retention-type>daily</dp-backup-retention-type>

    </retention-type>

</dp-backup-start>

[2014-08-05 18:01:52,454] INFO: STORAGE-03018: Protection Manager backup started successfully.

[2014-08-05 18:02:02,485] INFO: STORAGE-03020: Getting Protection Manager backup progress for job-id [73188]

[2014-08-05 18:02:02,485] DEBUG: <dp-job-progress-event-list-iter-start>

    <job-id>73188</job-id>

</dp-job-progress-event-list-iter-start>

[2014-08-05 18:02:02,485] DEBUG: <dp-job-progress-event-list-iter-next>

    <maximum>10</maximum>

    <tag>dpjobprogress123994_28452</tag>

</dp-job-progress-event-list-iter-next>

[2014-08-05 18:02:02,485] INFO: STORAGE-03021: Protection Manager backup progress get for job-id [73188] completed successfully

[2014-08-05 18:02:02,485] INFO: Protection Manager backup for job-id 73188 status is snapmirror-progress! Sleeping 1 minute

[2014-08-05 18:03:02,516] INFO: STORAGE-03020: Getting Protection Manager backup progress for job-id [73188]

[2014-08-05 18:03:02,516] DEBUG: <dp-job-progress-event-list-iter-start>

    <job-id>73188</job-id>

</dp-job-progress-event-list-iter-start>

[2014-08-05 18:03:02,516] DEBUG: <dp-job-progress-event-list-iter-next>

    <maximum>15</maximum>

    <tag>dpjobprogress123999_14203</tag>

</dp-job-progress-event-list-iter-next>

[2014-08-05 18:03:02,516] INFO: STORAGE-03021: Protection Manager backup progress get for job-id [73188] completed successfully

[2014-08-05 18:03:02,516] INFO: Protection Manager backup for job-id 73188 status is snapmirror-progress! Sleeping 1 minute

[2014-08-05 18:04:02,546] INFO: STORAGE-03020: Getting Protection Manager backup progress for job-id [73188]

[2014-08-05 18:04:02,546] DEBUG: <dp-job-progress-event-list-iter-start>

    <job-id>73188</job-id>

</dp-job-progress-event-list-iter-start>

[2014-08-05 18:04:02,546] DEBUG: <dp-job-progress-event-list-iter-next>

    <maximum>16</maximum>

    <tag>dpjobprogress124006_15202</tag>

</dp-job-progress-event-list-iter-next>

[2014-08-05 18:04:02,546] INFO: STORAGE-03021: Protection Manager backup progress get for job-id [73188] completed successfully

[2014-08-05 18:04:02,546] INFO: Protection Manager backup for job-id 73188 status is snapmirror-end! Sleeping 1 minute

[2014-08-05 18:05:02,576] INFO: STORAGE-03020: Getting Protection Manager backup progress for job-id [73188]

[2014-08-05 18:05:02,576] DEBUG: <dp-job-progress-event-list-iter-start>

    <job-id>73188</job-id>

</dp-job-progress-event-list-iter-start>

[2014-08-05 18:05:02,576] DEBUG: <dp-job-progress-event-list-iter-next>

    <maximum>17</maximum>

    <tag>dpjobprogress124007_29496</tag>

</dp-job-progress-event-list-iter-next>

[2014-08-05 18:05:02,576] INFO: STORAGE-03021: Protection Manager backup progress get for job-id [73188] completed successfully

[2014-08-05 18:05:02,576] INFO: Protection Manager backup for job-id 73188 status is snapmirror-end! Sleeping 1 minute

[2014-08-05 18:06:02,622] INFO: STORAGE-03020: Getting Protection Manager backup progress for job-id [73188]

[2014-08-05 18:06:02,622] DEBUG: <dp-job-progress-event-list-iter-start>

    <job-id>73188</job-id>

</dp-job-progress-event-list-iter-start>

[2014-08-05 18:06:02,622] DEBUG: <dp-job-progress-event-list-iter-next>

    <maximum>19</maximum>

    <tag>dpjobprogress124008_15632</tag>

</dp-job-progress-event-list-iter-next>

[2014-08-05 18:06:02,622] INFO: STORAGE-03021: Protection Manager backup progress get for job-id [73188] completed successfully

[2014-08-05 18:06:02,622] INFO: Protection Manager backup for job-id 73188 status is snapmirror-end! Sleeping 1 minute

[2014-08-05 18:07:02,840] INFO: STORAGE-03020: Getting Protection Manager backup progress for job-id [73188]

[2014-08-05 18:07:02,840] DEBUG: <dp-job-progress-event-list-iter-start>

    <job-id>73188</job-id>

</dp-job-progress-event-list-iter-start>

[2014-08-05 18:07:02,840] DEBUG: <dp-job-progress-event-list-iter-next>

    <maximum>60</maximum>

    <tag>dpjobprogress124040_4368</tag>

</dp-job-progress-event-list-iter-next>

[2014-08-05 18:07:02,840] INFO: STORAGE-03021: Protection Manager backup progress get for job-id [73188] completed successfully

[2014-08-05 18:07:02,840] INFO: Protection Manager backup for job-id 73188 status is snapvault-end! Sleeping 1 minute

[2014-08-05 18:08:02,886] INFO: STORAGE-03020: Getting Protection Manager backup progress for job-id [73188]

[2014-08-05 18:08:02,886] DEBUG: <dp-job-progress-event-list-iter-start>

    <job-id>73188</job-id>

</dp-job-progress-event-list-iter-start>

[2014-08-05 18:08:02,886] DEBUG: <dp-job-progress-event-list-iter-next>

    <maximum>61</maximum>

    <tag>dpjobprogress124041_941</tag>

</dp-job-progress-event-list-iter-next>

[2014-08-05 18:08:02,886] INFO: STORAGE-03021: Protection Manager backup progress get for job-id [73188] completed successfully

[2014-08-05 18:08:02,886] INFO: Protection Manager backup for job-id 73188 status is snapvault-end! Sleeping 1 minute

[2014-08-05 18:09:02,932] INFO: STORAGE-03020: Getting Protection Manager backup progress for job-id [73188]

[2014-08-05 18:09:02,932] DEBUG: <dp-job-progress-event-list-iter-start>

    <job-id>73188</job-id>

</dp-job-progress-event-list-iter-start>

[2014-08-05 18:09:02,932] DEBUG: <dp-job-progress-event-list-iter-next>

    <maximum>61</maximum>

    <tag>dpjobprogress124042_29259</tag>

</dp-job-progress-event-list-iter-next>

[2014-08-05 18:09:02,932] INFO: STORAGE-03021: Protection Manager backup progress get for job-id [73188] completed successfully

[2014-08-05 18:09:02,932] INFO: Protection Manager backup for job-id 73188 status is snapvault-progress! Sleeping 1 minute

[2014-08-05 18:10:02,978] INFO: STORAGE-03020: Getting Protection Manager backup progress for job-id [73188]

[2014-08-05 18:10:02,978] DEBUG: <dp-job-progress-event-list-iter-start>

    <job-id>73188</job-id>

</dp-job-progress-event-list-iter-start>

[2014-08-05 18:10:02,978] DEBUG: <dp-job-progress-event-list-iter-next>

    <maximum>61</maximum>

    <tag>dpjobprogress124043_18095</tag>

</dp-job-progress-event-list-iter-next>

[2014-08-05 18:10:02,978] INFO: STORAGE-03021: Protection Manager backup progress get for job-id [73188] completed successfully

[2014-08-05 18:10:02,978] INFO: Protection Manager backup for job-id 73188 status is snapvault-progress! Sleeping 1 minute

[2014-08-05 18:11:03,024] INFO: STORAGE-03020: Getting Protection Manager backup progress for job-id [73188]

[2014-08-05 18:11:03,024] DEBUG: <dp-job-progress-event-list-iter-start>

    <job-id>73188</job-id>

</dp-job-progress-event-list-iter-start>

[2014-08-05 18:11:03,024] DEBUG: <dp-job-progress-event-list-iter-next>

    <maximum>61</maximum>

    <tag>dpjobprogress124049_16117</tag>

</dp-job-progress-event-list-iter-next>

[2014-08-05 18:11:03,024] INFO: STORAGE-03021: Protection Manager backup progress get for job-id [73188] completed successfully

[2014-08-05 18:11:03,024] INFO: Protection Manager backup for job-id 73188 status is snapvault-progress! Sleeping 1 minute

[2014-08-05 18:12:03,070] INFO: STORAGE-03020: Getting Protection Manager backup progress for job-id [73188]

[2014-08-05 18:12:03,070] DEBUG: <dp-job-progress-event-list-iter-start>

    <job-id>73188</job-id>

</dp-job-progress-event-list-iter-start>

[2014-08-05 18:12:03,070] DEBUG: <dp-job-progress-event-list-iter-next>

    <maximum>61</maximum>

    <tag>dpjobprogress124050_9511</tag>

</dp-job-progress-event-list-iter-next>

[2014-08-05 18:12:03,070] INFO: STORAGE-03021: Protection Manager backup progress get for job-id [73188] completed successfully

[2014-08-05 18:12:03,070] INFO: Protection Manager backup for job-id 73188 status is snapvault-progress! Sleeping 1 minute

[2014-08-05 18:13:03,318] INFO: STORAGE-03020: Getting Protection Manager backup progress for job-id [73188]

[2014-08-05 18:13:03,318] DEBUG: <dp-job-progress-event-list-iter-start>

    <job-id>73188</job-id>

</dp-job-progress-event-list-iter-start>

[2014-08-05 18:13:03,318] DEBUG: <dp-job-progress-event-list-iter-next>

    <maximum>61</maximum>

    <tag>dpjobprogress124051_27923</tag>

</dp-job-progress-event-list-iter-next>

[2014-08-05 18:13:03,318] INFO: STORAGE-03021: Protection Manager backup progress get for job-id [73188] completed successfully

[2014-08-05 18:13:03,318] INFO: Protection Manager backup for job-id 73188 status is snapvault-progress! Sleeping 1 minute

[2014-08-05 18:14:03,364] INFO: STORAGE-03020: Getting Protection Manager backup progress for job-id [73188]

[2014-08-05 18:14:03,364] DEBUG: <dp-job-progress-event-list-iter-start>

    <job-id>73188</job-id>

</dp-job-progress-event-list-iter-start>

[2014-08-05 18:14:03,364] DEBUG: <dp-job-progress-event-list-iter-next>

    <maximum>61</maximum>

    <tag>dpjobprogress124052_30846</tag>

</dp-job-progress-event-list-iter-next>

[2014-08-05 18:14:03,364] INFO: STORAGE-03021: Protection Manager backup progress get for job-id [73188] completed successfully

[2014-08-05 18:14:03,364] INFO: Protection Manager backup for job-id 73188 status is snapvault-progress! Sleeping 1 minute

[2014-08-05 18:15:03,410] INFO: STORAGE-03020: Getting Protection Manager backup progress for job-id [73188]

[2014-08-05 18:15:03,410] DEBUG: <dp-job-progress-event-list-iter-start>

    <job-id>73188</job-id>

</dp-job-progress-event-list-iter-start>

[2014-08-05 18:15:03,410] DEBUG: <dp-job-progress-event-list-iter-next>

    <maximum>61</maximum>

    <tag>dpjobprogress124053_5245</tag>

</dp-job-progress-event-list-iter-next>

[2014-08-05 18:15:03,410] INFO: STORAGE-03021: Protection Manager backup progress get for job-id [73188] completed successfully

[2014-08-05 18:15:03,410] INFO: Protection Manager backup for job-id 73188 status is snapvault-progress! Sleeping 1 minute

[2014-08-05 18:16:03,472] INFO: STORAGE-03020: Getting Protection Manager backup progress for job-id [73188]

[2014-08-05 18:16:03,472] DEBUG: <dp-job-progress-event-list-iter-start>

    <job-id>73188</job-id>

</dp-job-progress-event-list-iter-start>

[2014-08-05 18:16:03,472] DEBUG: <dp-job-progress-event-list-iter-next>

    <maximum>61</maximum>

    <tag>dpjobprogress124059_13520</tag>

</dp-job-progress-event-list-iter-next>

[2014-08-05 18:16:03,472] INFO: STORAGE-03021: Protection Manager backup progress get for job-id [73188] completed successfully

[2014-08-05 18:16:03,472] INFO: Protection Manager backup for job-id 73188 status is snapvault-progress! Sleeping 1 minute

[2014-08-05 18:17:03,518] INFO: STORAGE-03020: Getting Protection Manager backup progress for job-id [73188]

[2014-08-05 18:17:03,518] DEBUG: <dp-job-progress-event-list-iter-start>

    <job-id>73188</job-id>

</dp-job-progress-event-list-iter-start>

[2014-08-05 18:17:03,518] DEBUG: <dp-job-progress-event-list-iter-next>

    <maximum>61</maximum>

    <tag>dpjobprogress124060_13246</tag>

</dp-job-progress-event-list-iter-next>

[2014-08-05 18:17:03,518] INFO: STORAGE-03021: Protection Manager backup progress get for job-id [73188] completed successfully

[2014-08-05 18:17:03,518] INFO: Protection Manager backup for job-id 73188 status is snapvault-progress! Sleeping 1 minute

[2014-08-05 18:18:03,564] INFO: STORAGE-03020: Getting Protection Manager backup progress for job-id [73188]

[2014-08-05 18:18:03,564] DEBUG: <dp-job-progress-event-list-iter-start>

    <job-id>73188</job-id>

</dp-job-progress-event-list-iter-start>

[2014-08-05 18:18:03,564] DEBUG: <dp-job-progress-event-list-iter-next>

    <maximum>61</maximum>

    <tag>dpjobprogress124061_5723</tag>

</dp-job-progress-event-list-iter-next>

[2014-08-05 18:18:03,564] INFO: STORAGE-03021: Protection Manager backup progress get for job-id [73188] completed successfully

[2014-08-05 18:18:03,564] INFO: Protection Manager backup for job-id 73188 status is snapvault-progress! Sleeping 1 minute

[2014-08-05 18:19:03,781] INFO: STORAGE-03020: Getting Protection Manager backup progress for job-id [73188]

[2014-08-05 18:19:03,781] DEBUG: <dp-job-progress-event-list-iter-start>

    <job-id>73188</job-id>

</dp-job-progress-event-list-iter-start>

[2014-08-05 18:19:03,781] DEBUG: <dp-job-progress-event-list-iter-next>

    <maximum>61</maximum>

    <tag>dpjobprogress124062_7415</tag>

</dp-job-progress-event-list-iter-next>

[2014-08-05 18:19:03,781] INFO: STORAGE-03021: Protection Manager backup progress get for job-id [73188] completed successfully

[2014-08-05 18:19:03,781] INFO: Protection Manager backup for job-id 73188 status is snapvault-progress! Sleeping 1 minute

[2014-08-05 18:20:03,837] INFO: STORAGE-03020: Getting Protection Manager backup progress for job-id [73188]

[2014-08-05 18:20:03,837] DEBUG: <dp-job-progress-event-list-iter-start>

    <job-id>73188</job-id>

</dp-job-progress-event-list-iter-start>

[2014-08-05 18:20:03,837] DEBUG: <dp-job-progress-event-list-iter-next>

    <maximum>61</maximum>

    <tag>dpjobprogress124063_16925</tag>

</dp-job-progress-event-list-iter-next>

[2014-08-05 18:20:03,837] INFO: STORAGE-03021: Protection Manager backup progress get for job-id [73188] completed successfully

[2014-08-05 18:20:03,837] INFO: Protection Manager backup for job-id 73188 status is snapvault-progress! Sleeping 1 minute

[2014-08-05 18:21:03,917] INFO: STORAGE-03020: Getting Protection Manager backup progress for job-id [73188]

[2014-08-05 18:21:03,917] DEBUG: <dp-job-progress-event-list-iter-start>

    <job-id>73188</job-id>

</dp-job-progress-event-list-iter-start>

[2014-08-05 18:21:03,917] DEBUG: <dp-job-progress-event-list-iter-next>

    <maximum>61</maximum>

    <tag>dpjobprogress124064_20147</tag>

</dp-job-progress-event-list-iter-next>

[2014-08-05 18:21:03,917] INFO: STORAGE-03021: Protection Manager backup progress get for job-id [73188] completed successfully

[2014-08-05 18:21:03,917] INFO: Protection Manager backup for job-id 73188 status is snapvault-progress! Sleeping 1 minute

[2014-08-05 18:22:03,996] INFO: STORAGE-03020: Getting Protection Manager backup progress for job-id [73188]

[2014-08-05 18:22:03,996] DEBUG: <dp-job-progress-event-list-iter-start>

    <job-id>73188</job-id>

</dp-job-progress-event-list-iter-start>

[2014-08-05 18:22:03,996] DEBUG: <dp-job-progress-event-list-iter-next>

    <maximum>61</maximum>

    <tag>dpjobprogress124065_11344</tag>

</dp-job-progress-event-list-iter-next>

[2014-08-05 18:22:03,996] INFO: STORAGE-03021: Protection Manager backup progress get for job-id [73188] completed successfully

[2014-08-05 18:22:03,996] INFO: Protection Manager backup for job-id 73188 status is snapvault-progress! Sleeping 1 minute

[2014-08-05 18:23:04,075] INFO: STORAGE-03020: Getting Protection Manager backup progress for job-id [73188]

[2014-08-05 18:23:04,075] DEBUG: <dp-job-progress-event-list-iter-start>

    <job-id>73188</job-id>

</dp-job-progress-event-list-iter-start>

[2014-08-05 18:23:04,075] DEBUG: <dp-job-progress-event-list-iter-next>

    <maximum>61</maximum>

    <tag>dpjobprogress124067_2534</tag>

</dp-job-progress-event-list-iter-next>

[2014-08-05 18:23:04,075] INFO: STORAGE-03021: Protection Manager backup progress get for job-id [73188] completed successfully

[2014-08-05 18:23:04,075] INFO: Protection Manager backup for job-id 73188 status is snapvault-progress! Sleeping 1 minute

[2014-08-05 18:24:04,154] INFO: STORAGE-03020: Getting Protection Manager backup progress for job-id [73188]

[2014-08-05 18:24:04,154] DEBUG: <dp-job-progress-event-list-iter-start>

    <job-id>73188</job-id>

</dp-job-progress-event-list-iter-start>

[2014-08-05 18:24:04,154] DEBUG: <dp-job-progress-event-list-iter-next>

    <maximum>61</maximum>

    <tag>dpjobprogress124068_8214</tag>

</dp-job-progress-event-list-iter-next>

[2014-08-05 18:24:04,154] INFO: STORAGE-03021: Protection Manager backup progress get for job-id [73188] completed successfully

[2014-08-05 18:24:04,154] INFO: Protection Manager backup for job-id 73188 status is snapvault-progress! Sleeping 1 minute

[2014-08-05 18:25:04,382] INFO: STORAGE-03020: Getting Protection Manager backup progress for job-id [73188]

[2014-08-05 18:25:04,382] DEBUG: <dp-job-progress-event-list-iter-start>

    <job-id>73188</job-id>

</dp-job-progress-event-list-iter-start>

[2014-08-05 18:25:04,382] DEBUG: <dp-job-progress-event-list-iter-next>

    <maximum>87</maximum>

    <tag>dpjobprogress124069_3611</tag>

</dp-job-progress-event-list-iter-next>

[2014-08-05 18:25:04,382] INFO: STORAGE-03021: Protection Manager backup progress get for job-id [73188] completed successfully

[2014-08-05 18:25:04,382] INFO: Protection Manager backup for job-id 73188 status is backup-create! Sleeping 1 minute

[2014-08-05 18:26:04,440] INFO: STORAGE-03020: Getting Protection Manager backup progress for job-id [73188]

[2014-08-05 18:26:04,440] DEBUG: <dp-job-progress-event-list-iter-start>

    <job-id>73188</job-id>

</dp-job-progress-event-list-iter-start>

[2014-08-05 18:26:04,440] DEBUG: <dp-job-progress-event-list-iter-next>

    <maximum>88</maximum>

    <tag>dpjobprogress124070_10549</tag>

</dp-job-progress-event-list-iter-next>

[2014-08-05 18:26:04,440] INFO: STORAGE-03021: Protection Manager backup progress get for job-id [73188] completed successfully

[2014-08-05 18:26:04,440] INFO: Protection Manager backup for job-id 73188 status is job-end! Sleeping 1 minute

[2014-08-05 18:27:04,467] INFO: Protection Manager backup for job-id 73188 completed successfully

########## POST DATA TRANSFER COMMANDS ##########

[2014-08-05 18:27:04,467] INFO: No commands defined

########## POST DATA TRANSFER COMMANDS FINISHED SUCCESSFULLY ##########

########## Running Snapshot copy Delete on Primary ##########

[2014-08-05 18:27:04,467] WARN: Snapshot copies will not be deleted, if this is not desired please set NTAP_SNAPSHOT_NODELETE=N in config file

########## POST NTAP COMMANDS ##########

[2014-08-05 18:27:04,467] INFO: No commands defined

########## NTAP COMMANDS FINISHED SUCCESSFULLY ##########

########## ARCHIVE COMMANDS ##########

[2014-08-05 18:27:04,467] INFO: Archive commands are not defined

########## Snap Creator Framework 4.0p1 finished successfully ##########

[2014-08-05 18:27:04,482] INFO: INFO: SnapCreator Backup completed successfully.

[2014-08-05 18:27:04,498] INFO: STORAGE-05016: Creating OM Event [script:information-event] on [10.205.225.140].

[2014-08-05 18:27:04,498] DEBUG: <event-generate>

    <event-name>script:information-event</event-name>

    <source>1</source>

    <event-message>SNAPCREATOR INFO: SnapCreator Backup completed successfully.(Config: CDCOLA2 Name: cdcola2 Policy: daily)</event-message>

</event-generate>

[2014-08-05 18:27:04,498] INFO: STORAGE-05017: OM Event [script:information-event] on [10.205.225.140] created successfully.

Re: SnapCreator not protecting (snapvault) relationship in OnCommand Dataset

I just stumbled upon something not correct, but so far I cannot figure out how to fix it.

If I go into the properties of the dataset, under physical primary resources, it shows items such as cdcfas02:/cdcola2_k/- and cdcfas02:/cdcola2_k/qo.  For l, it literally only shows cdcfas02:/cdcola2_l.  If I attempt to take that out and make it look like the rest, it tells me that it is going to delete my mirror.  On top of that, it's not really letting me add a /-, it shows as (non-qtree data). is that the same?

Thanks