American Megatrends ManageTrends 2.7, Руководство пользователя

Страница: 299 / 367

Appendix E : Replication Overview 281
When JAR is in ‘Snapshot mode’, it will check journal file upon completion of each
snapshot based replication to see whether it can fall back to Journal based replication.
Journal based replication can be done only when a snapshot event is exists (in Journal
File) for a completed snapshot. If so, JAR can replicate IO from the completed snapshot
event and change its replication mode to ‘Journal based’.
Once JAR is created, further JAR management like Fail Over, Fail Back Join, Fail Back,
Roll Back, etc are all similar to SAR management. Refer Snapshot Replication section.
CLI: A JAR can be created using ITX 2.7 CLI interface.
For example:
cli create -t jar –n jar0 –f 0 –a StoragePool1 –l privol0 –l privol1 –i
172.16.70.60 –s RemotePool0 –r SecReplVol0 –r SecReplVol1 -m 172.16.70.84 –p
25 –z 24 –e asyncreplica
Where, -t represents Replication type <jar>, -n represents name of the JAR (or CG), -a
represents local container, -l represents local volume, -i represents local IP, -s represents
remote container, -r represents remote volume name, -m represents remote IP, -z
represents maximum snapshot that can be maintained in remote replication and –e
represents encryption (optional).
For detail list of CLI commands, see the
StorTrends iTX 2.7 CLI User Guide .