livesync overwriting/corrupting already sync'd VM's

Last post 04-09-2020, 5:25 AM by Yaser BOUHAFS. 1 replies.
Sort Posts: Previous Next
  • livesync overwriting/corrupting already sync'd VM's
    Posted: 04-07-2020, 2:13 PM

    We are running livesync of about 190 VM's to prepare for a DC evacuation.  It is VMware to VMware and we are using our secondary copy of the backup data to perform the sync.


    We have one main client, several subclients, and then VM's buried in the subclients.  So we have one subclient with about 80 VM's in it but they each have their own schedule for live sync.  we also have subclients which only contain 1 vm.

    The subclients with 1 VM work fine every night doing their nightly backups/aux copy/livesync/validation

    Some of the VM's in the subclients with multiple VM's work, but most do not.  Support has seen that it looks like 2 simultaneous jobs kick off, one with the client name and one with the VM name (schedules are named after the VM).

    When this happens, the second job comes in and wipes out the boot disk causing it to fail and corrupt the VM.  I have no idea how to fix this and nor can i find any secondary job that is running to cause this.  Any ideas?

  • Re: livesync overwriting/corrupting already sync'd VM's
    Posted: 04-09-2020, 5:25 AM


    We arcurrently facing a similar problem with VMware livesync replication: boot disks are corrupted or errors are detected on the VM filesystem.

    However, when we run a full restore from the secondary copy, we don't see any problem on the restored VMs.

    We had this problem since installing SP16. Commvault support asked us to install hotfix_pack_43. Unfortunately we still have filesystem errors on VMs replicated by livesync.

    The commvault development team is still working on this case...

    Can you tell me which SP and hotfix Pack are installed on your commvault servers ?


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