Commserve - Log ship vs Database mirroring

Last post 06-01-2011, 4:43 AM by Rafter. 2 replies.
Sort Posts: Previous Next
  • Commserve - Log ship vs Database mirroring
    Posted: 05-25-2011, 7:02 AM

    Hi Guys,

    Looking to setup a standy commserve at a remote connected site for DR purposes.

    Looking at the documentation: http://documentation.commvault.com/commvault/release_9_0_0/books_online_1/english_us/prod_info/disaster_recovery.htm
    It looks like to keep the commserves in step (without having to do a DR recovery) its sql mirroring or log shipping.

    Does anyone have a view on which one is best?  I see with log shipping the need for an additional 2 sql licences as the main downside -and expense!

    I'm looking to use the mirroring setup, anyone had any issues?

    Any comments on DR commserve would be interesting.

    Cheers!

  • Re: Commserve - Log ship vs Database mirroring
    Posted: 05-31-2011, 2:18 PM

     

    Hello rafter,

    Database mirroring is functionality in the SQL Server engine that reads from the transaction log and copies transactions from the principal server instance to the mirror server instance.  Database mirroring can operate synchronously or asynchronously. If configured to operate synchronously, the transaction on the principal will not be committed until it is hardened to disk on the mirror. Database mirroring supports only one mirror for each principal database. Database mirroring also supports automatic failover if the principal database becomes unavailable.  The mirror database is always offline in a recovering state, but you can create snapshots of the mirror database to provide read access for reporting, etc.

    Log shipping is based on SQL Server Agent jobs that periodically take log backups of the primary database, copy the backup files to one or more secondary server instances, and restore the backups into the secondary database(s).  Log shipping supports an unlimited number of secondary’s for each primary database.

    In both cases the database is set to FULL recovery model. In regards to Database mirroring, with the Database set to this recovery mode it is recommended to take frequent log backups to truncate the size of the transaction log file. Otherwise this log files will grow very large. A Commvault SQL ida can be installed and scheduled to run such backups.

    Database mirroring is preferable to log shipping in most cases, although log shipping does have the following advantages:

    1. it provides backup files as part of the process
    2. multiple secondary’s are supported
    3. it is possible to introduce a fixed delay when applying logs to allow the secondary to be used for recovering from user error

    More information about both technologies is available in SQL Server 2008 Books Online in the topics "Understanding Log Shipping" and "Overview of Database Mirroring".

    Dave W.

  • Re: Commserve - Log ship vs Database mirroring
    Posted: 06-01-2011, 4:43 AM

    Thanks Dave, good info, we're going down the mirroring route.

    Cheers!

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