Backup File Location(s)?

Russell,

You have different types of backups here. It looks like you have been using ATI in combination with Win 7 backup.
Nothing wrong with using different technologies, but if you can, it is even better to use them on different disks, and keep one disk off-line.

You also use a Non-Stop Backup (again different technology) on the same disk? If you overlap the content of the Non-Stop Backup with the regular Disk and Partition backups, it is an overkill on the same disk again.

Here is what I suggest:
- do a disk and partition backup of all the partitions on your disk where you system is. Use a chain of full + 3-6 incrementals (daily or weekly). Keep always at least one full chain (auto-cleaning options),
- do a Win 7 backup on a spare drive that you keep disconnected from the computer, and that you refresh from time to time (maybe every month),
- keep the Non-stop-backup limited to content that you change frequently and that you want to keep versions of for as long as your space allows, given your disk and partition backup, or simply cancel the NSB: delete it from ATI. If you have hard times cleaning up versions, cancel the NSB and replace it with targeted file backups (easier to control the space and retention policies).
- turn off windows system restore on your disks if you want.

Note: there is no need to turn on the sector-by-sector option for a disk and partition backup. A disk and partition backup is typically much smaller (with normal compression turned on) than the original data.

Pat,

Thanks for the reply. I was thinking ATI would turn off Win7's own backup program when integrated but found out otherwise. It's off now and the Win7 b/u's are deleted.

I have set up a new scheme as custom using "full + 6 differentials" scheduled daily @ 11:00 pm, with auto deletion after 14 days. Is this reasonable? I will keep the non-stop for now, but if this scheme works as expected will likely delete the non-stop.

On another note (maybe for a separate thread?) I installed the plus pack and am only seeing a "WinPE ISO Builder" option. So what happened to the most intriguing feature, "Universal Restore"? Is there no interface for it? Not even a help file for the Plus Pack?

Thanks!

Russ

Russell,

You should use the "keep only the X most recent versions" option. It works better and is easier to predict.

With the Plus Pack, you need to create a new recovery CD that will show the Universal Restore option.

Pat L wrote:

Russell,

You should use the "keep only the X most recent versions" option. It works better and is easier to predict.

With the Plus Pack, you need to create a new recovery CD that will show the Universal Restore option.

I'll do that. So, if I select "two" to keep is that two complete chains or just two backups (one full and one differential)?

And about the naming convention, how will these "full with differentials" look as far as file names? And do I have any control over this?

Thanks for your patience!

Russ

If you select 2, here is what is going to happen, if you set it to have, let's say, 5 differentials after a full:
First, ATI will create Full1, then 5 differentials,
Then, ATI will create Full2, then 5 differentials,
Then ATI will create Full3, THEN it will delete Full1+its 5 differentials, and then, the next time it runs, it will continue building differentials on Full3.

Since ATI has some issue when you delete intermediate differentials WITHIN a chain, I don't see much interest in having differentials personally, so I use only incrementals. This consumes less space and allows me to keep more chains for security. Remember I backup with Win7 in parallel anyway.

Don't add tags to your TIB file names. When you set up the task, choose your destination, that will let you set the name for the TIB file. Keep it simple, like System. Don't use numerals at the end of the name.
The first full will be called System, the first incremental or differential will be called System2 (go figure), the second System3, etc. The following full will be called System(1), the first partial after that will be System(1)2, etc.

This is so NOT what I was hoping for... My first backup (full) was 55.5 gigs as expected. The second (first differential in chain) was 91.3 gigs! At this rate, I'll need a 100 terabyte server rack to backup a weeks' worth of data. I guess I'm too dense to understand the principles here. I think I'll just revert back to the scheme I'm familiar with from my many years of using Stomp, just one weekly full and keep the three most recent. It looks like all the "bells & whistles" that got my attention with ATI are just way over my head...

On another note, my Win7 was showing some "hinkiness" so I decided to try and restore a previous session of my non-stop backup (which BTW, did the trick). I restored only my "C" partition (29 gigs) and it took over 3 hours! The progress bar timer was so whacked it was actually funny. For the first 20 minutes, it showed "1 minute remaining", then it went to "4 hrs, 10 minutes" and started getting longer, then semi-accuracy took over for awhile. Again, "1 minute remaining" for 10 or so minutes and then "40,554 days, 18 hrs" and dropping by about half that "interval" every few minutes until a reboot notice with "5,632 days, 4 hrs" left. I'm really not impressed with this program. I was hoping for some "intuitiveness", but instead guess I'll be spending a few days reading through the KB in hopes of some enlightenment...

Russ

Russell,

