Salta al contenuto principale

Full Backup Incremental Backup

Thread needs solution

Hello

On this computer in marketing the second hard drive is with 160GB of photos, articles. It is imperative that I have a backup. Before I installed Acronis 2013 I would at least once a month do a full backup to a freshly formatted hard drive. Then I purchased and installed Acronis several months ago.

Last week I did a full backup to a dedicated 500 GB NTFS Hard drive the folder Amy that holds 160GB of data. The backup was successful. With Acronis I had scheduled a weekly incremental backup to start every Saturday morning.

Oh I forget ... why I used the 500GB hard drive was because I started out using a 250 GB hard drive.
I did a full backup to that 250 GB hard drive - 160GB data/ full backup - with weekly incremental backup applied. What happened was that I got an error message that there was not enough hard drive space to do the incremental backup. What confused me and today I remain confused was that I thought an incremental backup located any 'changed/altered files' since that last backup - and then created the incremental backup.

That this data is precious I bought a 500 GB hard drive. Now I have room for three full 160GB backups!
Plenty of digital space....

Today the 500GB holding the original 160GB full backup failed to do an incremental backup --- with the error insufficient hard drive space? I am looking and see ***full.v1.tib (160,530,119kb) and there below the ******inc.v1.tib (2,620,900kb). I have to assume that this inc.v1.tib (2,620,900kb) are the failed fragments. I don't know.

Having an absolute assurance that I can run a scheduled incremental backup would be encouraging.
What did I do wrong, what am I missing? I could buy a 1TB ...for the 160GB - that's how urgent this situation is.

Thanks
Chuck M

0 Users found this helpful

Chuck wrote:
Today the 500GB holding the original 160GB full backup failed to do an incremental backup --- with the error insufficient hard drive space? I am looking and see ***full.v1.tib (160,530,119kb) and there below the ******inc.v1.tib (2,620,900kb). I have to assume that this inc.v1.tib (2,620,900kb) are the failed fragments. I don't know.

The 160 full_b1_s1_v1 is the full backup as indicated by its name.
The next line contains all the changes to the disk since the last backup and is the incremental backup.
The 2,620,900 is the inc_b1_s2_v1 is the first incremental (s2) file as per its name.

Chuck wrote:
That this data is precious I bought a 500 GB hard drive. Now I have room for three full 160GB backups!
Plenty of digital space....

A logical assumption but unfortunately not true. To start with, the 500 has only 465 of usable space.

The program will not delete the oldest backup until AFTER its replacement has been verified to exist. So you always must allow room for the extra temporary 160GB of space. This leaves you with 465-160=295 usable.

If you have backup set to perform 4 or more incremental each with size such as 2.6gb, this reduces the usable space by another 10GB so your usable space becomes 275gb or 1 full plus a few incremental.
----------------------------------------------------
Click link #2 below and review the illustration 11-Diff.
You can continue to use the 500 but I would suggest you create a new backup task and set up your backup scheme as per the example of 11-Diff/

Based on using the available 465GB storage space
Change the example of 6 to 4 or 8 differential
Change the example of "store no more than 4 to your setting of 1
Do take the time to read all the text comments that accompany the 11-Dif example.

I am suggesting that you use the diffential type rather than the incremental type. Read the link below for more details as to why.
http://forum.acronis.com/forum/40810

With these settings, the program would complete whatever number of incremental or differential indicated by your settings. (Chain =1 full plus your settings of x inc or diff type backups. )
Next it would create the next full followed by the immediate deletion of the oldest chain.

So as you review your newly stored backups, you would never "see" a listing of two full backups. Only the current full plus whatever number inc or diff you have chosen to create at that moment of inspection.

If you intend to add a larger storage disk to your equipment, the 2 TB costs only slightly more than the 1 TB. It is always safer to store your backup in two disks rather than 1 disk.

One backup task could create backups to the 500 while a different task (drive letter X) could create additional backup to the 2tb disk (drive letter Y).
User assigns special drive letters to storage disk to avoid the drive letter change often caused by the insertion of a flash drive or camera. Assigning a high drive letters helps to keep the backup task functional or edits are not required. Backup task edits are often the cause of backup retention not working correctly.

Some of us use screen reminders to ourselves before backup time to be sure and attach the storage disk. The use of DriveNotify is also very effective to making sure the correct disk is attached before backup is enabled to continue.