+------------------------------------------------------------------------------ | On 2009-11-09 12:18:04, Ellis, Mike wrote: | | Maybe to create snapshots "after the fact" as a part of some larger disaster recovery effort. | (What did my pool/file-system look like at 10am?... Say 30-minutes before the database barffed on itself...) | | With some enhancements might this functionality be extendable into a "poor man's CDP" offering that won't protect against (non-redundant) hardware failures, but can provide some relieve in App/Human creativity.
Alternatively, you can write a cronjob/service that takes snapshots of your important filesystems. I take hourly snaps of our all our homedirs, and five-minute snaps of our database volumes (InnoDB and Postgres both recover adequately; I have used these snaps to build recovery zones to pull accidentally deleted data from before; good times). Look at OpenSolaris' Time Slider service, although writing something that does this is pretty trivial (we use a Perl program with YAML configs launched by cron every minute). My one suggestion would be to ensure the automatically taken snaps have a unique name (@auto, or whatever), so you can do bulk expiry tomorrow or next week without worry. Cheers. -- bda cyberpunk is dead. long live cyberpunk. _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
