Restore of large SQL database - what happens if it is interrupted?

Last post 12-17-2019, 8:14 PM by Creeves2012. 2 replies.
Sort Posts: Previous Next
  • Restore of large SQL database - what happens if it is interrupted?
    Posted: 12-03-2019, 7:22 AM

    Hypothetically speaking - if I have a large (or small, it doesn't matter) SQL database that needs to be restored, and I kick off the restore, and for some reason the job is interrupted - can it be resumed? If so, will it resume from the point it restored up to, or does it restart from the beginning?

    e.g imagine the evene is that the MA running the job was rebooted or became unavailable. We do have GridStor so multiple MA's per path/SP/copy etc.

    Any help useful, as long as it's based on fact - ideally I'm looking for facts, not guesses.

    Thanks very much!

    Rob

  • Re: Restore of large SQL database - what happens if it is interrupted?
    Posted: 12-16-2019, 9:57 AM

    Hi,

    We do not support restore restartability inside the database today. This is something we have in our roadmap.

     

    Thanks,

    Karthik

  • Re: Restore of large SQL database - what happens if it is interrupted?
    Posted: 12-17-2019, 8:14 PM

    We've found when restoring large SQL databases, or multiple large databases, it's best to up the VDI timeout for the iData agent on the restore client. We would see jobs fail with or time out at times with the default setting of 300 for any SQL restore job we would run larger than a few GB's.

    Upping the timeout to 99999999 or a large value would let our restore jobs finish and not fail from VDI errors. 

    Expand the client computer in the Commserv Expand the SQL agent, right click on the instance and you can changet the VDI timeout threshold from here. 

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