Subscribe

Vaulting vfiler backups with Protection Manager

[ Edited ]

Hi,

I've been trying to get vaulting of a vfiler with Oracle data on it's volumes to work but no backups were ever registered in Protection Manager so PM never knew there was anything to protect.I had referenced the vfiler using it's IP address - for NTAP_USERS, VOLUMES and NTAP_DFM_DATA_SET.

Once I went into the config and changed the IP address to the vfiler hostname, vaulting started working. Backups gets registered and are then vaulted per the Protection Policy in PM.

Is this a known limitation? That vfilers must be referenced to by hostname rather than IP?

Here's from the debug logs when creating a backup and it's apparent some info is missing in the failing one:

Failing:

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

[2014-08-13 13:47:48,020] INFO: STORAGE-05004: Creating NetApp Management Console driven backup of dataset [snapcreator_rp_sc_test].

[2014-08-13 13:47:48,020] INFO: STORAGE-04104: Creating NetApp Management Console Backup Version for volume [vn10xx_teo_test_techflex_jul_oradata] dataset [snapcreator_rp_sc_test]

[2014-08-13 13:47:48,020] TRACE: Dataset Member vn10xx:/vn10xx_teo_test_techflex_jul_oradata/- and controller 10.243.4.9 volume vn10xx_teo_test_techflex_jul_oradata did not match, skipping!

[2014-08-13 13:47:48,020] TRACE: Dataset Member netappbbbb:/snapcreator_rp_sc_test_backup_netappaaaa_vn10xx_teo_test/- and controller 10.243.4.9 volume vn10xx_teo_test_techflex_jul_oradata did not match, skipping!

[2014-08-13 13:47:48,020] DEBUG: <dp-backup-version-create>

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

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

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

        <version-timestamp>1407926853</version-timestamp>

        <version-members>

                <version-member-info>

                        <snapshot-unique-id>1407926853</snapshot-unique-id>

                        <snapshot-name>tech_sc_test-daily_20140813134703</snapshot-name>

                        <volume-name>10.243.4.9:/vn10xx_teo_test_techflex_jul_oradata</volume-name>

                        <snapshot-contents/>

                </version-member-info>

        </version-members>

</dp-backup-version-create>

Passing:

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

[2014-08-13 15:03:27,305] INFO: STORAGE-05004: Creating NetApp Management Console driven backup of dataset [snapcreator_rp_sc_test].

[2014-08-13 15:03:27,305] INFO: STORAGE-04104: Creating NetApp Management Console Backup Version for volume [vn10xx_teo_test_techflex_jul_oradata] dataset [snapcreator_rp_sc_test]

[2014-08-13 15:03:27,305] INFO: STORAGE-05015: Added member [vn10xx:/vn10xx_teo_test_techflex_jul_oradata/-] of dataset [snapcreator_rp_sc_test] to NetApp Management Console backup version.

[2014-08-13 15:03:27,305] TRACE: Dataset Member netappbbbb:/snapcreator_rp_sc_test_backup_netappaaaa_vn10xx_teo_test/- and controller vn10xx volume vn10xx_teo_test_techflex_jul_oradata did not match, skipping!

[2014-08-13 15:03:27,305] DEBUG: <dp-backup-version-create>

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

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

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

        <version-timestamp>1407931398</version-timestamp>

        <version-members>

                <version-member-info>

                        <snapshot-unique-id>1407931398</snapshot-unique-id>

                        <snapshot-name>tech_sc_test-daily_20140813150251</snapshot-name>

                        <volume-name>vn10xx:/vn10xx_teo_test_techflex_jul_oradata</volume-name>

                        <snapshot-contents>

                                <snapshot-member-info>

                                        <primary-name>vn10xx:/vn10xx_teo_test_techflex_jul_oradata/-</primary-name>

                                </snapshot-member-info>

                        </snapshot-contents>

                </version-member-info>

        </version-members>

</dp-backup-version-create>

Thanks in advance,

Erik Stjerna

Re: Vaulting vfiler backups with Protection Manager

I'm not an official source, but I was previously running cascades and vaults through PM with vfilers. Yes you have to use the vfiler name, not ip. The dataset in protection manager must also reference the vfiler name, not vfiler0. There was also a trick when you could set the MANAGEMENT_INTERFACES to vfiler0's hostname so SC would send api calls to vfiler0, but still have the vfiler name so protection manager integration would still work.

Thanks,

--

Chris