State value mapping in SQL Clone Config Database

• 
  Hi Robert,

  
  

  Here's the listing as of version 5.3.2.

  
  

  Operations:

  1. UserRequested (a user has told the Clone server to perform an operation)
     
  2. DispatchedToAgent (the Clone server has told the agent to perform the operation)
     
  3. Started (the agent has begun working on the operation)
     
  4. Successful (the operation succeeded)
     
  5. Faulted (the operation failed)
     
  6. Canceled (the operation was cancelled before it succeeded or failed)
     

  
  

  Images:

  1. BeingCreated (SQL Clone is creating the image)
     
  2. Created (the image is ready to use)
     
  3. Missing (more or less unused)
     
  4. Deleted (the image has been deleted)
     
  5. BeingDeleted (the image is being deleted)
     
  6. FailedToCreate (image creation failed)
     

  
  

  Clones:

  1. BeingCreated (SQL Clone is creating the clone)
     
  2. Online (the clone should be available in SQL Server)
     
  3. Offline (the clone storage exists but we can't online it for some reason)
     
  4. Missing (the clone storage or data files isn't accessible)
     
  5. Deleted (the clone has been deleted)
     
  6. BeingDeleted (the clone is being deleted)
     
  7. FailedToCreate (clone creation failed)
     
  8. ImageInaccessible (the clone's host machine can't access its parent image, so we can't risk using it)
     
  9. CleanUpRequired (we couldn't delete the clone when requested, but will clean it up when we can)
     
  10. BeingReset (the clone is being reset back to its initial state)
      
  11. AgentOffline (we don't know the clone's state because we can't contact its agent)

  Hope that helps!
  

  
  

  owen.hall February 01, 2022 11:49

  - 0 +
• 
  Thank you!  That does indeed help!  I'm sure this is in the documentation, but I was perhaps a bit too impatient in my searching.

  RobertReid February 01, 2022 18:30

  - 0 +

Add comment

Please sign in to leave a comment.