SnapProtect - SnapProtect for Open Systems - Best Practices - NetApp

Review the following best practices before using the SnapProtect for Open Systems 7-Mode or C-Mode.
  • Run SPOS or SPOS C-Mode jobs from the workflow alone. This ensures that data from all the subclients that are associated with the same SPOS or SPOS C-Mode 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 SPOS job or a SPOS C-Mode 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 the workflow immediately before and after any configuration change is done to any subclient associated to the same SPOS storage policy. A configuration change might 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 subclient content
    • Deletion of subclient content – Removing a source volume from subclient content
    • Addition of a new subclient - Adding a new subclient to a SPOS enabled storage policy or re-associating a subclient to a SPOS storage policy
    • Deletion of subclient – Deleting a subclient
  • Group subclients with similar application types together in each SPOS or SPOS C-Mode 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 to OCUM.
  • For File System agents: by default, the system state data is backed up along with the file system data by the default subclient. Backing up the system state is not supported by SPOS or SPOS C-Mode, hence backing up the default subclient with SPOS or SPOS C-Mode enabled storage policy is not supported. Do not associate default subclients with SPOS or SPOS C-Mode enabled storage policy.
  • It is recommended to add complete volume/drive letter/mount paths as subclient content since SPOS or SPOS C-Mode does full volume block level incremental backup during every backup.
  • Avoid using SPOS C-Mode storage policy with client running versions earlier than 11.0. Jobs will fail since the clients send 7-Mode OCUM messages to C-Mode OCUM server.
  • NFS, HTTP, and HTTPS ports for the destination vServer, that is, the vServer to which SPOS C-Mode data is replicated to must be accessible via any firewall configuration.