Sublient type - System Databases Questions

Last post 01-30-2019, 1:05 PM by Hoodsie. 3 replies.
Sort Posts: Previous Next
  • Sublient type - System Databases Questions
    Posted: 01-28-2019, 10:27 AM

    1. Does anyone know what effect it has if you set a Database subclient type to "System Databases"? 

    The previous admin put a full schedule and a t-log schedule on the default subclient which included the system databases. Now we need to not backup any DBs except the system ones in the server client because we have a DAG client for it. But we want to backup the system dbs. 

    Should I just select 'system dbs' or do I need to exclude all existing DBs in the content tab? And then turn off auto-discover so no future DBs are backed up on the client directly? Or should I just create a regular subclient and add the system DBs manually to the content and disable activity on the default subclient? 

     2. Should a subclient that only backs up the 3 system databases be configured to start a log backup right after in order to truncate the logs of the model database which is in Full Recovery mode by default? 

    Thanks

  • Re: Sublient type - System Databases Questions
    Posted: 01-29-2019, 6:36 PM

    Hi Hoodsie,

    TL;DR:

    1. System Databases subclient will pull system databases if they haven't been manually discovered elsewhere, all of the methods you mentioned are also valid, but also see using BackupAGDBsViaActualInstance below for possibly an easier way.

    2. You can definitely do that if you like, but model should be relatively stable, so might not be necessary to run log backup. You can tell databases not in full recovery model to skip T-Log if this is easier and then schedule T-Log anyway.

    Full Response:

    Question 1:

    Adding a 'System Database' subclient will automatically pull the System DBs (master, model and msdb) into it during the next backup operation. Note that this only works if the databases were not manually discovered under another subclient previously. If they were auto-discovered under the default subclient, then next backup should move them to the System Databases subclient.

    See BOL: http://documentation.commvault.com/commvault/v11/article?p=18158.htm 

    Default subclient will backup up all available databases that are not otherwise discovered under user-defined subclients.

    As of V11 SP11 (I believe) the databases currently discovered under your AlwaysOn Group client should be automatically skipped from backup under subclients on the stand-alone node, but if you're not seeing that occur you can look at implementing the BackupAGDBsViaActualInstance additional setting.

    Before V11 SP11, this was only possible with a Global Additional Setting  http://documentation.commvault.com/additionalsetting/details?name=%22BackupAGDBsViaActualInstance%22&id=

    After SP11 this can be done on a per-client level: http://documentation.commvault.com/additionalsetting/details?name=nBackupAGDBsViaActualInstance

    For more information on the AG client see: http://documentation.commvault.com/commvault/v11_sp13/article?p=18295.htm

    Note: The client SP level is what determines whether the additional setting above needs to be set at theglobal or client level.

     

    Question 2:

    In terms of needing to run log backup for the model database, this database by rights should not be growing. It is just a template database from which all new databases (and TempDB) are created. If you do notice it growing you can definitely schedule log backup against the subclient.

    Prior to V11 SP11 you can tell a backup to automatically skip transcation log backups on databases that in simple recovery model by checking the "Skip transactional log backups for simple recovery model databases"

    http://documentation.commvault.com/commvault/v11_sp10/article?p=en-us/universl/user_account_password/cs_db_config.htm 

    From SP11 onwards the default behaviour is to skip transaction log backup on Simple Recovery model databases.

    How you would like to configure the scheduling is up to you, but if you would like to run a t-log backup right after the full just to ensure truncation is occurring that would be fine.

    One thing that's worht noting here, running a log backup does not shrink the physical file size on disk. If model has runaway (unlikely, but has been known to happen) you will need to run a shrink file on it after flipping recovery model on the database.

    I hope this helps

    - David

  • Re: Sublient type - System Databases Questions
    Posted: 01-30-2019, 12:55 PM

    ddwyer:

    Hi Hoodsie,

    TL;DR:

    1. System Databases subclient will pull system databases if they haven't been manually discovered elsewhere, all of the methods you mentioned are also valid, but also see using BackupAGDBsViaActualInstance below for possibly an easier way.

    2. You can definitely do that if you like, but model should be relatively stable, so might not be necessary to run log backup. You can tell databases not in full recovery model to skip T-Log if this is easier and then schedule T-Log anyway.

    Full Response:

    Question 1:

    Adding a 'System Database' subclient will automatically pull the System DBs (master, model and msdb) into it during the next backup operation. Note that this only works if the databases were not manually discovered under another subclient previously. If they were auto-discovered under the default subclient, then next backup should move them to the System Databases subclient.

    See BOL: http://documentation.commvault.com/commvault/v11/article?p=18158.htm 

    Default subclient will backup up all available databases that are not otherwise discovered under user-defined subclients.

    As of V11 SP11 (I believe) the databases currently discovered under your AlwaysOn Group client should be automatically skipped from backup under subclients on the stand-alone node, but if you're not seeing that occur you can look at implementing the BackupAGDBsViaActualInstance additional setting.

    Before V11 SP11, this was only possible with a Global Additional Setting  http://documentation.commvault.com/additionalsetting/details?name=%22BackupAGDBsViaActualInstance%22&id=

    After SP11 this can be done on a per-client level: http://documentation.commvault.com/additionalsetting/details?name=nBackupAGDBsViaActualInstance

    For more information on the AG client see: http://documentation.commvault.com/commvault/v11_sp13/article?p=18295.htm

    Note: The client SP level is what determines whether the additional setting above needs to be set at theglobal or client level.

     

    Question 2:

    In terms of needing to run log backup for the model database, this database by rights should not be growing. It is just a template database from which all new databases (and TempDB) are created. If you do notice it growing you can definitely schedule log backup against the subclient.

    Prior to V11 SP11 you can tell a backup to automatically skip transcation log backups on databases that in simple recovery model by checking the "Skip transactional log backups for simple recovery model databases"

    http://documentation.commvault.com/commvault/v11_sp10/article?p=en-us/universl/user_account_password/cs_db_config.htm 

    From SP11 onwards the default behaviour is to skip transaction log backup on Simple Recovery model databases.

    How you would like to configure the scheduling is up to you, but if you would like to run a t-log backup right after the full just to ensure truncation is occurring that would be fine.

    One thing that's worht noting here, running a log backup does not shrink the physical file size on disk. If model has runaway (unlikely, but has been known to happen) you will need to run a shrink file on it after flipping recovery model on the database.

    I hope this helps

    - David


    Awesome Answers. Thanks! For now we just disable the default subclient on hosts that have DBs only in the AGs. Then we have a second subclient for system databases. The DBAs know to let us know if they create a new DB that needs to be backed up. We don't want a catchall for new ones for other reasons. Good to know that simple mode DBs skip the attempt to do a T-Log. 

  • Re: Sublient type - System Databases Questions
    Posted: 01-30-2019, 1:05 PM

    Just an FYI - looks like it automatically skips databases in simple mode even if that checkbox isn't configured on the client. At least that's what happening for me. This process below may not be necessary. You can confirm what's happening on the "status" tab for a job's details. 

     

    http://documentation.commvault.com/commvault/v11/article?p=18196.htm 

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