Views:

Summary

 


Seeding process Using NetApp Storage System

 

 

SnapVault Seeding - Using a NetApp Storage System

 

 

Introduction

The following procedure outlines the steps to use an intermediary (or mobile) NetApp storage system to provide a client node’s initial base backup to a local SV secondary that can then be initialized to a centralized NetApp storage system through SnapMirror. Afterwards, block-level incremental can continue to run from these remote clients to the central NetApp Storage system. 
 
  
 
 
 

Procedure

  1. Scan the intermediary NetApp storage system into your enterprise through the Configure > Enterprise window of the management console. 

 

  1. Create a new volume on the intermediary NetApp storage system which will store the initial base snapshots for your remote clients. For each DPX job defined, you must define a separate volume.

 

  1. Define a Block backup to NetApp Storage job for your DPX clients and schedule these jobs to go to their respective volumes on the intermediary NetApp storage system. 

 

  1. If required, physically transport the intermediary NetApp storage system to the central location and attach it to the network. 

 

  1. Create new volumes on the central NetApp that will act as SnapMirror destinations for the source volumes you initially backed up to in step 2. 

 
Note: The volume names on both NetApp devices do not need to be the same.
 

  1. Perform a SnapMirror initialization between the intermediary and central NetApp volumes. 

 

  1. Quiesce and break the SnapMirror relationship once the transfer completes.

 

  1. Ensure that no DPX jobs are running on your master server. Close the management console and stop the DPX CMagent service. 

 

  1. Open a registry editor on the DPX master server and modify the registry settings for HKLM > Software > Syncsort > BackupExpress > {MasterServerName} > 0 > SSSVH. If you do not see a string with the name SSSVH, create this new string value.

 
a. Append “–xnocheck 2” to SSSVH the data value. 

  
 


WARNING: The -xnocheck flag bypasses underlying DPX functionality which validates the SnapVault relationship between the DPX client node and NetApp. Use this flag only as directed by this document or through the guidance of Catalogic Software Support/Services personnel. Failure to remove this flag upon completion of this procedure may produce unintended side effects or result in backup/restore failures in the future. 
 

  1. Restart the DPX CMAgent service and log in to the management console. Load the original job definition you created in step 3 and reconfigure the destination volumes to point to the mirrored volumes located on the central NetApp storage system. Resave the job definition using the original job name. 

CAUTION: Take care when reconfiguring nodes or tasks to point to the new volume. Simply selecting a new volume destination may only change the destination for the selected task that is in focus. To ensure that each object will go to the new destination volume, right click on each object selected in your backup job definition source pane and select View Destination from the context menu and ensure that this particular object is pointing to the correct destination volume. 

  1. Remove from Master Server machine corresponding DSL file. Remove SSPRODIR\db\tmp\sv-<ClientNameHere>.*.dsl file – this will ensure that condense job following resaved Job with the new destination volume will Not reset CJ on the Client.
  2. Run your backup job. When running you will notice the following warning in the job monitor, immediately followed by the first task failure. Disregard the initial task failures. Upon retry of these tasks, the incremental will be transferred to the newly designated central NetApp destination. 

SNBSVH_092W DEVDEBUG: BASE_INCR_MISMATCH check bypassed due to user option
SNBNCJ_103E Message: Task 1 NDMP_LOG: id(2), type(NDMP_LOG_ERROR), text(Qtree /vol/<volume_name>/[<jobname>]<masterservername> @{diskid} is already a replica. )

  1. Confirm that an incremental transfers and you are able to restore from that snapshot. 
  2. Remove the –xnocheck 2 parameter from the SSSVH string value in the registry and restart the DPX CMAgent service on the master server. 
  3. You can delete the SnapMirror relationship between the central and intermediary NetApp storage system.
  4. You can also delete the volume on the intermediary NetApp storage system that contained the initial base snapshots for your remote clients.