This example shows the results of protection jobs using the default time zone for the protection schedules.
The following actions occur, assuming the replication jobs all succeed:
- The NetApp Management Console data protection capability interprets the Daily local backup job in the time zone of the DataFabric Manager server, therefore, the backup starts at 1:00 p.m. Monday, Lagos time (8:00 p.m. Hong Kong time).
- The NetApp Management Console data protection capability interprets the Daily remote backup job in the time zone of the DataFabric Manager server, therefore, the remote backup starts at 4:00 p.m. Monday, Lagos time (11:00 p.m. Hong Kong time). The NetApp Management Console data protection capability starts the backup, replicating primary data in Nigeria to backup destination storage in Los Angeles.
- The NetApp Management Console data protection capability interprets the Weekly mirror copy job in the time zone of the DataFabric Manager server, therefore, remote mirroring starts at 2:30 a.m. Monday, Los Angeles time (6:30 p.m. Hong Kong time). The NetApp Management Console data protection capability mirrors the data, replicating the backed-up data on the secondary storage in the U.S. to tertiary storage in Lima.
The location and time zone of the tertiary destination storage does not impact the schedule.