Chapter 31: Remote Seeding with NetApp Storage

For remote data protection (for example, of a branch office), it can be a challenge to perform an initial base backup if the source primary system contains a large amount of data and is to be backed up over a slow communication link.

The Remote Seeding function solves this problem. It allows for remote block-level backups over very slow connections that would normally take a prohibitive amount of time. The process involves a base backup to a locally attached tape or portable hard drive. The media is then transferred through physical delivery (for example, FedEx, UPS, etc.) to a site running a NetApp storage system. This base backup is then restored to the NetApp storage system, after which incremental backups continue over the slow Internet connection. Once the first incremental backup is complete, the data is available for recovery.

Consider the following example. From the company headquarters in City A, an administrator wants to back up a node in a small office to a server at the headquarters in City B. Over a robust Internet connection, such a backup is handled using normal backup procedures, regardless of physical location. However, the City B office has a slow upload speed. A conventional backup ties up this connection for several days and would probably fail, due to the likelihood of service interruptions over a long period. Instead, the administrator uses the Remote Seeding process.

Using the management console from his office in City A, the administrator initiates a seeding backup job, chooses the remote node to back up and a remote backup device (at the same location as the source node, in this case, City B). Once the base backup is complete, the administrator arranges for the media to ship to City A, where he initiates a seeding restore job and restores the media to a NetApp storage system. Once that restore job is complete, Catalogic DPX continues running incremental backups from the source node in City B to the NetApp storage system in City A over the slow connection.

The backup media is typically tape, but a portable or removable hard drive; even a laptop or NetApp storage system can be used.

The following diagram illustrates a sample scenario.

Seeding Stage 1

A base backup to directly attached media followed by the transport of that media to a NetApp storage system location.

Seeding Stage 2

Restore of the base backup to a NetApp storage system.

After Seeding

Automatic incremental block-level backups over a slow internet connection.

Remote Seeding is a multi-step process that is platform dependent. If you are using a release of earlier than DPX 4.2, use the remote seeding process described in knowledge base article 42036.

To use a mobile NetApp storage unit to seed a source NetApp volume to a destination NetApp volume, use the process described in knowledge base article 46085 or 46087.