What These Scripts Don't Do

These scripts do not post notifications via email or any other means. The XML output of these scripts can be communicated some other means such as a web dashboard or RSS feed.

These scripts do not analyze the verification output. Information such as the number of files, changes and versions can be obtained by this analysis. This information can then be used when estimating hardware requirements.

These scripts do not analyze the backup program output. The backup log file is saved in the log directory so you can conveniently inspect it.

These scripts do not perform a test restore from backup. This type of test is needed to insure the integrity of your backups. You must do it. If you don't, you don't know whether your backups are working.

These scripts do not cleanup old files that they have created. Old checkpoint, journal, log and backup files will need to be removed on a regular basis.

These scripts do not replace the Perforce metadata database with one created from the restored checkpoints. This would require restarting the Perforce server. Newer Perforce server versions typically do not require tree rebalancing obtained by restoring from the checkpoint.

These scripts do not implement off–line checkpoints