(file) Return to CIM_Snapshot.mof CVS log (file) (dir) Up to [Pegasus] / pegasus / Schemas / CIM231 / DMTF / Device

 1 karl  1.1.2.2 // Copyright (c) 2005 DMTF.  All rights reserved.
 2               // <change cr="ArchCR00066.004" type="add">Add UmlPackagePath
 3               // qualifier values to CIM Schema.</change>
 4               // ==================================================================
 5               //  CIM_Snapshot 
 6               // ==================================================================
 7                  [Deprecated { "No Value" }, 
 8                   Version ( "2.7.0" ), 
 9                   UMLPackagePath ( "CIM::Device::SccExtents" ), 
10                   Description ( 
11                      "Deprecated. Snapshots are now modeled in a more abstrct way "
12                      "using StorageExtent and StorageSynchronized. \n"
13                      "The Snapshot class is an optional construct. It can be used to "
14                      "represent an Extent that contains a full copy of another "
15                      "Extent, or the changes to that Extent when performing a "
16                      "delta-based (delta before or delta after) copy. \n"
17                      "Snapshot\'s definition in CIM is not equivalent to the act of "
18                      "creating a volume or file-based snapshot, or a point in time "
19                      "copy. It is at a much lower level and represents the use of "
20                      "storage to hold a copied image of an Extent, or to hold "
21                      "changes to an Extent. Use of the Snapshot object when making a "
22 karl  1.1.2.2        "full copy is only recommended if the purpose is to describe "
23                      "the existence of a copy. (This use will be very infrequent.) "
24                      "The problem with describing an Extent solely as a \'snapshot\' "
25                      "is that when the snapshot/copy is broken, the object must be "
26                      "destroyed. Typically, this object still holds valid data, and "
27                      "would have to be reinstantiated. If the \'full copy\' object "
28                      "is to be treated as a StorageVolume or more general Extent, "
29                      "then it should be modeled as such from the beginning - i.e., "
30                      "not as an instance of Snapshot but as an instance of a generic "
31                      "StorageExtent or StorageVolume. In this case, the Synchronized "
32                      "association would be used to describe that one StorageExtent "
33                      "is synchronized with another. \n"
34                      "When describing a delta-based snapshot/point in time copy, the "
35                      "Snapshot object represents the store holding the before/after "
36                      "image changes to the original Extent. For example, when doing "
37                      "a \'delta before\' Snapshot, the resultant target would be "
38                      "modeled as a StorageExtent that is BasedOn the original Extent "
39                      "and the instance of Snapshot (that holds the changes to the "
40                      "original Extent)." )]
41               class CIM_Snapshot : CIM_StorageExtent {
42               
43 karl  1.1.2.2       [Deprecated { "CIM_Synchronized.SyncMaintained" }, 
44                      Description ( "True indicates that the snapshot is synced." )]
45                  boolean IsSynced;
46               
47                     [Deprecated { "CIM_Synchronized.WhenSynced" }, 
48                      Description ( 
49                         "The time stamp indicating when the sync occurred." )]
50                  datetime SyncTime;
51               
52               
53               };

No CVS admin address has been configured
Powered by
ViewCVS 0.9.2