On 05/31/2011 12:26 PM, Khushil Dep wrote:
Generally snapshots are quick operations but 10,000 such operations would I believe take enough to time to complete as to present operational issues - breaking these into sets would alleviate some? Perhaps if you are starting to run into many thousands of filesystems you would need to re-examin your rationale in creating so many.
Thanks for your feedback! My rationale is this: I have a lot of hostingaccounts which have databases. These databases need to be backed up, preferably with mysqldump and there need to be historic data. I would like to use ZFS snapshots for this. However, I have some variables that need to be taken into account:
* Different hostingplans offer different backupschedules: every 3 hour, every 24 hour. Backups might be kept 3 days, 14 day or 30 days. These schedules thus need to be on separate storage, otherwise I can't create a matching snapshot schedule to create and rotate snapshots.
* Databases are hosted on multiple databaseservers, and are frequently migrated between them. I could create a ZFS filesystem for each server, but if a hostingaccount is migrated, all backups will be 'lost'.
Having one filesystem for each hostingaccount would have solved nearly all disadvantages I could think of. But I don't think it is going to work, sadly. I'll have to make some choices :).
Regards, Gertjan Oude Lohuis _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
