* Matthias Kilian <[EMAIL PROTECTED]> [2005-08-17 22:42]:
> Depending on hardware and infrastructure, you can dump(8) to tape,
> to a separate disk (that's not very safe, though), to a remote
> machine via ssh, or to an ftp server.
for larger scale, I am still (after years) happy with what we do:
* Will H. Backman <[EMAIL PROTECTED]> [2005-08-17 21:50]:
> > > list of steps that anyone can follow, based on tools in the base
> system.
> > like, reading the dump and restore manpages?
> Do you use dump and restore
of course
> What about partition table backup?
there is a copy of the disklabe
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of
> Matthias Kilian
> Sent: Wednesday, August 17, 2005 4:18 PM
> To: misc@openbsd.org
> Subject: Re: The Care and Feeding of OpenBSD
>
> On Wed, Aug 17, 2005 at 03:25:56PM -040
Will H. Backman said the following on 2005-08-17 21:25:
Do you use dump and restore, or are you just giving and example?
What about partition table backup?
I do it using this script below. its proved to be sufficient for a
restore, except for re-creating the mysql.sock on recovery. I recall
On Wed, Aug 17, 2005 at 03:25:56PM -0400, Will H. Backman wrote:
> > like, reading the dump and restore manpages?
> >
>
> Do you use dump and restore, or are you just giving and example?
Can't speak for Henning, but I use dump(8) and restore(8) at home,
on a server I rented from Strato, and for
On 8/17/05, Will H. Backman <[EMAIL PROTECTED]> wrote:
> > > list of steps that anyone can follow, based on tools in the base
> system.
> >
> > like, reading the dump and restore manpages?
> >
> Do you use dump and restore, or are you just giving and example?
>
> What about partition table backup?
On 8/17/05, Will H. Backman <[EMAIL PROTECTED]> wrote:
> OK. Looking at the release(8) man page...yikes! Is this really the
> best way to start backing up an OpenBSD system?
>
it is not _that_ hard. do it once, and you'll know how.
--knitti
> > list of steps that anyone can follow, based on tools in the base
system.
>
> like, reading the dump and restore manpages?
>
Do you use dump and restore, or are you just giving and example?
What about partition table backup?
* Will H. Backman <[EMAIL PROTECTED]> [2005-08-17 20:18]:
> > Best Who quantifies what makes the "best" backup system. I gave
> you
> > one
> > option which will rapidly get your system running after something like
> a
> > HD
> > failure or a fat-fingered 'rm -rf /*' instead of 'rm -rf ./*'.
>
> Best Who quantifies what makes the "best" backup system. I gave
you
> one
> option which will rapidly get your system running after something like
a
> HD
> failure or a fat-fingered 'rm -rf /*' instead of 'rm -rf ./*'.
Sorry. I shouldn't have used the word "Best". What I am looking to do
On Wednesday 17 August 2005 12:59 pm, Will H. Backman wrote:
> > > 2. Disaster Recovery: Dump and Restore, or make a tar file for use
>
> as
>
> > > an install set?
> >
> > make a release for every upgrade (-stable) you do, add your packages
> > to sitexx.tgz. backup your data and config files reg
> > 2. Disaster Recovery: Dump and Restore, or make a tar file for use
as
> > an install set?
>
> make a release for every upgrade (-stable) you do, add your packages
> to sitexx.tgz. backup your data and config files regularly.
>
>
OK. Looking at the release(8) man page...yikes! Is this real
> -Original Message-
> From: Timothy Donahue [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 17, 2005 10:08 AM
> To: Will H. Backman
> Cc: misc@openbsd.org
> Subject: Re: The Care and Feeding of OpenBSD
>
> On Wednesday 17 August 2005 09:48 am, Will H. Backman
On Wednesday 17 August 2005 09:48 am, Will H. Backman wrote:
> > I have the following line in my crontab '(/usr/src/ && cvs -q update
>
> -PAd
>
> > -rOPENBSD_3_7)' If there are any updates, cron will email them to you
> > (cron
> > automattically emails any output to the user that owns the cron j
> I have the following line in my crontab '(/usr/src/ && cvs -q update
-PAd
> -rOPENBSD_3_7)' If there are any updates, cron will email them to you
> (cron
> automattically emails any output to the user that owns the cron job,
so
> setup
> your aliases and optionally your .forward file)
>
I'm cu
"Will H. Backman" <[EMAIL PROTECTED]> writes:
> > > 4. Version Upgrades: This will usually happen once a year given the
> life
> > > cycle of OpenBSD. As far as I can tell, the best practice is to
> read
> > > the upgrade FAQ that comes out with each release, and in general
> fresh
> > > install
-Original Message-
>From: Hannah Schroeter [mailto:[EMAIL PROTECTED]
>On Tue, Aug 16, 2005 at 11:36:42AM -0400, Timothy Donahue wrote:
>>[...]
>
>>As a general rule, if the update is in a library or in the /usr/src/sys
>>folder
>>then I build and install a new kernel then do a `make buil
Hello!
On Tue, Aug 16, 2005 at 11:36:42AM -0400, Timothy Donahue wrote:
>[...]
>As a general rule, if the update is in a library or in the /usr/src/sys folder
>then I build and install a new kernel then do a `make build`. If the change
>is in an application, then I skip the kernel.
IIRC the k
On 8/16/05, Will H. Backman <[EMAIL PROTECTED]> wrote:
> I'm looking for comments on the care and feeding of OpenBSD servers.
> Essentially and "best practices" document for maintaining OpenBSD
> production servers. Yes, "best" is a stupid way to describe anything,
> but I'm hoping that there is s
sorry, replying to my own posting.
you will find some interesting thoughts on server maintenance on
www.infrastructures.org.
On 8/17/05, knitti <[EMAIL PROTECTED]> wrote:
> On 8/16/05, Will H. Backman <[EMAIL PROTECTED]> wrote:
> > 2. Disaster Recovery: Dump and Restore, or make a tar file for
On 8/16/05, Will H. Backman <[EMAIL PROTECTED]> wrote:
> 1. Change Management: Many changes are logged by the daily insecurity
> report, but not all.
in /etc/changelist you can add any file which needs to be tracked. but you
will not change very much on a production server.
> 2. Disaster Recover
> > 4. Version Upgrades: This will usually happen once a year given the
life
> > cycle of OpenBSD. As far as I can tell, the best practice is to
read
> > the upgrade FAQ that comes out with each release, and in general
fresh
> > install with hand merging of old config files is preferred.
>
> FAQ
Forgot to cc
On 16/08/05, Edd Barrett <[EMAIL PROTECTED]> wrote:
> > Upgrading packages now easier with
> > new pkg options, but how do you know when packages are updated?
>
> ftp://ftp.rt.fm/pub/OpenBSD/3.7/packages/i386/index.txt
>
> This file contains all the package listing. Perhaps write a
On Tuesday 16 August 2005 10:39 am, Will H. Backman wrote:
> I'm looking for comments on the care and feeding of OpenBSD servers.
> Essentially and "best practices" document for maintaining OpenBSD
> production servers. Yes, "best" is a stupid way to describe anything,
> but I'm hoping that there
24 matches
Mail list logo
