Define a Block Incremental Backup Job

Before running the Image restore, a Block backup job must be defined to initialize aspects of the seeding process. To define Block incremental backups:

1. Launch the management console.

2. Define and save a new Block incremental backup job to back up all selected volumes to their destination NetApp storage systems. This will become the block incremental backup job that runs across the slow communication link. This job will be scheduled later in the process.

Note. The best practice is to define a new Block backup job. If a previously used Block backup job name must be used, it is critical that all the backup instances have expired and no base snapshot is needed to be kept as a recovery point. If that is the case, delete the job and run a Catalog condense. Otherwise, you should use a new Block backup job name.

Additionally, if a previously used Block backup job name must be used, no qtree relationship should remain on the NetApp storage system. To ensure this, run the following command on the filer:

snapvault status -l <netappname>:/vol/<volumename>/<qtreename>, where the qtreename consists of [blockbackupjobname]sourceclientnodename@{volumeserialnumber}.

In the preceding command, the names used must be consistent with the names used in the Block backup definition and on the client. Obtain the volumeserialnumber by issuing dir vol from the source client, and removing the dashes from the volumeserialnumber.

If the output indicates SnapVault is ON followed by detailed information about Source, Destination, Status, etc., then there is still a qtree relationship and the remote seeding process might not succeed, in which case you should use a new Block backup job name. If the output indicates only SnapVault is ON, then there is no qtree relationship and you can proceed.