Skip to main content

Back Up to NAS fills drive C:

Thread needs solution

f I select a NAS as the destination for a full backup of my PC (Windows 10 pro), the C: drive is filled with a large .tibx file, and the backup fails.

Can I avoid that?

--
Eigil

0 Users found this helpful

Eigil, welcome to these public User Forums.

Please see forum topic: True Image 2020 -Backup option settings loss - where the same issue has been reported by other users with different versions of ATI.

Acronis have asked for users to submit Feedback including an Acronis System Report from affected computers.

See KB 57216: Acronis True Image: Send Feedback for help with the Feedback process.

For the immediate problem, please reselect your NAS Destination for your backup task, delete the .tib file that was written to your C: drive and check all the other task configuration settings, in particular automatic cleanup and email notifications.

I had the same issue with a .tibx file being written to C: but this has only happened (for me) the one time before doing as above.

I am having a similar-sounding issue on 2 of my 3 licenced Windows 10 PCs in a domestic network. It's so frequent that I have had to disable scheduled Back-ups, limiting the usefulness of ATI. The Backup Scheme is set to Differential with automatic clean-up. ATI 2020 first successfully puts a Full .tibx on the NAS then, a week later, tries to run a scheduled or catch-up differential back-up (as it is set to do) and seems to ignore that it had created the first Full backup and also that it had correctly located it on the NAS. It now creates another Full backup and in error, puts it on the root of C: drive of the Source PC. Eventually it either causes performance problems on the PC or the Backup fails with the message that there's not enough room on the destination drive. When you click on the Right-hand ATI icon 'change destination drive' on the Backup screen to check what is happening, the path shown at the top is the correct one. However the bright blue bar is highlighting the incorrect tree to the source PC. I have some days ago uploaded a System Report for the issue. I dont know if it is relevant but the NAS is a Synology 218play and has a Fixed IP address.

Yikes!  I haven't seen this yet, but I've been limiting my time with 2020 until more of these bugs have been worked out as the validation length issues continue to be a sticking point for me.  

Everyone that experiences this needs to submit a direct support ticket to Acronis AND submit feedback in the app!!! In the interim, the only thing that seems to be helping (some?) is to re-pick the source and/destination and run the backup to save the change - and hopefully it will stick.  If not, turn off the MMS service in the interim, re-pick backup settings (source, destination, schedule, etc.) and hopefully that resolves it until a fix comes out.

I have this exact problem.  I created a post for this but it has yet to be approved.

I have two different Windows 10 PCs with a new NAS with 3+TB free.  Brand new ATI 2020 copies installed on each and updated.  Set to create a full backup (created find) and then do incremental every weekend.  This was the first weekend.  Both PCs failed on the incremental backup and I found huge tibx files on each C drive completely filling them with the 100+ GB files/  The first incremental Backups on both PCs failed due to insufficient space.

 

This is a side-effect of the known issue with backup settings being reset.

See forum topic:  True Image 2020 -Backup option settings loss - with hundreds of users affected.

I have also had the same issue on one of my computers backing up to my own NAS.

Stop the Acronis Managed Machine Mini Service and set the Start up type to Disabled to prevent the problem coming back until the issue from the Acronis Dashboard servers has been fixed by Acronis.

I'm having exactly the same issue as below. I even deleted my previous backup job and created a new one. First backup is full and on my NAS. But then schedule ran day later, seemed to ignore the full backup, then tried to create full backup on my root c drive (unsuccessfully as it ran out of disk space). Just checked my new backup job and it is correctly pointing to my NAS. 

Steve Atherton wrote:

I am having a similar-sounding issue on 2 of my 3 licenced Windows 10 PCs in a domestic network. It's so frequent that I have had to disable scheduled Back-ups, limiting the usefulness of ATI. The Backup Scheme is set to Differential with automatic clean-up. ATI 2020 first successfully puts a Full .tibx on the NAS then, a week later, tries to run a scheduled or catch-up differential back-up (as it is set to do) and seems to ignore that it had created the first Full backup and also that it had correctly located it on the NAS. It now creates another Full backup and in error, puts it on the root of C: drive of the Source PC. Eventually it either causes performance problems on the PC or the Backup fails with the message that there's not enough room on the destination drive. When you click on the Right-hand ATI icon 'change destination drive' on the Backup screen to check what is happening, the path shown at the top is the correct one. However the bright blue bar is highlighting the incorrect tree to the source PC. I have some days ago uploaded a System Report for the issue. I dont know if it is relevant but the NAS is a Synology 218play and has a Fixed IP address.

Having the same problem with the latest version of Cyber Protect.

The first post I came across describing this was 13 years old! How is this still an issue?

Joel, welcome to these public User Forums.

If you are seeing this issue with ACPHO then I would urge you to open a Support ticket direct with Acronis to report it and get them to investigate what is happening and why??

I not seen any other users reporting an issue in the forums before yours today for a long time.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 2
Comments: 1727

Joel Barker wrote:

Having the same problem with the latest version of Cyber Protect.

The first post I came across describing this was 13 years old! How is this still an issue?

Hello Joel,

I have raised a ticket with our support.

The reference is 06056559.

You can expect a response from our support team as soon as possible.

Feel free to update this thread anytime you need.

Best regards.