Skip to main content

Two Issues) 1) File name for backup 2) wants first verion for a restore for a single version full backup

Thread needs solution

20.6.2015

I have now two issues

1) I cannot seem to define my own file name for the backup file -- BAD!

2) When attempting a recovery I got "Cannot find Volume 1" on a single version full backup.

Just how reliable is your product?

Disappointing!

0 Users found this helpful
Bonzadog wrote:

20.6.2015

I have now two issues

1) I cannot seem to define my own file name for the backup file -- BAD!

Out of the box, you have partial control of the file name. Change the task name, and ATI will change the root of the file name automatically. It will however append a suffix that you cannot change. If you are an advanced user, you could venture in editing the backup script to add tags for things like date, machine name, etc, akin to what was available out of the box with 2014 and previous version.

2) When attempting a recovery I got "Cannot find Volume 1" on a single version full backup.

Just how reliable is your product?

Disappointing!

[/quote]
The probable reason is that you deleted manually an existing version of the backup, the disk changed, or you modified the task some other way, and now ATI is looking for an older file.

At any rate, you can shutdown the pgm, delete the archive database in C:\ProgramData\Acronis\TrueImageHome\Database, then relaunch the program.

Hello,

Thank you for your replies.
I have found out how to change the backups file name, but why change the method that was OK in 2014 version?

2) Since I am create a full single version there will only be one version on in the saving directory.
So why I get a "cannot find version" when only one version is ever on disk?
The taks was not modified.

Why add extra chars. to the file name when old versions will be delete and a single version is to be created?

Surely a restore must always on any full single backup ?

I like to be in control of any Backup software and I feel that 2015 is taking control away.

Perhaps consider using a scheme which involves automatic cleanup or deletion of the oldest backup with the deletion being done by the program.

Create a CUSTOM scheme (scheme name MUST read custom) and set the "Store no more than 1 recent version"

The program will make and keep the 1 version. When the next backup occurs (manual or scheduled), a new full will be first created and then seconds after the new backup created, the first or oldest full backup will be auto deleted by the program . So you need storage space for two but untimately only keeping one full backup.

GH11. Create Custom Full Backup Scheme w/auto cleanup....Store/Keep 4 versions (chains). Use whatever number best fits the individual needs..

Here is more options on backup naming if willing to edit the actual backup .tib.tis script via notepad.

http://forum.acronis.com/forum/91956

I am thinking the database has been corrupted. Did you try to delete it per my previous post?