Direkt zum Inhalt

Drive Resize caused Full backup on *_inc_b1_s2_v1.tib

Thread needs solution

I uninstalled True Image 2018 v11530 (it was doing 'odd' things).  I removed Acronis where possible ?safe? from the registry.  Installed ATI 2018 v12510.  Renamed all prior .tib files to a sub-dir (_prev01).  Created new backups (5 partitions, 1 backup each).  Did incremental this time rather than Diff (diff taking too much space on NAS).

Question / Information desired relates to my G partition.  It was ~1.3 TB on a 4TB drive with 2 other partitions (F & U).  The *full*b1_s1_v1 backup did fine, ~1 TB.  Free space on G was tight for what I have planed so I added 350 GB from U (ADD12).  No problems with that.  When I checked backups the next day, the *inc_s2 was ~1 TB also, seems ATI saw it as a 'new' drive that had never been backed up.

Has anyone run into same/similar?  Bug or Feature?  Below is a dir of the NAS drive for this backup.

Not really an issue, although I would have preferred an s2 incremental that was a ~100 MB rather than a TB, new files are large audio files, but don't change once placed.  No issues with the other 4 drive backups (so far, only have 2-3 versions for each).  Going to take a month and a half before it purges.

thx, lo

 Directory of z:\G_Incr_ATI2018_Backups

2018-06-25  12:56    <DIR>          _prev01
2018-06-28  03:20   923,138,877,440 G_Incr_13_45_ATI2018_full_b1_s1_v1.tib
2018-06-29  02:37   923,138,637,312 G_Incr_13_45_ATI2018_inc_b1_s2_v1.tib
               2 File(s) 1,846,277,514,752 bytes
               3 Dir(s)  4,570,408,214,528 bytes free

0 Users found this helpful

Lo, welcome to these User Forums.

Resizing your partition will cause any backup to be equivalent to a new full backup because you have effected changes to the majority of sectors on the drive, i.e. by data being moved during the resize process, and may also have caused the partition identifier to be changed too.

I would recommend starting a new Full backup after making this type of change for these reasons alone, but also to always have a backup before making such changes to protect against any data loss if something goes wrong!