Direkt zum Inhalt

ABR v11 Naming convention

Thread needs solution

I recently upgraded from ACR 10 to ACR11. I like to use command lines within a script so I can create a backup of my hard drive. I read the new listing of the commands and can back up successfully. The issue is when the backup file is created Acronis adds a date to it and some other gobbly gook. All I want is the backup name to be the name I give it not additional worthless stuff from the program. Is there a way to turn this feature off so I can name the backup file the name I want to give it?

Jim

0 Users found this helpful

Apparently there is --plain_archive option

In this parameter, you can specify an archive by the file name of a backup that belongs to the
archive; for example: --arc=my_backup2.tib.

If the archive does not contain metadata, the command will apply to the backup chain. (A backup
chain is a full backup and all of its dependent incremental and differential backups.)

This syntax is useful for archives created using the --plain_archive (p. 54) parameter.
...
Without this parameter, each backup will have a unique file name with the exact time stamp and the
backup type; for example: MyData_2010_03_26_17_01_38_960D.tib.

I read about this in the manual. When I tried it the first time, before posting in the forum, but could not get it to work. I will try it again and see if it will run.

Jim

Well, I just tried it again and no luck. Here is the command line I used. According to the manual all of my parameters are correct?

acrocmd backup disk --loc=J:\Windows 7\QuadGame3 --arc=QuadGame3HardDisk3 --plain_archive --log=C:\Program Files (x86)\Acronis\BackupAndRecoveryConsole\log3.txt

So why does it not work?

Thanks,
Jim

I'm not sure about this one - with space between Windows and 7
--loc=J:\Windows 7\QuadGame3
Maybe it should be --loc="J:\Windows 7\QuadGame3"
The same for --log (btw "program files" may be read-only if application is not elevated, it may fail because of it too)

The "space" between Windows and 7 is a true space. It is the exact name of the folder. I have not had any problem with Backup & Recovery 10 using the same folder name.

As far as the log file is concerning I changed it to C:\log3.txt. The backup ran but it move the backup file to the J:\ root and it attempted to backup the 1st hard drive and the external too. Very strange software update....must be buggy!

Thanks,
Jim

'backup disk' with no parameters backs up all disks in system. Folders and other parameters with space are quoted in commandline reference - e.g --loc="F:\my backups" --arc="my archive"