HDD's fail,... It is a fact of IT life that is unavoidable.
Now I will say this, because I do it, but not exactly for the same reasons as above.
I do use images for machines for fast recovery. Most of my images however are stored on a drive array (of course raid5). Which in turn is backed up to tape.
There are some images that are on "hot standby". That is they are already loaded onto a drive. But their master image is still located on the file server.
At no time though are these images updated/added to. They are simply the bare neccesity to get a system deployed rapidly.
A different archive method "MUST" be used when making backups. That is the whole point of backups. You must backup to a different physical medium.
An example of a fast backup method is SQL. While i use the native backup method in sql to create backups of itself. And those backups are created to a different array attached to the servers. Those backups are also backed up to tape.
The onlyreason they are backed up initially to disk, is for restore speed only. They are not meant to stay on their permementally. In fact only 2 days worth of backups/trans logs stay on the backup array.
For user's: backing up to disk is a very very very very bad thing. It is useless, pointless and a really bad idea. If you have to, make a backup to disk then burn it to cd.
But, mark my words. The backup drive will fail, and so will the primary. Where will you be then.