Windows Knowledge Base

[EMC Clariion]How to Ensure consistent fracture of clones?

Follow the procedure below:
1. Put your application/database in Hot Backup mode.
2. From the production host, stop I/O to the source LUN, and  flush all cached data written to the source LUN by issuing the appropriate command for your operating system.

? For a Windows host, use the admsnap flush command.
? For Solaris, HP-UX, AIX, and Linux hosts, unmount the file system by issuing the unmount command. If you are unable to unmount the file system, issue the admsnap flush command.

3. Using Navisphere from any client that is managing the storage system, do the following:

a). From the Storage tab of the Enterprise Storage dialog box, navigate to the Clones icon, and then to the Clone Group Name icon(s).
b). Right-click the Clone Group Name icon that contains the clone you want to fracture and select Properties.
c). Select the Clone tab for the clone you want to fracture and verify that its state is Synchronized. If its state is not Synchronized, you must wait until it is Synchronized before closing the dialog box and continuing to the next step. The state of the clone may also be Consistent. However, if you fracture a clone in a Consistent state, the clone does not contain the most up-to-date information from its source LUN. This is because the source LUN receives host I/O that has not been copied to the clone.
d). Double-click the Clone Group Name icon that contains the clone you want to fracture.
e). Right-click the clone you want to fracture, and select Fracture. A "Confirm: Fracture Clone" dialog box opens.
f). Click Yes to confirm the fracture of the clone, and then click OK. The clone is now fractured from its source LUN.

4. From the production host, resume I/O to the source LUN.

5. From the second host, activate the clone by issuing the appropriate command for your operating system.

? On a Windows host, run the admsnap clone_activate command.  After a delay, the admsnap clone_activate command finishes re-scanning the system and assigns drive letters to newly discovered clone devices.

Note: If the second host is running Windows NT and the clone was already mounted on the second host, a reboot is required after you activate the fractured clone. If the second host is running Windows 2000, a reboot is recommended but not required.
? On a UNIX host, use the same commands that you used to discover the new FLARE LUNs.
See also "Fracturing a Clone" in Chapter 3 of EMC SnapView for Navisphere Administrators Guide (P/N 0690011180).