Skip to main content

Weird naming issue

Thread needs solution

I created a full disk backup.  I backed up my machine to M:\Acronis Backups.

Then I deleted the job and the folder.  And then created a new backup job and ran that to M:\Acronis Backups2

 

I then deleted the job and the folder and created a new full diskbackup.

 

I notced that on this, even though it was a brand new job and no other jobs existed, that the resulting file looked like:

MyLaptop_full_b3_s1_v1.tib

 

I thought that was strange so I tried validating...it tried looking for previous versions and I hit the skip button, eventuallyallwing me to validate. So I renamed it from MyLaptop_full_b3_s1_v1.tib to MyLaptop_full_b1_s1_v1.tib and ran the backup job again which resulted (correctly) in a new file called MyLaptop_diff_b1_s2_v1.tib.

 

a) Why was the numbering off?

b) Is the way I solved it OK in terms of maintaining things and if I ever need to do a restore?

0 Users found this helpful

John,

What you describe should not be, or I would desribe as a bug.

You might want to report this via the feedback channels.

http://www.acronis.com/en-us/support/feedback.html

It is either residue carried over in the history file; or residue carried forward from default script value.

either way, it should no be.

---------------

Note. If you used the clone script setting, the clone script would carry forward the backup number and the B3 would be expected--being a clone.

I am aware of this clone issue and have reported it a long time ago.