Remote Seeding for the Linux Platform
The procedure in this section illustrates how to seed a NetApp storage system for use with a primary node’s initial base backup in the Linux environment.
The seeding process requires the following components:
master server
Use the management console on the master server to coordinate backup and restore activity.
(Linux) primary node
The source for the base Image backup.
Tape Library
To record the base Image backup to tape for physical transport.
(Linux) spare client
A spare Linux machine added to the Enterprise that is local to the NetApp storage system.
NetApp storage system
The final destination for the restoration of the base Image backup data, and all subsequent incremental backups.
Remote seeding is a multi-step process. Carefully track relevant behavior and record significant identification data along the way, as required for running the full process, as shown in the following table:
| Machine Type(Linux) | Logical Node Name Within Enterprise | Volume Label | Hostname/IP Address | OS |
|---|---|---|---|---|
master server | master | N/A | QASATAS | Windows |
primary node | linux.client | N/A | rh55-233 | Red Hat |
spare client | linux.spare | rh55-231 | Red Hat | |
NetApp storage system | qa-f270b |
| qa-f270b | N/A |
At the primary site perform the following procedures:
At the destination site perform the following procedures:
Note that DPX agent-based Block backup from a Linux client to a NetApp Clustered Data ONTAP target uses iSCSI protocol. Support for remote locations is limited.
See also. For the latest system compatibility details regarding supported hardware, file systems, applications, operating systems, and service packs, see the Compatibility Guide.
Last updated