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

Diff for /pegasus/Schemas/CIM231/DMTF/Device/CIM_Snapshot.mof between version 1.1.2.1 and 1.1.2.2

version 1.1.2.1, 2012/01/24 13:50:09 version 1.1.2.2, 2012/02/15 17:46:24
Line 0 
Line 1 
   // Copyright (c) 2005 DMTF.  All rights reserved.
   // <change cr="ArchCR00066.004" type="add">Add UmlPackagePath
   // qualifier values to CIM Schema.</change>
   // ==================================================================
   //  CIM_Snapshot
   // ==================================================================
      [Deprecated { "No Value" },
       Version ( "2.7.0" ),
       UMLPackagePath ( "CIM::Device::SccExtents" ),
       Description (
          "Deprecated. Snapshots are now modeled in a more abstrct way "
          "using StorageExtent and StorageSynchronized. \n"
          "The Snapshot class is an optional construct. It can be used to "
          "represent an Extent that contains a full copy of another "
          "Extent, or the changes to that Extent when performing a "
          "delta-based (delta before or delta after) copy. \n"
          "Snapshot\'s definition in CIM is not equivalent to the act of "
          "creating a volume or file-based snapshot, or a point in time "
          "copy. It is at a much lower level and represents the use of "
          "storage to hold a copied image of an Extent, or to hold "
          "changes to an Extent. Use of the Snapshot object when making a "
          "full copy is only recommended if the purpose is to describe "
          "the existence of a copy. (This use will be very infrequent.) "
          "The problem with describing an Extent solely as a \'snapshot\' "
          "is that when the snapshot/copy is broken, the object must be "
          "destroyed. Typically, this object still holds valid data, and "
          "would have to be reinstantiated. If the \'full copy\' object "
          "is to be treated as a StorageVolume or more general Extent, "
          "then it should be modeled as such from the beginning - i.e., "
          "not as an instance of Snapshot but as an instance of a generic "
          "StorageExtent or StorageVolume. In this case, the Synchronized "
          "association would be used to describe that one StorageExtent "
          "is synchronized with another. \n"
          "When describing a delta-based snapshot/point in time copy, the "
          "Snapshot object represents the store holding the before/after "
          "image changes to the original Extent. For example, when doing "
          "a \'delta before\' Snapshot, the resultant target would be "
          "modeled as a StorageExtent that is BasedOn the original Extent "
          "and the instance of Snapshot (that holds the changes to the "
          "original Extent)." )]
   class CIM_Snapshot : CIM_StorageExtent {
   
         [Deprecated { "CIM_Synchronized.SyncMaintained" },
          Description ( "True indicates that the snapshot is synced." )]
      boolean IsSynced;
   
         [Deprecated { "CIM_Synchronized.WhenSynced" },
          Description (
             "The time stamp indicating when the sync occurred." )]
      datetime SyncTime;
   
   
   };


Legend:
Removed from v.1.1.2.1  
changed lines
  Added in v.1.1.2.2

No CVS admin address has been configured
Powered by
ViewCVS 0.9.2