Backup of Exchange VM failed

Last post 05-28-2020, 12:29 PM by Liam. 2 replies.
Sort Posts: Previous Next
  • Backup of Exchange VM failed
    Posted: 04-30-2020, 3:24 PM
    Hello

    Until a few days ago, the backup of the VM of our Exchange server was flawless. But recently,
    the backup failed with the following message:
    ----
    Error Code: [91:155]
    Description: The system or provider has insufficient storage space. If possible delete any old or unnecessary persistent shadow copies and try again.
    Source: unicwbsvcl03, Process: vsbkp
    ----
    We increased the size of the Exchange disk from 2.6TB to 3TB and made a Full backup that ended 
    without errors.

    On this last dawn, however, there was a failure with the following message:
    ----
    Error Code: [91:113]
    Description: Unable to read the disk [\\?\GLOBALROOT\Device\CSV{69170e0c-ff8e-4347-9552-baf35303ec89}\UNICWBSV215\VIRTUAL HARD DISKS\UNICWBSV215_D.vhdx] for virtual machine [UNICWBSV215] on Host [UNICWBSVCL03]. [Invalid argument (ErrNo.22)]
    Source: unicwbsvcl03, Process: vsbkp
    ----

    Both times, as a consequence, the Exchange server crashed forcing our colleagues from windows
    support to work for about 2 hours to recover the email service.

    Now, we disable the backup until we have understood and fixed the problem.


    Environment:
    CommCell: Version 10 build 116
    Client: Windows Server 2016 Datacenter version10 SP14 +

    Does anyone have any idea how to deal with this failure?
  • Re: Backup of Exchange VM failed
    Posted: 05-02-2020, 8:05 AM

    Check if the datastore has less than 10% free, this is the default (tunable) free space required on the datastore.

  • Re: Backup of Exchange VM failed
    Posted: 05-28-2020, 12:29 PM
    • Aplynx is not online. Last active: 06-30-2020, 12:58 PM Liam
    • Top 10 Contributor
    • Joined on 05-04-2010
    • New Jersey
    • Master
    • Points 1,846

    Space issue certainly sounds like the right path to investigate since the enviroment is crashing.

    I'd also suggest moving past v10 since official support was dropped 12/15/17

    http://documentation.commvault.com/commvault/v10/article?p=v10_end_of_support.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 © 2020 Commvault | All Rights Reserved. | Legal | Privacy Policy