Acronis creates extra tib file while imaging to network location

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Messaggi: 1
Commenti: 0

Hello,

I have been battling with this behavior in both 2011 and 2012.

If I use the bootable media to boot and create a full drive backup to a network location, the process always works, but at the end creates a second tib file that is always 512 bytes.

Example: I boot the ATI 2012 bootable disc and do a full disk backup of the machine. For a location, I select \\server\share\BACKUP.tib

While backing up, everything looks good, but when it finishes, there will be 2 files:

BACKUP1.tib
BACKUP2.tib

The second file will be 512 bytes and appears to be pretty much empty. But, if I delete it, the image is broken.

How can I prevent this? If I use a flash drive to backup to, it will finish with one BACKUP.tib file. I am trying to keep things organized, and having a bunch of these tiny files is getting annoying. Any ideas?

Thanks
-Dennis

Mer, 11/09/2011 - 16:18
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Messaggi: 24
Commenti: 3268

Hello Dennis,

Welcome to our Forum, we're glad to greet you here! I understand your concern, and would like to help you.

We don't have any known issues registered that would match your description, and the situation requires investigation. Could you please provide us with the following information (if you don't want to attach it to the thread, you can send it to me via Private message, or in case of emergency contact support directly): 

  1. Acronis Linux Report from the bootable media
  2. Screenshot of the backup location
  3. Whether the result is different if you're specifying the path to the server using the ip-address (\\ip-address\share)

This data might help to localize the cause of the problem and thus find an appropriate solution for it.

Let us know if you have any questions, we will help.

Thank you.

Gio, 11/10/2011 - 15:02