VADP backup stuck in waiting state after memory change in the VM after the previous INC backup

Last post 03-14-2019, 2:19 PM by CmVlt. 0 replies.
Sort Posts: Previous Next
  • VADP backup stuck in waiting state after memory change in the VM after the previous INC backup
    Posted: 03-14-2019, 2:19 PM

    I am facing a wierd issue. 

    1. took a VADP full backup of a VM (3PM)

    2. took a VADP INC (5PM)

    3. Took another VADP INC (6PM)

    4. increased the memory of the VM by 2 GB.

    Post this memory allocation change the backup is stuck with no progress.

    Request you to please suggest with a solution.

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