When you integrate SnapManager with datasets and SnapVault, some limitations exist with dataset configuration, retention policies, Business Continuance, and verification.
- You cannot perform remote backup and archiving operations without dataset configuration.
- You cannot control the archived backup retention policy by using SnapManager.
Archived backup retention policies are controlled by Protection Manager.
- You cannot use SnapManager to create and manage datasets for disaster recovery or business continuance.
- SnapManager does not support LUNs residing on one qtree.
- SnapManager does not support LUNs that do not reside on a qtree.
- SnapManager does not support verification of an archived backup copy on secondary storage after a backup operation is complete.
- After you apply a dataset policy, you cannot change it using SnapManager.
If you want to change a dataset policy, then change it using Protection Manager, which automatically updates the policy in SnapManager as well.
