Data Backup and Recovery

Problem with NTAP_PM_UPDATE SC 3.4.0 and Protection Magnager of OnCommand 5.0

f_duranti
6,465 Views

Hi, I'm setting up a new backup from SC 3.4.0 with Protection Manager integration but it seems that I've some problem with this. The backup is composed of 8 volumes snapmirrored on a secondary filer.

This is what I've done:

1) Create a Dataset with pmsetup (then I've renamed it for our naming convention)

2) Create a primary (NFS) and secondary provisioning policy

3) Create a protection policy (it just have the lag time and no schedule because I'll schedule from cron with SC)

4) Create a resource pool for primary and secondary storage

5) Assigned the original volume to the primary storage, assigned the provisioning policy, the protection policy and the resource pool

6) OnCommand created the secondary volume with my naming convention and initialized the snapmirror relationship

At this point I create a backup with snapcreator --action snap

I'm expecting that in the Dataset, selecting the Dataset, in the "Primary Data", Backup Version I should see the button to see backup of this dataset and the date of the last backup but There's nothing and after the snapshot policy lag time the dataset go in error.

Going on the provision tab on a volume and on the detele snapshot to see the snapshot of the volume I see them as normal and not as "Backup" as they should be.

Checking the log SC says that it has registered the backup correctly but it's not visible.

I've an older test configured that was working correctly but I cannot find what can be wrong.

This is part of the config file that is not working:

CONFIG_TYPE=STANDARD

USE_PROXY=N

NTAP_CONSISTENCY_GROUP_WAFL_SYNC=N

NTAP_SNAPSHOT_RESTORE_AUTO_DETECT=N

SNAME=BCK

SNAP_TIMESTAMP_ONLY=N

VOLUMES=itnapfs20:DSR_Data,DSR_Log,DSR_Temp,DSR_Exe,DJR_Data,DJR_Log,DJR_Temp,DJR_Exe

NTAP_SNAPSHOT_RETENTIONS=daily:7

NTAP_USERS=itnapfs20:user/pw

NTAP_PWD_PROTECTION=Y

TRANSPORT=HTTPS

PORT=443

LOG_NUM=10

SC_TMP_DIR=

########################

### Snapshot Options ###

########################

NTAP_SNAPSHOT_RETENTION_AGE=7

SNAPDRIVE=N

SNAPDRIVE_DISCOVERY=N

NTAP_SNAPSHOT_DISABLE=N

NTAP_SNAPSHOT_NODELETE=Y

NTAP_CONSISTENCY_GROUP_SNAPSHOT=Y

NTAP_CONSISTENCY_GROUP_TIMEOUT=relaxed

NTAP_SNAPSHOT_DELETE_BY_AGE_ONLY=N

NTAP_SNAPSHOT_DEPENDENCY_IGNORE=Y

##########################

### SnapMirror Options ###

##########################

NTAP_SNAPMIRROR_UPDATE=N

NTAP_SNAPMIRROR_CASCADING_UPDATE=N

SNAPMIRROR_VOLUMES=

SNAPMIRROR_CASCADING_VOLUMES=

NTAP_SNAPMIRROR_WAIT=0

NTAP_SNAPMIRROR_USE_SNAPSHOT=N

NTAP_SNAPMIRROR_MAX_TRANSFER=

##################################

### Protection Manager Options ###

##################################

NTAP_PM_UPDATE=Y

NTAP_DFM_DATA_SET=itnapfs20:SC_SAP_SRM_Dev/DSR_Data,DSR_Log,DSR_Temp,DSR_Exe,DJR_Data,DJR_Log,DJR_Temp,DJR_Exe

NTAP_PM_RUN_BACKUP=Y

###################################

### Operations Manager Settings ###

###################################

OM_HOST=itromlx13.q8int.com

OM_USER=root

OM_PWD=pw

OM_PORT=8488

OM_EVENT_GENERATE=Y

