Re: What should be backed up?

Jeffrey Goldberg wrote: This is one of the several reasons that I use rsync (via rsnapshot). At each increment, it backs up the minimum that is need. With the cost of having a complete backup which duplicates what you would find in a reinstall, you have a complete system. For binaries,

Re: What should be backed up?

If you have any databases or ldap service, then you want to add those as well, but it is recommended to dump these rather than backup the files themselves. I'm learning a lot from this thread. Thanks for all the suggestions. The paragraph above raises one more question... how to use the

Re: What should be backed up?

John Almberg wrote: If you have any databases or ldap service, then you want to add those as well, but it is recommended to dump these rather than backup the files themselves. I'm learning a lot from this thread. Thanks for all the suggestions. The paragraph above raises one more

Re: What should be backed up?

On Sat, 22 Aug 2009 15:58:25 +0200, Erik Norgaard norga...@locolomo.org said: E Yes, it's easy to miss something that should have been backed up. There E is no point in backup of files other than those you modify yourself, E unless you plan to create an exact image and recover using dd.

Re: What should be backed up?

On Aug 23, 2009, at 7:14 PM, Karl Vogel wrote: Touching a timestamp file and backing up stuff newer than that works fine for things you modify, but I frequently copy over source tarballs and the timestamp method won't work for those. This is one of the several reasons that I use

Re: What should be backed up?

Jeffrey Goldberg wrote: On Aug 21, 2009, at 2:33 PM, John Almberg wrote: I am currently using rsnapshot to back up these directories on a FreeBSD 7.2 webserver: /etc /usr/home /usr/local /var/cron Here is my exclude list from my rsnapshot.conf exclude /var/log exclude

What should be backed up?

I am currently using rsnapshot to back up these directories on a FreeBSD 7.2 webserver: /etc /usr/home /usr/local /var/cron These directories contain all the data and config files that I use... I think... Question: am I missing anything crucial? Thanks: John

Re: What should be backed up?

On Fri, Aug 21, 2009 at 2:33 PM, John Almberg jalmb...@identry.com wrote: I am currently using rsnapshot to back up these directories on a FreeBSD 7.2 webserver: /etc /usr/home /usr/local /var/cron These directories contain all the data and config files that I use... I think...

Re: What should be backed up?

John Almberg schrieb: I am currently using rsnapshot to back up these directories on a FreeBSD 7.2 webserver: /etc /usr/home /usr/local /var/cron These directories contain all the data and config files that I use... I think... Question: am I missing anything crucial? Thanks: John

Re: What should be backed up?

On Aug 21, 2009, at 2:33 PM, John Almberg wrote: I am currently using rsnapshot to back up these directories on a FreeBSD 7.2 webserver: /etc /usr/home /usr/local /var/cron These directories contain all the data and config files that I use... I think... Question: am I missing anything

Re: What should be backed up?

QUOTE My general advice is to back up everything and then explicitly excluding those things that you know that you don't need. Here is my exclude list from my rsnapshot.conf exclude /var/log exclude /var/tmp exclude /usr/obj exclude /usr/ports/distfiles

Re: What should be backed up?

--On Friday, August 21, 2009 16:14:22 -0500 John Almberg jalmb...@identry.com wrote: That raises another question... How feasible is it to restore a server from these backups? Is it really possible to install 7.2 on a new machine and then just copy the backed up data onto the new machine? I