7065Admin_Configure.fm
Draft Document for Review August 30, 2007 12:59 am
180
IBM System Storage DS3000: Introduction and Implementation Guide
Figure 8-62 FlashCopy - Complete
In the example just shown in Figure 8-61, the FlashCopy logical disk is made available to the
Host x3755_Colorado. This enables the Host x3755_Colorado to access and mount the
FlashCopy’d disk as part of its own file system.
It is possible to map the FlashCopy logical disk to the same server that owns the base logical
disk. However, note that the two logical disks, immediately after creating the FlashCopy,
appear exactly the same (a block-by-block copy). Many operating systems do not tolerate
seeing an exact duplicate volume. In Windows, for example, when a FlashCopy source logical
drive is a dynamic disk, the FlashCopy source and target logical drive will get the same
DiskID in Logical Disk Manager (LDM) which will cause problems. When the FlashCopy
source logical drive is a basic disk, FlashCopy source and target logical drives will get the
same disk signature. We recommend to map the FlashCopy destination logical drive to a
different host.
For more information about Windows disk best practices, see the Microsoft Web site:
http://support.microsoft.com/kb/816307/en-us
Continue to “Step 3: Restart host application” on page 183.
Create Logical Drives - Advanced
1. For more control over the FlashCopy logical drive, select Advanced from the Select Path
view (Figure 8-63) and click Next.
Important: If you use a FlashCopy drive regularly (for example, for backup purposes), use
the Disable FlashCopy and Re-create FlashCopy options to reuse the FlashCopy
repository logical drive as in “Create Logical Drives - Advanced” on page 180. Using these
options preserves the existing mappings to the FlashCopy logical drive.