SnapProtect - SnapProtect for Open Systems - Best Practices - NetApp

Review the following best practices before using the SnapProtect for Open Systems feature.
  • Run SnapProtect for Open Systems jobs from the workflow alone. This ensures that data from all the subclients that are associated with the same SnapProtect for Open Systems policy get backed up at the same time and consume a single snapshot on the destination filer volume. The workflow sets up interdependencies between individual subclient jobs, so the subclient that takes the longest time to complete is going to add delays to the running time of the other subclient jobs. This delay is inherent to the nature of the workflow.
  • Running a SnapProtect for Open Systems job from a subclient is supported but not recommended. Doing so will cause the subclient to consume a snapshot just for itself on the destination filer.
  • Run a workflow job immediately before and after any configuration change is done to any of the subclients that are associated with the same SnapProtect for Open Systems storage policy. A configuration change may cause the dataset that corresponds to the SnapProtect for Open Systems storage policy to get non-conformant, thus causing failures in any jobs that are run subsequently (i.e., without running the workflow first) from the subclient level. Examples of configuration changes:
    • Addition of subclient content – Adding a new source volume to a subclient content
    • Deletion of subclient content – Removing a source volume from subclient content
    • Addition of a new subclient - Adding a new subclient to a SnapProtect for Open Systems enabled storage policy or re-associating a subclient to a SnapProtect for Open Systems storage policy
    • Deletion of subclient – Deleting a subclient
  • Group subclients with similar application types together in each SnapProtect for Open Systems enabled storage policy. For example, group SQL agents into one storage policy, Oracle into another.
  • Unless the workflow job is the next job to run whenever a new volume is added to any subclient associated with the storage policy, any jobs that are run from of the associated subclients will fail because the dataset will not get conformant on the OnCommand Unified Manager end.
  • For the File System agents: by default, system state data is backed up along with file system data by the default subclient. Backing up system state is not supported by SnapProtect for Open Systems, hence backing up the default subclient with a SnapProtect for Open Systems enabled storage policy is not supported. Do not associate default subclients with any SnapProtect for Open Systems enabled storage policy.
  • It is recommended to add complete volume/drive letter/mount paths as subclient content since SnapProtect for Open systems does full volume block level incremental backup during every backup job.