Backup Fails with "Less than 1 minute left" and sits there for 2 days.
Like the title says. backup is in a hung state forever with one minute left. I downloaded the VSS tool and I generated a log file. It says something about not enough disk space on one of the volumes but only less than half of the 1 TB Raid 10 system is being used. It offers to fix the problem but then says, "You must understand the consequences of what you are doing." Does this imply some sort of disaster or i will lose data? Anyway I am attaching the VSS log file.
-John
Steve Smith wrote:John, I don't see anything worrying in the VSS Doctor report other than what is a common issue with very small hidden / system partitions having low space, which should not cause your backup to fail or hang with 'less than 1 minute remaining'.
Download a copy of the MVP Assistant log viewer tool and use this to look at the logs to see if they show any issues during the operation process?
The latest version of the new log viewer tool is at the link below.
MVP Assistant update for Acronis Cyber Protect Home Office (Version 1.1.6.0)If you have Disks & Partitions backups created on ATI 2020 or later using .tibx files, then look in the Backup Worker logs.
If you have Files & Folders backups using .tib files (or Disk backups from earlier versions using .tib files) or using Cloning then look in the Demon logs.
Other logs are shown by the MVP Assistant under the 'Active Logs' heading of the Log Viewer page of the Assistant.
The Schedule2 log contains information related to scheduled task but is one of the more difficult logs to read / work through.
The log files should be zipped to preserve their original file names if sharing in the forums and would need to be less than 3MB in size, otherwise you would need to share the zip file via a Cloud share service such as OneDrive, Dropbox etc.
Sorry it took so long to get back here but, your reply went in my Junk folder. I'm going to follow your advice but, i still have a question about the VSS Doctor. It gives a warning about the fix for the low disk space and asks if I really want to proceed. If I let it apply the fix, will i lose any data? There is over a half terrabyte available on the RAID 10 set. I just want to be sure nothing bad will happen. Thanks. -John
John, the only VSS issue that the tool will offer to fix is the VSS configuration parameter for the volume identified below:
ForVolume: \\?\Volume{ef7c68b0-0000-0000-0000-c0bfe8000000}\
OnVolume: \\?\Volume{ef7c68b0-0000-0000-0000-c0bfe8000000}\
Used: 0 B
Allocated: 0 B
Maximum: 32 MB <<<<----------------
Minimum: 320 MB <<<<----------------
VolumeSize: 528 MB
Available: 78 MB
TargetMaximum: 320 MB
MaximumGreaterThenMinimum: False
MaximumIsEnough: False <<<<----------------
MaximumIsNotReached: True
AvailableIsEnoughForMaximum: True
IsOk: False <<<<----------------
Description: Maximum storage size is less than required minimum
The issue being fixed in that the Maximum size set is only 32 MB but the Minimum size is ten times greater than this at 320 MB.
As for actual warning in the next section of the report:
Disk Free Space Available Status: Warn Description: Some disks have insufficient free space. Perform a cleanup.
The only action here has to be performed by the user. The tool cannot / will not perform any disk cleanup for you! This again only applies to the volume identified below:
Name: \\?\Volume{ef7c68b0-0000-0000-0000-c0bfe8000000}\
DeviceId: \\?\Volume{ef7c68b0-0000-0000-0000-c0bfe8000000}\
Size: 528 MB
Available: 78 MB <<<<----------------
Minimum: 320 MB <<<<----------------
IsOk: False <<<<----------------
Description: Free space is below required minimum
IsMounted: False
Steve Smith wrote:John, the only VSS issue that the tool will offer to fix is the VSS configuration parameter for the volume identified below:
ForVolume: \\?\Volume{ef7c68b0-0000-0000-0000-c0bfe8000000}\ OnVolume: \\?\Volume{ef7c68b0-0000-0000-0000-c0bfe8000000}\ Used: 0 B Allocated: 0 B Maximum: 32 MB <<<<---------------- Minimum: 320 MB <<<<---------------- VolumeSize: 528 MB Available: 78 MB TargetMaximum: 320 MB MaximumGreaterThenMinimum: False MaximumIsEnough: False <<<<---------------- MaximumIsNotReached: True AvailableIsEnoughForMaximum: True IsOk: False <<<<---------------- Description: Maximum storage size is less than required minimumThe issue being fixed in that the Maximum size set is only 32 MB but the Minimum size is ten times greater than this at 320 MB.
As for actual warning in the next section of the report:
Disk Free Space Available Status: Warn Description: Some disks have insufficient free space. Perform a cleanup.The only action here has to be performed by the user. The tool cannot / will not perform any disk cleanup for you! This again only applies to the volume identified below:
Name: \\?\Volume{ef7c68b0-0000-0000-0000-c0bfe8000000}\ DeviceId: \\?\Volume{ef7c68b0-0000-0000-0000-c0bfe8000000}\ Size: 528 MB Available: 78 MB <<<<---------------- Minimum: 320 MB <<<<---------------- IsOk: False <<<<---------------- Description: Free space is below required minimum IsMounted: False
OK... This is what I'm worried about. If I hit the "YES" button to do the repair, is disaster going to strike?
I doubt that any disaster is going to befall you by allowing the VSS Doctor to correct the issue to make the maximum value 1 MB greater than the minimum value of 320 MB. It doesn't make any sense to have a maximum value which is only 32 MB when the minimum is set to 320 MB...!
The change only applies to this one very small 528 MB hidden partition.
Steve Smith wrote:I doubt that any disaster is going to befall you by allowing the VSS Doctor to correct the issue to make the maximum value 1 MB greater than the minimum value of 320 MB. It doesn't make any sense to have a maximum value which is only 32 MB when the minimum is set to 320 MB...!
The change only applies to this one very small 528 MB hidden partition.
OK, I'll let VSS Doctor fix it tonight when I go in after hours. I'll let you know how things went. Thanks! -John