Cleanup Snapshot if Job was aborted

Last post 05-26-2020, 12:57 AM by jagito. 4 replies.
Sort Posts: Previous Next
  • Cleanup Snapshot if Job was aborted
    Posted: 05-25-2020, 10:34 AM

    Hello everyone,

    I had a problem last week with a customer who had 5 x 10TB
    VM's in the backup.
    When I noticed that, I had to quit the job. By canceling, commvault caused two problems.
    First, the created snapshots were left on the datastore after the backup was aborted.
    Second, although the job was aborted, the snapshot kept growing until the datastore was full and the systems running on it were shut down.
    Is there a setting that also checks if Commvault snapshots are still present and deletes them when the job is aborted?

    Regards

    Thomas

  • Re: Cleanup Snapshot if Job was aborted
    Posted: 05-25-2020, 11:22 AM
    • Aplynx is not online. Last active: 06-30-2020, 12:58 PM Liam
    • Top 10 Contributor
    • Joined on 05-04-2010
    • New Jersey
    • Master
    • Points 1,846

    Clean up is part of the backup process, so long as you don't force kill the job. 

  • Re: Cleanup Snapshot if Job was aborted
    Posted: 05-25-2020, 11:50 AM

    Hello Liam,

    thanks for your answer.
    Okay, if the job was killed, Commvault doesn't delete the snapshot. Then how is it possible that the snapshot grew after the job was canceled ?
    I am trying to find a solution that always deletes the snapshot, whether the job was successful or killed.
    Do you have any suggestions how to do this ?

    Regards

    Thomas

  • Re: Cleanup Snapshot if Job was aborted
    Posted: 05-25-2020, 12:17 PM
    • Aplynx is not online. Last active: 06-30-2020, 12:58 PM Liam
    • Top 10 Contributor
    • Joined on 05-04-2010
    • New Jersey
    • Master
    • Points 1,846

    the vm is not cleaned up if a 'force kill' is used as it will abort the process. a normal kill send an API request to vmware to delete the disks. you'll see this in the vsbkp.log when the process is killed

  • Re: Cleanup Snapshot if Job was aborted
    Posted: 05-26-2020, 12:57 AM

    Hello Liam

     

    That's right, if in any way the Job finish abnormally or the communication with the vCenter was aborted, the snapshots are still there....

    Are you using VM layer Snapshots or Disk Array snapshots?

     

    From Console or Webconsole you can try the following:

    In Menu Storage > Array Management, click on the Array and the click on "List Snaps"

     

    If Snaps are still mounted, use unmount snaps or force unmount snaps (based on Job ID)

    After that use remove snapshot or force remove snapshot.

     

    When finish, run Reconcile Snaps

     

    If that doesn't work, first remove snaps in vCenter or array system and then run Reconcile Snaos again

     

    Jago :)

The content of the forums, threads and posts reflects the thoughts and opinions of each author, and does not represent the thoughts, opinions, plans or strategies of Commvault Systems, Inc. ("Commvault") and Commvault undertakes no obligation to update, correct or modify any statements made in this forum. Any and all third party links, statements, comments, or feedback posted to, or otherwise provided by this forum, thread or post are not affiliated with, nor endorsed by, Commvault.
Commvault, Commvault and logo, the “CV” logo, Commvault Systems, Solving Forward, SIM, Singular Information Management, Simpana, Commvault Galaxy, Unified Data Management, QiNetix, Quick Recovery, QR, CommNet, GridStor, Vault Tracker, InnerVault, QuickSnap, QSnap, Recovery Director, CommServe, CommCell, SnapProtect, ROMS, and CommValue, are trademarks or registered trademarks of Commvault Systems, Inc. All other third party brands, products, service names, trademarks, or registered service marks are the property of and used to identify the products or services of their respective owners. All specifications are subject to change without notice.
Close
Copyright © 2020 Commvault | All Rights Reserved. | Legal | Privacy Policy