ATI2020 will not backup

Hello!

After checking the logs the issue seem to be related to Disk 6. These warnings indicate that there were IO (Input/Output) operations at certain logical block addresses on Disk 6 that were retried. These retries may indicate potential problems or issues with Disk 6, which could lead to data access or storage problems.

Check Disk Cables and Connections: Physical issues with cables or connections can also lead to IO problems. Make sure all cables are securely connected.

Check Disk Health: Perform a thorough check of the health of Disk 6. Look for bad sectors or other issues that might be causing IO operation retries. You can also run a CHKDSK: https://learn.microsoft.com/en-us/windows-server/administration/windows…

Update Drivers and Firmware: Ensure that the drivers and firmware for Disk 6 and its associated hardware are up to date. Sometimes, outdated drivers can lead to IO issues.

Check Disk Space: Ensure that there is sufficient free disk space on both the source and destination drives for the backup.

Best regards!

Jill, the system report logs are showing snapshot errors causing your backup task to fail which do not look to be associated with the I/O error being reported for Disk 6 in the VSS Doctor report.  Note: the disks.txt (disk report) in the system report zip does not show any disk errors for any of your drives.

You mention above "I use Acronis VSS in backing up to avoid VSS problems with Windows." but the VSS Doctor report doesn't show any obvious issues with any VSS components, so please try changing from Acronis VSS back to the default Windows VSS setting for your task and see if it still fails?

All the Backup Worker logs in the system report going back to 3rd October are giving the same error.

03/10/2022 10:00:55:404 AM +10:00 1208 I00000000: type=commonerror;
value=?5cA??@?A backup error.
$moduleAdisk_backup_vs_650
$fileAc:\jenkins_agent\workspace\mod-disk-backup\650\product\core\da_api\backup.cpp
$funcAda_backup::Commit
$lineNa!o?(????Failed to create volume snapshot.
$moduleAdisk_backup_vs_650
$fileAc:\jenkins_agent\workspace\mod-disk-backup\650\product\core\resizer\archive3\backup_partition.cpp
$funcAresizer::Archive3ImageBuilder::BackupPartitions
$lineNw????v???All attempts to create a snapshot have failed.
$moduleAdisk_backup_vs_650
$fileAc:\jenkins_agent\workspace\mod-disk-backup\650\product\core\fdisk\win_snapshot.cpp
$funcAwin_snapshot_core::Lock
$lineN?I?6??v???Failed to lock the volume snapshot.
$moduleAdisk_backup_vs_650
$fileAc:\jenkins_agent\workspace\mod-disk-backup\650\product\core\fdisk\win_snapshot.cpp
$funcAwin_snapshot_core::CallSbLock
$lineN@k????v???VSS writer 'ASR Writer' with class ID 'BE000CBE-11FE-4426-9C58-531AA6355FC4' has failed to process the snapshot.
$moduleAdisk_backup_vs_650
$fileAc:\jenkins_agent\workspace\mod-disk-backup\650\product\core\fdisk\win_snapshot.cpp
$funcA`anonymous-namespace'::ObtainVSSFailReasonSuberror
$lineN??????d??(?codeN?#?
$moduleAdisk_backup_vs_650
$fileAc:\jenkins_agent\workspace\mod-disk-backup\650\product\core\common\error.cpp
$funcACommon::Error::AddHResult
$lineN==; id=1;
03/10/2022 10:00:55:404 AM +10:00 1208 I00000000: type=retcode; value=4095; id=1;

09/10/2023 11:42:06:696 PM +10:00 15388 I00000000: type=commonerror;
value=?5cA??@?A backup error.
$moduleAdisk_backup_vs_650
$fileAc:\jenkins_agent\workspace\mod-disk-backup\650\product\core\da_api\backup.cpp
$funcAda_backup::Commit
$lineNa!??(????Failed to create volume snapshot.
$moduleAdisk_backup_vs_650
$fileAc:\jenkins_agent\workspace\mod-disk-backup\650\product\core\resizer\archive3\backup_partition.cpp
$funcA`anonymous-namespace'::PartitionBackuper::ReadDrive
$lineN]Z????v???Failed to read the snapshot.
$moduleAdisk_backup_vs_650
$fileAc:\jenkins_agent\workspace\mod-disk-backup\650\product\core\fdisk\win_snapshot.cpp
$funcAwin_snapshot_volume::IoOp
$lineN? ?R?*{??Unknown status.codeN?
$moduleAdisk_backup_vs_650
$fileAc:\jenkins_agent\workspace\mod-disk-backup\650\product\core\fdisk\ver2\arch\windows\win_errors.cpp
$funcAFdisk::AddKstatusError
$lineN(?????d??(?Insufficient system resources exist to complete the requested servicecodeN??
$moduleAdisk_backup_vs_650
$fileAc:\jenkins_agent\workspace\mod-disk-backup\650\product\core\common\error.cpp
$funcACommon::Error::AddWindowsError
$lineN3=; id=1;
09/10/2023 11:42:06:696 PM +10:00 15388 I00000000: type=log; level=inf; message=lsm#1: dedup_map nr_lookup=444 nr_found=75 false+=75 (16.89%/100.00%);
09/10/2023 11:42:06:696 PM +10:00 15388 I00000000: type=retcode; value=4095; id=1; 

Many thanks for this information, I  really appreciate you taking the time to access and read  my reports.

. I  have a few Ext HDD connected to my PC. Is there any indication on these reports to identify Disk 6?  Like GB capacity or Serial number?

From your disk management image attachment.

Thanks Steve. I  was not sure if the VSS Doctor used the same disk number as Windows. That particular disk is a very old one.

I have removed all the Ext Hard Drives and will start the backup again

SUCCESS !! 

Thanks for all the great advice, very much appreciated.

I  disconnected all the External HDDs , esp Drive 6, and I backed up using VSS ( not Acronis VSS)

Went very smoothly.

ran the VSS Doctor, and there is still the error with the small J drive, which I  cannot find  on my Disk Management screen. This is the same error as I  found in the original VSS Report. I  suspect J:/ might be the Recovery Partition on Disk 1
Kind regards to all,

Jill

Jill, glad that all is back working successfully for you.

The Acronis disks.txt / disk report in the zip file confirms that J: is the Hidden Recovery 'Windows RE' partition so the size issue is to be expected!

          PS         Speed IFace Hs-Bs-Tg Model                     
Num  NT    L9NO  Size FSsize Free FS     Type            Label       ABCHSV Error
---- ----- ---- ----- ----- ----- ------ --------------- ----------- ------ ----------
2-   d(4) GPT   447G SATA  0-0-0    WDC WDS480G2G0A-00JH30 UG500000
                                  MBR                                ------
                                  GPTpri                             -----v
  -1       ----  100M  100M   69M FAT32  EF EFI          ........... --c--V
                                  MSresr                             -----v
  -3       --FC  447G  447G   73G NTFS   07 NTFS, HPFS   Win SSD.... --c--V
  -4       ---J  509M  509M   84M NTFS   27 Windows RE H ........... --c--V

Thanks Steve, you are really on the ball and I appreciate your time and effort helping me. Thank you.

With that J: drive VSSDoctor error of inadequate free space , do I  need to do anything about it? ie, will it affect any future backups?

my kind regards,

Jill

Jill, there is nothing you can do about the inadequate free space for the Windows RE recovery partition - it happens on the majority of systems including my own!  The VSS Doctor is working with an algorithm of what the ideal free space allocation should look like rather than the reality of these hidden, system partitions where VSS snapshot space isn't needed to backup.

Thank you kindly, Steve, for helping me lots. My stress levels havedropped enormously :)