When I should run FULL (not SynFull)

Last post 11-19-2019, 4:40 PM by ADMPI. 3 replies.
Sort Posts: Previous Next
  • When I should run FULL (not SynFull)
    Posted: 10-25-2019, 1:17 PM

    We have backup subclients for VMware VM backups with "Content of subclients" as a list of VMs or as "Folder" from Vcenter.

    I am wondering should we run Full backup every time when we Add/Delete VM from the list of VMs or when the list of VMs in Folder on Vcenter was changed?

    It's "Crush Consistent" backups with "Collect File Details" enabled.

    When we add a new VM, will the index of files inside VM created by the next Inc job?

    Thank you.
  • Re: When I should run FULL (not SynFull)
    Posted: 10-25-2019, 2:32 PM

    I have never had to run a Full backup when a new VM is added to an existing subclient and we also use Folders on our ESX vCenter environment.

    If you check your backup history it should show you something like this in the job log "2496 2530  10/08 01:34:27 1673799 Check Index CIMetaCopy: moved file [I:\index cache\CV_Index\2\392\1570503650\5003b2c9-5786-3557-5c2d-e5f25834a116!VolHdr(5003b2c9-5786-3557-5c2d-e5f25834a116_scsi0-0-COL-ADFSP1.vmdk).imf] to [I:\index cache\CV_Index\2\392\1570503650\36\VolHdr(5003b2c9-5786-3557-5c2d-e5f25834a116_scsi0-0-COL-ADFSP1.vmdk).imf]

    You should also be able to see in the log from the first nightly backup that it performs a Full backup of the added VM.

    Hope this helps.

  • Re: When I should run FULL (not SynFull)
    Posted: 10-25-2019, 5:31 PM

    Hi ADMPI 

    The purpose of Synthetic Fulls is to consolidate previous fulls and incremental, minimizing the need of interacting with the ESXi host (reducing load from the client).

    You would only want to run a new Full if their are inconsistency in previous Synthetic Full. (i.e. corruption)



  • Re: When I should run FULL (not SynFull)
    Posted: 11-19-2019, 4:40 PM

    I have checked vsbkp.log on the corresponding VSA Proxy and found all answers now:

    VSBkpWorker::ProcessVM() - Failed to query VM [TESTVMNAME] Metadata from previous index. Backup of VM will be a full backup


    VSBkpWorker::AddVMMetadataFile() - Adding metadata file [C:\Program Files\HDS\Backup and Recovery\iDataAgent\JobResults\CV_JobResults\iDataAgent\VirtualServerAgent\2\589\VolHdr(5018d973-808a-39a1-d9f1-3a04dc7701c8_scsi0-0-TESTVMNAME.vmdk).imf] to list to be uploaded to index cache


    Thank you

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