This is the part of the log with the PM Update:

########## Running NetApp Protection Manager Backup Version Create for dataset SC_SAP_SRM_Dev ##########

[Fri Aug 12 04:32:06 2011] INFO: Registering snapshot BCK-daily_recent with Protection Manager dataset SC_SAP_SRM_Dev

[Fri Aug 12 04:32:06 2011] DEBUG: ZAPI REQUEST

<dp-backup-version-create>

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

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

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

        <version-timestamp>1313116263</version-timestamp>

        <version-members>

                <version-member-info>

                        <snapshot-unique-id>1313116263</snapshot-unique-id>

                        <snapshot-name>BCK-daily_recent</snapshot-name>

                        <snapshot-contents></snapshot-contents>

                        <volume-name>itnapfs20:/DSR_Data</volume-name>

                </version-member-info>

                <version-member-info>

                        <snapshot-unique-id>1313116263</snapshot-unique-id>

                        <snapshot-name>BCK-daily_recent</snapshot-name>

                        <snapshot-contents></snapshot-contents>

                        <volume-name>itnapfs20:/DSR_Log</volume-name>

                </version-member-info>

                <version-member-info>

                        <snapshot-unique-id>1313116263</snapshot-unique-id>

                        <snapshot-name>BCK-daily_recent</snapshot-name>

                        <snapshot-contents></snapshot-contents>

                        <volume-name>itnapfs20:/DSR_Temp</volume-name>

                </version-member-info>

                <version-member-info>

                        <snapshot-unique-id>1313116263</snapshot-unique-id>

                        <snapshot-name>BCK-daily_recent</snapshot-name>

                        <snapshot-contents></snapshot-contents>

                        <volume-name>itnapfs20:/DSR_Exe</volume-name>

                </version-member-info>

                <version-member-info>

                        <snapshot-unique-id>1313116263</snapshot-unique-id>

                        <snapshot-name>BCK-daily_recent</snapshot-name>

                        <snapshot-contents></snapshot-contents>

                        <volume-name>itnapfs20:/DJR_Data</volume-name>

                </version-member-info>

                <version-member-info>

                        <snapshot-unique-id>1313116263</snapshot-unique-id>

                        <snapshot-name>BCK-daily_recent</snapshot-name>

                        <snapshot-contents></snapshot-contents>

                        <volume-name>itnapfs20:/DJR_Log</volume-name>

                </version-member-info>

                <version-member-info>

                        <snapshot-unique-id>1313116263</snapshot-unique-id>

                        <snapshot-name>BCK-daily_recent</snapshot-name>

                        <snapshot-contents></snapshot-contents>

                        <volume-name>itnapfs20:/DJR_Temp</volume-name>

                </version-member-info>

                <version-member-info>

                        <snapshot-unique-id>1313116263</snapshot-unique-id>

                        <snapshot-name>BCK-daily_recent</snapshot-name>

                        <snapshot-contents></snapshot-contents>

                        <volume-name>itnapfs20:/DJR_Exe</volume-name>

                </version-member-info>

        </version-members>

</dp-backup-version-create>

[Fri Aug 12 04:32:06 2011] DEBUG: ZAPI RESULT

<results status="passed">

        <backup-id>3743</backup-id>

</results>

[Fri Aug 12 04:32:06 2011] INFO: Snapshot BCK-daily_recent for dataset SC_SAP_SRM_Dev registered with Protection Manager successfully

1 ACCEPTED SOLUTION

ktenzer
6,464 Views

In theory oncommand should use name of filer so what you see when you logon to filer. When you add filer oncommand doesnt give option to specify name.

The only thing I can think of atm to change name is use oncommand cli. The "dfm host" command maybe do a "dfm host help", maybe there is option to change name? If that doesnt work maybe an NGS case, they might have a trick or two to help.

Let us know if you find solution

Have good weekened

Keith

View solution in original post

10 REPLIES 10
Public