RE: What to backup for named?
After a recent disk failure, I left myself a note to add the DNS/DHCP info to my backup. I have a small, over-engineered for my education, network of 10 computers in my house. I run BIND with dynamic zones on my FreeBSD server, I also use the DNS service on my Win2k-AD server. They both are designated as slaves for each other. What do I need to backup? Are just the configuration files from /var/namedb/etc/namedb enough to recreate everything if my FBSD server dies? Or are there some database files I should be keeping also? I tried googling, but either this is way to easy of a question or I'm not looking in the right places. Thanks for any insight, Joe. Yup, that is what we backup. The named.conf and all records created along. Tamouh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What to backup
* Gary Aitken [EMAIL PROTECTED] [0911 20:11]: Scott Gerhardt wrote: On Sep 15, 2004, at 12:19 PM, Curtis Vaughan wrote: I have a question about what exactly I should backup on my 5.3 FreeBSD Server. So far I have chosen the following directories for full backup. But perhaps some is overkill. /etc /boot /home /var/log /usr/ports /root /usr/local /usr/src You probably do want to back up /usr/src/sys/xxx/conf, where xxx is i386 or whatever for your sys, since that is where your kernel config for custom kernels normally resides. What I do is keep my kernel config in my home directory (under CVS control) and symlink to it from /usr/src. I have 'rm -rf /usr/src'ed once too often in anger :) Also I prefer to have /usr/local/etc as a symlik into /etc/local/ , again so I can 'cp -Rp /etc /etc.ok' before I start to reconfigure the system (changing network IPs or similar) and restore everything easily. -- The only real way to look younger is not to be born so soon. -- Charles Schulz, Things I've Had to Learn Over and Over and Over Rasputin :: Jack of All Trades - Master of Nuns ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What to backup
On Sep 15, 2004, at 12:19 PM, Curtis Vaughan wrote: I have a question about what exactly I should backup on my 5.3 FreeBSD Server. So far I have chosen the following directories for full backup. But perhaps some is overkill. /etc /boot /home /var/log /usr/ports /root /usr/local /usr/src Curtis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] You don't really need to backup /usr/ports and /usr/src since they can be easily rebuilt by cvsup'ing the latest. Not backing these up will probably save you about 500MB. Thanks, -- Scott A. Gerhardt, P.Geo. Gerhardt Information Technologies ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What to backup
On Sep 15, 2004, at 2:19 PM, Curtis Vaughan wrote: I have a question about what exactly I should backup on my 5.3 FreeBSD Server. So far I have chosen the following directories for full backup. But perhaps some is overkill. The best answer is backup everything. If you use a decent backup system which support differential or incremental backups, you will generate one large backup image (ie, a level-0 dump), and then future backups will take up a lot less space. If backing everything up requires too much space, backing up /etc, /home, and probably /var/mail is about the minimum one can do, but that depends on whether you have other stuff around that you care about. If you keep the output of pkg_info handy, you won't really need to backup /usr/local or /usr/ports; /usr/src, /boot, and /root can generally be recovered from a clean reinstall. -- -Chuck ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What to backup
On 09/15/04 11:19 AM, Curtis Vaughan sat at the `puter and typed: I have a question about what exactly I should backup on my 5.3 FreeBSD Server. So far I have chosen the following directories for full backup. But perhaps some is overkill. /etc /boot /home /var/log /usr/ports /root /usr/local /usr/src As mentioned by other posters, you can probably omit /usr/local, /usr/ports, and /usr/src, but of course you may want to include any directories you make code changes in, particularly if you have a habit of hacking the kernel. I also make a point of saving any custom kernel configs in /root/kernels, and softlinking them to /usr/src/sys/i386/conf/ so that when /root is backed up, the kernel config is too. I still haven't found a reliable way to save my fvwm2 patch in the ports directory (I changed the screen wraparound behavior) so I just keep that one in my home directory. That's pretty much the only port I've hacked, so it works for now. You might also want to back up /usr/local/etc if you skip /usr/local. Many important ports will use this area for configs, and you won't want to lose the weeks or months you spend tweaking these out either. Good luck Lou -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org ԿԬ QOTD: It's hard to tell whether he has an ace up his sleeve or if the ace is missing from his deck altogether. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What to backup
Scott Gerhardt wrote: On Sep 15, 2004, at 12:19 PM, Curtis Vaughan wrote: I have a question about what exactly I should backup on my 5.3 FreeBSD Server. So far I have chosen the following directories for full backup. But perhaps some is overkill. /etc /boot /home /var/log /usr/ports /root /usr/local /usr/src ... You don't really need to backup /usr/ports and /usr/src since they can be easily rebuilt by cvsup'ing the latest. Not backing these up will probably save you about 500MB. You probably do want to back up /usr/src/sys/xxx/conf, where xxx is i386 or whatever for your sys, since that is where your kernel config for custom kernels normally resides. Gary ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What to backup
On Sep 15, 2004, at 1:08 PM, Louis LeBlanc wrote: On 09/15/04 11:19 AM, Curtis Vaughan sat at the `puter and typed: I have a question about what exactly I should backup on my 5.3 FreeBSD Server. So far I have chosen the following directories for full backup. But perhaps some is overkill. /etc /boot /home /var/log /usr/ports /root /usr/local /usr/src As mentioned by other posters, you can probably omit /usr/local, /usr/ports, and /usr/src, but of course you may want to include any directories you make code changes in, particularly if you have a habit of hacking the kernel. I also make a point of saving any custom kernel configs in /root/kernels, and softlinking them to /usr/src/sys/i386/conf/ so that when /root is backed up, the kernel config is too. I still haven't found a reliable way to save my fvwm2 patch in the ports directory (I changed the screen wraparound behavior) so I just keep that one in my home directory. That's pretty much the only port I've hacked, so it works for now. You might also want to back up /usr/local/etc if you skip /usr/local. Many important ports will use this area for configs, and you won't want to lose the weeks or months you spend tweaking these out either. Good luck Lou -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org ԿԬ You might want to make sure to get /usr/local/etc/ which includes all the local configs and periodic scripts. Thanks, -- Scott A. Gerhardt, P.Geo. Gerhardt Information Technologies ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What to backup
On Wed, 2004-09-15 at 18:23, Scott Gerhardt wrote: On Sep 15, 2004, at 1:08 PM, Louis LeBlanc wrote: On 09/15/04 11:19 AM, Curtis Vaughan sat at the `puter and typed: I have a question about what exactly I should backup on my 5.3 FreeBSD Server. So far I have chosen the following directories for full backup. But perhaps some is overkill. /etc /boot /home /var/log /usr/ports /root /usr/local /usr/src As mentioned by other posters, you can probably omit /usr/local, /usr/ports, and /usr/src, but of course you may want to include any directories you make code changes in, particularly if you have a habit of hacking the kernel. I also make a point of saving any custom kernel configs in /root/kernels, and softlinking them to /usr/src/sys/i386/conf/ so that when /root is backed up, the kernel config is too. I still haven't found a reliable way to save my fvwm2 patch in the ports directory (I changed the screen wraparound behavior) so I just keep that one in my home directory. That's pretty much the only port I've hacked, so it works for now. You might also want to back up /usr/local/etc if you skip /usr/local. Many important ports will use this area for configs, and you won't want to lose the weeks or months you spend tweaking these out either. Good luck Lou -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org ԿԬ You might want to make sure to get /usr/local/etc/ which includes all the local configs and periodic scripts. Thanks, -- Scott A. Gerhardt, P.Geo. Gerhardt Information Technologies ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] For my desktop machine, I make a habit of putting a comment with my initials in every configuration file that I modify. I then have a nightly run that finds all these files and copies them to a sub-directory in my home directory, and the home directory is then copied to another machine. Periodically, I burn a CD of the home directory. I have found this a reliable way to make sure that I can always re-create my machine if things go badly wrong. I don't mind if it takes an hour or two to reinstall and reconfigure, provided I am sure I won't lose anything I have worked on myself. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]