Disk image snapshots are grossly inefficient as configuration backups. On any systems with significant file system churn, such as a proxy server or logging server, each snapshot may represent a significant and unexpected disk usage on the back end storage array. It's also not safe or reliable for any database backups, inclding MySQL, PostgreSQL, or even source control tools like CVS and Subversion. If you need to preserve system files for just such problems, learn to do efficient backups. I recommend the old "rsnapshot" tool, available at EPEL. On Sat, Mar 8, 2014 at 6:35 PM, JacobV <nycfresh@xxxxxxxxx> wrote: > https://forums.aws.amazon.com/thread.jspa?messageID=481859񵩃 > https://forums.aws.amazon.com/thread.jspa?messageID=453572񮯄 > > This is a timebomb waiting to strike so many people who like do daily > snapshot backups and keep them for few weeks and not realizing their > snapshots are useless if they had accidentally mess up some boot related > file earlier on. > > Another scenario you mess up the sudoers file or the root authorized keys - > you'd have to loose a whole days data and go to previous nights restore just > for single file error like that ? > > If AWS marketplace is unable to remove this hardcoded rule then it's only > prudent to remove Centos from AWS marketplace and release it in the > community section instead ? > > Thoughts ? > > > > > > > _______________________________________________ > CentOS-virt mailing list > CentOS-virt@xxxxxxxxxx > http://lists.centos.org/mailman/listinfo/centos-virt > _______________________________________________ CentOS-virt mailing list CentOS-virt@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos-virt
