"Don't keep your eggs all in the same basket" is good advice. Two vastly different storage philosophies compete. One is rapid restore of a mistakenly deleted file. That happens fairly often. We used to do a full backup to tape every night, but that consumes vast quantitites of tape and hits the network pretty hard all night long. Such things as incremental or differential backups require much more handling to restore a particular file. I still do selective full backups weekly (not all file types) to tape just for the archive but we are also experimenting with DVD-R. Only the tapes contain the full permission structure information.
For immediate restoral purposes I am using rsync hosted on Linux to synchronize storage devices. Using the crontab, I instruct it to make 7 versions, one for each day of the week. Rsync is amazingly efficient; copying only changes and makes a replica (without all the permission info, but the permission structure is not complex in our case). Over the wire, rsync has some added benefits -- bandwidth limiting, compression, and selective copying within a single file. What that does is hash the source and destination files (if they both exist), discover just the changed pages *within* the file and transmits only the changed pages. A test required only 30 kilobytes of wire transmission to synchronize two 11 megabyte spreadsheets in which one cell had been changed.
So when the daily "oops" happens, I just type in "locate xxxx" where the filename replaces the x's, look at the path to find the most recent one (last night usually) and copy the file back to the NAS device. To reduce the potential for catastrophe, the Linux box is permitted to read (only) the directory trees on the NAS to perform its synchronization; restores go to a special writeable folder and from there must be dragged to the final destination. Some commands entered into Linux can be VERY destructive to itself and any mounted storage. "How do I destroy thee, let me count the ways!"
BEWARE file size limitations; some storage solutions fail if you have a file >8 gigabytes, and that includes some implementations (maybe all of them) of the zip compression format.