The laws of backups stipulate that you will only find out the tape drive has been systematically scribbling random gibberish over the backup tapes when your file server eats the filesystem.
So guess what's happened to the Informatics file server here?
Yep, someone at the Lizard Alliance apparently hit the "scramble" button for Sussex, and got the Informatics file server to eat the disks. It seems that they've been planning this for a while, as the backups for last weekend are mysteriously corrupt.
So guess what's happened to the Informatics file server here?
Yep, someone at the Lizard Alliance apparently hit the "scramble" button for Sussex, and got the Informatics file server to eat the disks. It seems that they've been planning this for a while, as the backups for last weekend are mysteriously corrupt.
no subject
Date: 2006-05-05 02:05 pm (UTC)Of course, I only have 1 customer who uses a tape backup system. All of my other customers use a tar-to-drive-over-net system where the backups are kept on secondary file servers. Much quicker backup/restore system. Even my tape drive customer uses that system. I create a master .tar.bz2 backup file on the server with the tape drive. Dump it to tape while at the same time sending it via 10G eather over to the master fileserver. So far, never had an issiue with either archive being corrupted when we needed to restore data.
Cheers