How does this automatic schedule work in the background?

Last post 08-27-2018, 1:44 PM by ckubik. 2 replies.
Sort Posts: Previous Next
  • How does this automatic schedule work in the background?
    Posted: 06-04-2018, 6:07 PM

    I would like to know, how does the CV's Automatic Scheduling works in the backend

    Suppose if have an automatic schedule set to monitor the archive_log destination every 2 hours and trigger a backup when the usage has crossed 80%.

    What exactly does commvault do in the backend, and how does the oracle agent check the usage of the log destination ?

    If the log_destination usage is 60% if i would wish to know if commvault has done its bi-hourly check where do i get to see these logs.


    Thanks in advance!

  • Re: How does this automatic schedule work in the background?
    Posted: 06-05-2018, 5:41 AM

    Start backup when disk at log destination is

    Runs the job when the log files on the disk use this percentage of the storage space. The default is 80 percent.

    For SQL Agent, starts the backup operation for log files only if 80 percent of the space available within the log file (per maximum log file size) is full.

    Note: Automatic schedule does not work for an SQL Availability Group client.

    Regarding the log files to check this, I am not sure which to check.
    If someone from Commvault support reads this, can you confirm where to look?

    Jos Meijer
    Senior Technical Consultant
  • Re: How does this automatic schedule work in the background?
    Posted: 08-27-2018, 1:44 PM

    Automatic scheduling is done by sending some schedule XMLs to the client and the client then knows how to do the check and when to start "pushing" data. So the job is initiated from the client (as only the client knows when the Log is full enough for example)...

    I would believe that CVD.log should probably contain some information about this, but I'm not sure... I would need to try this out in my lab to confirm this. So if someone else knows this feel free to add to this discussion :)

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