Skip to main content

Acronis stops recognizing created task parameters or back-ups

Thread needs solution

I have had a persisting problem since I began using a second back up to a portable drive. It has taken me months to realize what was happening. I use home 2010 on Win7 64 PC.

I back-up to a USB3 portable drive always connected to the PC. I create scheduled new full images of two internal drives about one every month or or two, with auto incremntals to these every few days between. No problem. But half a year ago, I began using making an additional backup to a similar drive, which is stored offsite for safety. I created full, unschedlued backups for this drive, which I run manually to be staggered two weeks from other.

I found that I had to unplug the first drive before plugging in the second to my USB hub. Fine. However, after having run the unscheduled backups, disconnected the offsite drive, and reconnected the onsite one, Acronis, which should be ready to continue its two incremental backups, fails to recognize its friend, I get a notice saying the backup has failed, and I have to recreate the scheduled backup from scratch.

Today, after completing the offsite backups and reconnecting the onsite drive, I opened (edit) the scheduled backups to see if I could determine a problem. Instead of remaining as incrementals, both are now set as full backups.

Something is evidently confusing Acronis into overwriting the scheduled backup paramenters with the unscheduled ones. could this be a naming issue, i.e., that I have to create different names for the backups? Could it be that, becuase the backup drive letter reminas the same, due to having only one plugged in at a time, this cuase the problem?

I'll be glad to get the solved.

Thanks to any who respond.

 

0 Users found this helpful

First, some generalities.Each task that you create should have its own unique name--no two tasks named alike. Likewise, the name assigned as the tib name should also always differ--no two alike. Such can help to prevent confusion by the program and the user.

 The  task will not work if the target is multiple disks.  Each different target disk needs its own individual backup tasks and will only perform backups to the target disk that was attached at task creation time. The task and target are mated by id numbers.

Where practical, it can be helpful to assign a different drive letter to each backup target so each target has its own unique drive letter, such as

X, or Y or Z. This offers drive letter stability so the insertion of other devices does not interfere with the pre-assigned drive letters.

However, these unique drive letters need to be assigned at task creation time, before any backups accrue.

These unique drive letters can be assigned in Windows Disk Management.   These unique letters are only recognized by the master disk which assigns the letters. If disks with special drive letters are attached to other computers, the unique letter will not appear.

If I assign special drive letters, I also like to additionallly assign meaningful volume names to the target disk. (11 characters).  I include the unique drive letter as part of the volume name such as "Toshiba-2T_Z" if the drive letter assigned is Z and the target is a Toshiba 2Tb disk.    

Refer this link below. It contains some same custom backup schemes as examples of GH11, GH12 and GH13.  These have cleanup settings so backup deletion by the user is not necessary.

http://forum.acronis.com/forum/100416