Miscellaneous:
a. Are you running the most current version of 2011 which is 6696?
b. As for the 91.3 size, make sure your Windows or your TIB backups are not being included in areas covered by the Diff. Use exclusions if necessary to bypass certain folders or types.
Another possibility might be if your task is marked not to delete original. If your first two resulted in full type backups and the third backup is a smaller sized differential, then the explanation and action might be a normal increase due to actual increased disk writings after the first backup occurred.
c. Also check disk for errors which can cause large files. From a command prompt: Chkdsk x: /r    (where x is actual drive letter)
d. One chain= 1 full plus any diff; or 1 full plus any inc; . The creation of a new full begins a new chain.
e. Actual practice seems have better results when you determine how many backups to keep based on number of chains rather than after x number of days or rather after x amount of size.
f. Actual practice seems to have better results if task not edited.
g. Running defrag should only be done just prior to a full backup. Running prior to a diff or inc will cause all file movement to be included in the upcoming backup. Acronis diff or inc backups are based on changes of disk sector position so any relocation of files will be included.
h. As a matter of preference, I use two underscores as the last two characters of the backup file names.
i. Identification of type of backups can be assisted if you double click on the task name and look at the various slices of backups. See attachment.

Directed to Grover....

Grover, hello again...
You mentioned in your post above, item "f", " Actual practice seems to have better results if task not edited."

I have had trouble with a task destination that has been working for several months... I noticed one of my backup tasks was sending the data to G:\Acronis Backups when it was originally set up to send to G:\Acronis Backups\MyWeb. When I tried to edit the destination, Acronis TIH2011 w/latest update, refused to change the destination. Out of frustration, I just deleted the backups and removed the task. I then created a new task with the proper destination and started all over. That was not my best solution because I lost several iterations of the backup that may have been useful if I had trouble with some of the website backups that were stored there.

You seem to have an immense knowledge of the TIH systems and I'd appreciate your thoughts regarding the editing or correction of the storage "Destination" of a task.

We are using TIH2011,PPack,Latest Version. These backups are extremely important to us and we get nervous everytime we read the forums.... I am sure you understand. By the way.. Our storage disk, "G:" is a dedicated internal data storage drive and not used for any other purpose. We often test backup restores on an external sata drive for peace of mind.

Look forward to hearing from you.
Steve
Perdido Beach, AL

Steve,

Keep in mind that I am a volunteer and not associated with nor employed by Acronis. My comments are based on my own testing or experiences. Thank you for the personal comments. It's nice to know someone is reading my postings.

Acronis enables task editing and allows you to make those changes. The program also allows you to save different tasks backups to the same folder. This has been in effect since beginning with the 2009 version. Based on postings from this forum, posters have advised
a. the meta file database becoming corrupt and backup retention or cleanup not occurring as indicated by option settings.
b. task settings either changed or not retained via creation or editing.

As a result, I have tried to find what works for me rather than what Acrois says is possible. Like you, I want my backups to be restorable and predictable so here a few personal rules which I try to employ.

c. Every task has its own individual storage folder.

d. Many of the problems reported have involved an edited task, therefore, I go to great lengths to avoid editing a task. Like--- you can't changes horses in the middle of the race, etc. If you need to change the options, then start a new task. Undoing a failed task is difficult which is why I just start over with a new task with my revised settings.

e. I try to prove that backups/restores work as intended. Under numerous testings, the "retain x number of backup chains" has worked for me. I do numerous actual partition and/or disk restores so I have a pretty good comfort level that I can recover if and when needed. However, I do have redundant backups and to use alternate backup and restore methods to make sure I always have a Plan-B just in case Plan-A encounters any problems--like don't put all your eggs in one basket, etc. Keep in mind that I have just a personal computer so I may have greater flexibility or freedom.

f. Often times, when a problem is reported in the restore or clone area, I will attempt to replicate the same issue or write some guides to help others avoid the same issues.

g. I would suggest you open a support ticket for your situation and seek their explanation as to how this might have been prevented.

Gentlemen,

Thanks for all your help. Grover, thanks for all the reading! Mea Culpa on the backup size, I'd forgotten about moving an older Win7 backup to my C drive and not excluding it. Sucks to be old! I do have the latest version and I'm starting over from scratch on the "full + diff" scheme for another try...

Russ

EDIT: Working much better now, waiting to see if the "cleanup" feature actually deletes old chains and frees up disc space. Once I get a couple chains, I'll delete my non-stop, as it just keeps getting bigger and cleanup does nothing to free up space...

Russ,
Age is a non-issue as we all have that issue at one time or another.

The cleanup will only work better if you started with a fresh task. If you edited a task and made changes, there is a high degree of probability (IMHO) that the task will not produce the desired results.