> This is going to be used for my parents business (Im > merely setting it up for them and then leaving it.) > So basically what I want is reliability and > redundancy. I want there to be very little chance > of data loss as the business they are in requires > them to keep all documents.
Ok, ZFS is good, but what you really need here is a proper backup strategy. If need be, skimp on the server so that you can create a good backup system. Never, ever, keep all your eggs in one basket. If their data is that important, you need to get a copy off-site, and you need some kind of automated process to do that - people don't realise how important backups are, and if you leave it to a manual system it won't get done or checked. I'd be very tempted to use zfs send/receive to send the data to another machine, even if it's just a virtualbox server you run at home. PS. You're also going to need some kind of remote monitoring of that server - sure, raidz2 will keep your data going when a disk fails, but unless you know that the disk needs replacing, what's going to happen? What's going to happen to that server in a couple of years time when you've forgotten all about it and suddenly get a call from your parents to say it's stopped working? If I were you, I'd write a script to run "zpool status -x", and email you if there are any errors. PPS. Yes, you can and should scrub regularly, running that once a week is as easy as adding a line to crontab. -- This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
