How do I know that my backed data/ disk image has the same size of the original backed data
Hi, there.
Simple question. How do I know that my backed data/ disk image has the same size of the original backed data, and that no file has been missed during cloning? since TI do not make an identical copy of the original data as it uses its own format I can't know if everything has been backed correctly?
Any idea?
- Accedi per poter commentare
Thanks for the help.
Isn't this fact (having to restore to ensure your back up is identical to original) tempting enough to most of you to just jump and look for another application for data back up, for me I'll check again Cobian as it support backing up to normal files, so the end result - if things went alright - is two identical back ups without the hussle of having to restor data (which is waste of effort to say the least).
What do you think?
- Accedi per poter commentare
Anybody who uses any backup program and does not ensure that they can restore their files properly has only done half the job. You don't want to find out about restore problems when you really need the restore to work.
You can restore the TI backup and then compare the files restored as you would compare the Cobian or other file-based backup.
For the record, I use TI for making images of my C drive so I can easily restore a bootable drive. I use SyncBack for my data files which are never kept on the OS/apps partition. I don't use TI for the data files not because I think it might miss a file but because I don't like stuffing all the files into a large proprietary format container file. BTW, I've never had an indication that a TI image has missed any file and I've used it since TI9 which is about 6 versions ago.
- Accedi per poter commentare
But TI DID repeatedly interrupted back up processes to tell me that its facing a "bad Sector" and it would not continou the back up process untill I hit OK to the message it produced. Anyone had that or something similar.
- Accedi per poter commentare
A bad sector on a drive is not unheard of by any means and it could be an indication the drive is going to fail. Sometimes the bad sector is caused by a head strike on the platter and this can release particles from the head material. These microscopic particles float inside the drive and can collide with the head upsetting its "flying" characeristics and causing another strike. This is just one scenario there are other reasons for a bad sectore as well.
What you want to do is track down the reason for the message. The first thing I would do is run chkdsk with the command: chkdsk X: /r replace the X in the command with the drive letter of the partition being checked. A reboot will likely be required for some partitions. Check all of the partitions on the drives in question and don't forget to use the /r option. It will take some time to run the command on large partitions sine the /r does a check of all of the partition not just the file structure. The option will also map out the bad sector if possible.
If chkdsk reveals a lot of bad sectors consider replacing the drive. If you don't want to do that or it is only a few sectors then re-run chkdsk at some interval to ensure that more sectors are not failing. If more sectors are found after a chkdsk repair then it means the drive should be replaced.
- Accedi per poter commentare