PRIMECLUSTER Global Disk Services Configuration and Administration Guide 4.1 (Solaris(TM) Operating System) |
Contents |
Chapter 2 Objects | > 2.7 GDS Snapshot Objects |
There are five types of shadow object as follows: shadow classes, shadow disks, shadow groups, shadow volumes and shadow slices. These objects correspond to disk classes, SDX disks, disk groups, logical volumes and logical slices that are SDX objects respectively.
When SDX objects and shadow objects do not have to be classified particularly, they may be called "objects" collectively.
On the server where GDS Snapshot is installed, physical disks that are not registered with disk classes in the same domain and that store SDX disk management data can be managed as shadow objects and accessed. Physical disks conforming to either of the following conditions can be managed as shadow objects.
Disks registered with a class (local class or shared class) of GDS or SynfinityDisk in another domain and managed as SDX disks
Disks to which the private slice was copied from an SDX disk registered with a class of GDS or SynfinityDisk in another domain or in the same domain with the disk unit's copy function
Shadow objects have the following characteristics.
When shadow objects, such as shadow disks and shadow volumes, are configured or broken up, the physical disk format and data remain unchanged. For this reason, shadow volumes can be created without affecting data stored on the physical disks, and the data can be read in or write out through the shadow volumes.
The configuration information of shadow objects is not saved on the private slices but managed on memory. Shadow objects are cleared by server reboot, but they can be reconfigured. However, if those objects in the same configuration are not created after the server reboot, restoration is necessary.
For details, see "Rebooting a Node" in "Shadow Volume."
Shadow objects other than shadow disks can be named as desired. The object names must be unique in the entire system. For details on the shadow disk naming restrictions, see "Object Name."
Contents |