Data Protection
351
Titan SiliconServer
5.
To define a new starting date and time for the selected schedule, click
re-schedule
and
enter the new values in the appropriate fields.
6.
To change the schedule’s interval, configure the schedule to repeat either daily, weekly,
or monthly, or configure the schedule to run
Continuously, Once Only.
Select
Inactive
to pause a replication job.
7.
Click
OK
to apply the changes or
cancel
to discard them, and return to the
Replication
page.
Note:
A replication job cannot be started if a previous instance of the same
job is still in progress. In this case, the replication is skipped, and an error is
logged.
Scheduling Incremental Replications
Incremental replications rely on the existence of the snapshot taken during the previous
replication. If this snapshot no longer exists, the data management engine has to perform a full
replication. The data management engine automatically preserves the snapshots it needs for
replication. However, replication-defined snapshots are purged after 7 days (configurable to 40
days via "Replication Schedule"). A full replication could occur in the following scenarios:
•
"Periodic" or "Once Only" schedule but not running frequently (waiting 8 or more days
between replication runs could result in a full replication).
•
Deleting the schedule of policy and then rescheduling at a much later date (the
snapshots will have been purged when the schedule is deleted).
•
Scheduling a "Date of Final Run", then re-using the schedule/policy weeks after the final
run finished (the snapshots will have been purged after the "final run").
The schedule section shows the age of the snapshot to be used for replication. If the snapshot
doesn't exist, then indicates that a 'full replication' is performed.
Replication Status & Report
The
Replication Status & Reports
page displays a list of replication jobs that are in progress or
that have been completed. Replication Reports also includes a number of reporting details on
files replicated, amount of data replicated, success or failure status, etc. If a schedule is deleted,
the reports associated with it are also deleted.
The replication report Status column displays the results of the replication job (successful or
failed). Reports can also be beneficial for analyzing the effects of a particular incremental
replication policy. This is particularly true when replicating across a WAN by viewing the Report
Summary page. The information contained in the Report Summary provides a detailed view of
the replication job results. This information can be used to make adjustments in the replication
policy and schedule that can improve the overall replication efficiency.
Содержание Titan SiliconServer
Страница 1: ...Titan SiliconServer System Administration Manual ...
Страница 12: ...Table of Contents xii Titan SiliconServer ...
Страница 308: ...File Services 296 Titan SiliconServer 4 Click OK To access available iSCSI Targets 1 Click on the Available Targets tab ...
Страница 411: ...Status Monitoring 399 Titan SiliconServer 3 Click details ...