Why do I have to run the Verify Task and can it help if there is hardware failure?
Like any backup verification, there is no protection from future hardware problems. For example, you could verify all recovery point in a Disk Safe and they are all OK. Then you could have a hard disk controller failure where it corrupts some data causing the data to be useless later because of a hardware fault (we see this happen).
What the Verification is good for is catching hardware problems early. If you run a weekly verify and notice they start failing contact technical support with the error. The error would be caused by either an unclean shutdown of the CDP Server and Disk Safe while it was being written to, or by a hardware issue. Tech support can recognize the difference.
You can read about what we have done with the CDP 3 Disk Safe to make it impervious to unclean shutdowns, power failures, and crashes here: Disk Safes.
|Page: Verifying Disk Safe (Archived Knowledge Base 2.0) Labels: disk_safe, verify|
|Page: What Does the Verify Recovery Point Task Do? (Archived Knowledge Base 2.0) Labels: cdp_server, disk_safe, verify|
|Page: Using Verification to Detect Hardware Problems (Archived Knowledge Base 2.0) Labels: verify, hardware|
|Page: What Does the Verify Disk Safe Task Do? (Archived Knowledge Base 2.0) Labels: verify|
|Page: How Often to Run Verify? (Archived Knowledge Base 2.0) Labels: verify|
|Page: Verify Task and Fsck (Archived Knowledge Base 2.0) Labels: fsck, verify|