43
Figure 36. Creating a new remote snapshot
4. Set the Recurrence time (in minutes, hours, days, or weeks).
Consider the following:
– Ensure you leave enough time for the previous snapshot to complete.
– Ensure there is adequate storage space at both sites.
– Set a retention policy at the primary site based on a timeframe or snapshot count.
5. Select the Management Group for the remote snapshot.
6. Create a remote volume as the destination for the snapshot.
Based on the convention used in this document, name the target Remote-XPSP2-02.
7. Set the replication level of Remote-XPSP2-02
8. Set the retention policy for the remote site. .
Depending on the scheduled start time, replication may now commence.
The first remote snapshot copies all your data – perhaps many terabytes – to the remote cluster.
To speed up the process, you can carry out this initial push on nodes at the local site, then physically
ship these nodes to the remote site
6
. For more information, refer to the support documentation
After the initial push, subsequent remote snapshots are smaller – only transferring changes made since
the last snapshot – and can make efficient use of a high-latency, low-bandwidth connection.
6
The physical transfer of data – in this case, a storage cluster or SAN that may be carrying many terabytes of data – is known as sneakernetting.
