![]() ![]() These two events are usually coupled together. The shadow copies of volume D: were aborted because the shadow copy storage failed to grow. As a result of this failure all shadow copies of volume D: are at risk of being deleted. There was insufficient disk space on volume D: to grow the shadow copy storage for shadow copies of D. This usually points to a disk issue on the drive being referenced and there should be ‘Disk’ or ‘Ntfs’ events at the same time that give more information on the issue. The shadow copies of volume D: were aborted because of an IO failure on volume D: The shadow copies of volume D: were aborted because volume D:, which contains shadow copy storage for this shadow copy, was force dismounted. Increases (not going up to the maximum) do not typically require a restart. Note that if you set the it to the maximum page file available, you will be required to restart the machine. Vssadmin resize shadowstorage /For=D: /On=E: /MaxSize=UNBOUNDEDĪdjusting the page file to 1.5 times the amount of RAM can also help the situation. ![]() You can run the following command on the host in order to place the shadow copy on another disk drive letters need to be changed accordingly: vssadmin add shadowstorage /For=D: /On=E: /MaxSize=UNBOUNDED You’ll need to ensure that you have a disk with enough (10% of the original source) and it should also be a disk with on-per performance as the source. In addition to that something that will help alleviate the IO on the source disk is placing the shadow copies onto another drive completely. In this case you can choose to re-schedule the backup job when there is less IO on the source disk. ![]() This error is logged due to the source drive experiencing a high IO load and thereby it causes the shadow copy to dismount, as a result causing a backup failure. Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied. The shadow copies of volume D: were deleted because the shadow copy storage could not grow in time. You can refer to this article showcasing the error seen in Altaro.īelow you can find a couple of ‘volsnap’ events that we’ve encountered along with their solutions: Such events usually contain relevant troubleshooting information as to why the shadow copy got dismounted and as a result causes the backups to fail. The volsnap source errors are events that are listed in the Windows System event log. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |