Skip to end of metadata
Go to start of metadata

The Server Backup Replication has four stages:

1. Snapshot of the Disk or Volume
A point-in-time online snapshot of the server's file system is created.

2. Exclude Files/Folders
At this stage, you can choose which files/folder will be excluded from the replication.
If you exclude files by pattern (e.g. ".log"), this process will take longer as each file name must be examined against the pattern (e.g. ".log"). You can save time by excluding entire folders rather than single files. The Backup Manager will give you a progress indicator showing you how much time has elapsed excluding files/folders.

3. Copy Deltas or Perform Initial Replication
At this stage, the deltas are saved to the Disk Safe a new Recovery Point is created.

4. Merging Recovery Points
If the total number of Recovery Points exceeds the Recovery Points limit when a new Recovery point is created, the old Recovery Points will be automatically merged. This process sometimes requires a considerable amount of time, especially if the Recovery Points to be merged are large.

Although this stage is not displayed in the Task History, the Replication is finished only after the old Recovery Points have been merged.

To view the ID of the merged Recovery Point, access the Task History for the current policy and click the _Merged Recovery Points _tab.

Replication Types

The Server Backup Replication has three types:

1. Initial Replica
This replica is created once for each new device you save to a Disk Safe. During the Initial Replica, all information from the disk (except for the files/folders you have excluded) is copied to the Disk Safe and forms the first Recovery Point. This usually requires some time. To learn more about this process, refer to Virtual Full Backups.

2. CDP Replication
During Replication, the Backup Agent installed on the Host tracks which block-level deltas have changed on the target replication device since the last Recovery Point and copies them to the Disk Safe. This process doesn't take long. To learn more, refer to Computing Deltas.

3. Full Block Scan
Sometimes the Backup Agent must perform a full block scan replication of the device. This procedure is required to get the asynchronous CDP replications back in sync. During the scan, every allocated block in the file system must be read from disk. Its MD5 check sum is computed and compared to the checksum in the last completed Recovery Point. This process takes much longer than the CDP Replication.

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.