SQL transaction log restore interrupt

Last post 06-27-2017, 8:00 AM by Kay. 0 replies.
Sort Posts: Previous Next
  • SQL transaction log restore interrupt
    Posted: 06-27-2017, 8:00 AM
    • Kay is not online. Last active: 2019-05-03, 5:32 AM Kay
    • Top 500 Contributor
    • Joined on 10-28-2013
    • Essen
    • Novice
    • Points 87
    When using the SQL iDA to restore SQL transaction logs (CS DR workflow scenario)…   is there any phase where the destination database will switch into an inconsistent mode when the Commserve will crash during the restore?

    Assumption the size of the transaction log will be a few MB. The cv services of the Instance002 need to be stopped and the dr csdb switched out of the restore mode manually, before start up the dr cs services (Instance001).

    Thanks, Kay
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.
Copyright © 2019 Commvault | All Rights Reserved. | Legal | Privacy Policy