backup documentation

[sonuteklists]

This might be a odd question. We have a backup system which includes 3 tape autoloaders backing up machines on three different network segments. The backups are stable most of the time unless we run into issues such as tape-not-found, blank-tape-not-available, client-not-available, etc.
I already have documentation on what machines are getting backed up on what segment, time schedules, interval when which tape backup set gets recycled, etc.
But I somehow am not very satisfied with it. What I am trying to do now is to make the the documentation as detailed as possible which would explain recovery procedures, problem-solution examples, etc.
Could anybody provide me with a guideline or prototype backup document, either the one you use or even a industry standard one. I searched unsuccessfully in google for it.
Would greatly appreciate all comments.
Thanks a bunch.

 

[unclebulgaria]

Depending on how details you want to get, the pahrmaceutical industry has good guidelines. Try the GAMP 4 guide, from the ISPE (international society of pharmaceutical engineers).

It outlines what you should specify in your documents, and (i think, but don't hold me to this) might give you templates for the doucments.


Its pretty thorough, and stands up to regulatory inspection.




Womble free, always.

 

[sonuteklists]

Thanks a bunch. Any idea where I can get hold of this. Google??

 

[unclebulgaria]

Try

http://www.ispe.org/gamp.

It might cost a bit though, but you might get someuseful info from the forums.

Womble free, always.