File Directory Path Depth
Hi,
I have a question:
If I store my scheduled backup file in a deep directory path is the schedule more likely to fail or the file become corrupt?
Cheers.
Hi James F & thanks for the reply.
I have one more question and that is how do I make a system snapshot with TIH2011?
Also I've been told I can test a backup by restoring a single file; how do I go about doing this please?
I'm not sure what you mean by "system snapshot", but if your are referring to a point in time full system backup, that is the core purpose of True Image. Anytime you do a full disk backup and then any incrementals or differentials based on the full (as well as any subsequent full backups), each backup would be considered a recovery point or if I am on the same page as you a "system snapshot".
Item #5 at this link will show several methods of restoring single files or folders, etc.
http://forum.acronis.com/forum/29618
If your "system snapshot" is a reference to a prior version feature which was like the creation of a Windows Restore point, that feature was dropped in favor of the more complete backup as suggested by MVP James in the above posting.
Remember, if you want your backup to be able to create a replacement disk--should yours fail or you need fully to replace your system disk, the best type backup to have is a full backup which includes all contents of the disk and all partitions listed on the disk--as pictured in the Windows Disk Management graphical view.
The link below illustrates in more details regarding creating a backup/backup task.
Thanks James
Hi Grover,
Do you have to put underscores between words with both the file names & the storage folder of the backup?
Do you also have to put an underscore before the ".tib"?
John,
There is no rules as such but it does make identification easier. The program will add numbers to the file name so having an underscrore or dash is simply a separator before the number starts.
Thank you all for you helpful replies.
Sorry one last question Grover.
In your guide it says not to use spaces in either the file name or the destination folder. Is this still so?
It is still my preference and my recommendation but it is not an Acronis requirement.
I try not to create long file names.
Another Question:
I still don't quite understand the backup scheme.
With the custom scheme:
e.g: Weekly incremental backup that creates a full version after 3 increments with deletion of version chains older than 7 days.
So if 1 chain is achieved on the fourth week (Full Bckup/Inc/Inc/Inc/Full Bckp) how can a full chain be achieved if 1 chain is deleted every week?
Sorry if I'm making it more complicated than it is.
Note the illustration of figure 11-inc inside thiw link.
http://forum.acronis.com/forum/28705
This illustration is my recommendation as to how to set up your task. You can adjust the 6 and 4 examples to meet your needs. I do suggest that you cease to use your current task and create a completely new task pointing to a empty target folder.
I prefer the method of keeping x number of backup. I do NOT like using the settings which based on number of age of backup. Keeping x number of backups is easy to calculate your needs.
The program will create the replacement backup file before deleting the old file so always allow space for the temporary extra backup.
A chain is one full plus all associated incs. If parts of the chain deleted, only the backups preceding the deletion will be usable.
Thank you Grover.
When I performed my first backup the backup in the chain has extra characters on the end of the file name
e.g If the file name of the initial backup was called 'MyBackup' the subsequent file is called 'MyBackup1(1).'
Is this usual?
Yes, that is normal.
The next backup if an incremental will be mybackup1(2)
if a full, it will be
mybackup2, etc