Figure 4.54 Sync Subcommand Example – Pairsplit; Figure 4.55 Sync Subcommand Example – Pairsplit -S - Hitachi TAGMASTORE MK-90RD011-25 User Manual

The following examples show the sync subcommand used as an option of the pairsplit
command. For the example in Figure 4.54, the data remaining on logical drives C: and D: is
written to disk, all pairs in the specified group are split (status = PSUS), and read/write
access is enabled for all S-VOLs in the specified group.
pairsplit -x sync C: D: -g oradb -rw
Figure 4.54 Sync Subcommand Example – Pairsplit
For the example in Figure 4.55, the data remaining on physical devices harddisk2 and
harddisk3 is written to disk, all pairs in the specified group are deleted (status = SMPL),
which enables read/write access for all secondary volumes.
pairsplit -x sync hdisk2 hdisk3 -g oradb -S
Figure 4.55 Sync Subcommand Example – Pairsplit -S
Note: Sync has the following behavior on any conditions:
If the logical drives designated as the objects of the sync command will not be opened
to any applications, then sync flushes the system buffer to a drive and makes the
dismount state for this drive.
If the logical drives designated as the objects of the sync command are already opened
to any applications, then sync only flushes the system buffer to a drive.
This will be allowed to flush the system buffer before pairsplit without unmounting the
PVOL (opening state), and indicates as [WARNING] below:
pairsplit -x sync C:
WARNING: Only flushed to [\\.\C:] drive due to be opening
[SYNC] C: HarddiskVolume3
Note: Syncd has the following behavior as well:
If the logical drives designated as the objects of the sync command will not be opened
to any applications, then syncd flushes the system buffer to a drive and waits (30 sec)
the delayed (paging) IO for dismount after made the dismount state about the drive.
This avoids a problem that NTFS on PVOL will be split on inconsistent state because
Windows 2003 delays the IO for dismounting.
274 Chapter 4 Performing CCI Operations