Name of Backup-file

Hi

This option is added into v12 Advanced and will be available in v12 too very soon.

You can try it using v12 Advanced Beta https://www.acronis.com/en-us/business/backup/beta/#registration

Hi,

Please let me know when this option will be available?

Regards

Hi,

This option is already available in Acronis Backup 12.5 which was released just recently (it can be installed as an update for Acronis Backup 12).

Thank you.

Hello,

Great

I hope this version is available for Linux!!

Hi,

I have now the 12.0 version for Linux. My backup file name is like that:

But the real name of the file is:

I don't want "_2017_10_12_04_00_26_503D" on the name of this file.

How can do?

Hi Vicent,

Appending the date timestamp cannot be avoided for Backup format version 11 (defined in Backup Options->Backup format) - the backup filename option won't affect this specific. With default backup format version 12 the name will be matching the template you specify.

Thank you.

Hi Vasily,

I tried with format version 12, for the first backup, it's ok, but for the second backup there is also numbers after the name.

For exemple, it was SRV-ABAS-0001.tibx, and the day after SRV-ABAS-0002.tibx etc...

I want only a complete backup every day with the same name of file.

Hi Vincent,

The current backup creation logics prevents situations when the last backup in chain is lost, which will happen if we try to overwrite the same backup each day. Still we understand that in some specific scenarios it's a valid approach to discard the previous backup by overwriting it with new one and we'll add corresponding option to retention rules in future updates.

In the current version to achieve the goal you describe you'll need to set up retention rules to delete backups when their number exceeds 1 AND set up the backup scheme (in Scheduling settings) to "Always full". There will be still 2 files generated as the result (one small .tibx with metadata + 1 large .tibx with actual data), but physically it will be a single archive and the space consumed will correspond a single full backup. The presence of 2 files is necessary for internal work with the archive and consistent updating of the backup chain in our current Acronis Backup architecture (it's an architectural specific which should not affect the actual user experience).

If you specifically need to have a single file (not sure though why this may be required), then the only option is to run Pre-backup script which will physically delete the existing backup file before starting a new backup (Backup Options->Pre/post commands).

Thank you.

Hello Vasily,

On your first way, is the problem, the .tibx File is going bigger and bigger, show my last post.

On the second way, if you delete everything with a script or manually, the next backup fails, because, i think the .xml file is needed for further backups. 

I have tried everything to solve this, because, i am on of the persons they need, daily full backups on RDX Media.

If you have any ideas to solve this, i will be very happy.

best regards Yavuz

Yavuz,

The .tibx will grow up only until its big enough to contain the backup data in accordance with the retention policies. In the method suggested by me above ("Always-Full" scheme + retention by number of backups = 1 + apply retention rules after backup), the space for only a single full backup will be consumed, even though it will be creating 2 .tibx files. I've verified this scenario myself to confirm that it works of course.

Also the .xml files are related to backup format v11 only (for .tib files), so solution via scripting is still applicable. This method I've also confirmed myself by adding a pre-command which removes everything from folder which is used as destination for the backup - the full backup is always properly generated in this folder.

However all the above is completely not applicable to locations managed by Acronis Storage Node, where it is highly not recommended to do any manual manipulations with the .tib files. The managed locations on Acronis Storage Node are not intended to be used along with RDX drives used as backend storage (that's what you seem to try in the thread). For your scenario you should therefore avoid using managed locations. Since you just need a full backup - select RDX drive as local storage, or share it over network as SMB share.

Thank you.

Hi Yavuz,

I would like a backup file like "Acronis true image Echo". I'm using on other server, Acronis 11.5 (It works well on it).

I can use a backup file V12 but wich pre-command to delete all files on one specific folder?

With this version, the first backup has the good name, this is why I must delete it every day!

Hello Vincent,

you can do it like that: 

del /q x:\"YOUR FILES IN FOLDER"\*.*

@Vasily

i will test it on next week and give a feedback.

Thx for you help.

thanks for sharing

Is it necessary to put a letter drive on the folder?

I´ve never tried it before, with smb share. In this case, i would create a batch script.

You can test it, and give us a feedback.

You can create a batch script, I will test it, and give you a feedback with pleasure.

Build a batch with .cmd ends.

Put in:

net use "driveletter" \\SHARE 
cd "driveletter"
del *.* /q /f /s
net use "driveletter" /delete /yes

Configured it like screenshot below.

It´s working, i tested it.

And:

I´m not here to do your job, but i created this, because i have a big heart. ;-)

Hi Yavuz,

Many thanks for your help...

But is it really necessary to apply a letter drive?

My way is like that : smb: //srv-nas/bac-srv-abas/

I'm not under Windows, I'm under Linux system :-(

Oh, i don´t read it before. I´m sorry, i don´t work under linux with acronis, i can´t test it. Write a message to Vasily, maybe he can help.

Hi,

For Linux agent the commands could inserted in a bash script. I've followed instructions from this article to mount the share before the backup, clean up it's contents and unmount thereafter (confirmed that it works on Ubuntu):

1) First you need to have samba and cifs-utils installed on the machine running Agent for Linux:

#sudo apt-get install samba cifs-utils

2) Then create a Bash script to mount windows share folder in Linux using samba:

#mkdir /mnt/smb

#touch smb.sh

#chmod +x smb.sh

#vi smb.sh

3) Write the following into the smb.sh file using "vi" (or any other text editor):

#/bin/bash

SERVER_IP="192.168.1.1"

SHARE_NAME="c$"

USERNAME="samba user name"

PASSWD="samba password"

DOMAIN="domain"

mount.cifs //$SERVER_IP/$SHARE_NAME /mnt/smb/ -o username=$USERNAME,password=$PASSWD,dom=$DOMAIN

rm -rf /mnt/smb/*.tibx

umount //$SERVER_IP/$SHARE_NAME

4) Copy the created smb.sh file into some folder (I've used /tmp in my example) on the Linux machine and create /mnt/smb mount path there (mkdir /mnt/smb).

5) Configure pre-command to be executed as part of backup plan:

Command to run: smb.sh

Working dir: /tmp/

See example:

Hope this helps.

Thank you.