From: | "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk> |
---|---|
To: | btober(at)seaworthysys(dot)com |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Alternative cluster location |
Date: | 2003-11-22 15:12:07 |
Message-ID: | Pine.LNX.4.21.0311221506170.13011-100000@ponder.fairway2k.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
btober(at)seaworthysys(dot)com writes:
> I think the original driving thought technically has something to do with
> system backup, and restore or system re-install in the case of
> catastrophic failure, as well as what I've alluded to in regards to
> original server setup planning and how intended usage impacts decisions
> with respect to hard drive partitioning (and vice versa?).
I believe some of the partitioning idea for /var was the idea that it was a
filesystem that would often be written to, unlike /, and that it was partly a
filesystem corruption safety net to have it as a separate filesystem. This of
course is what gives us the impression that it's suitable for ommission from
backups, i.e. stuff we don't worry too much about losing in the case of a
filesystem failure.
> I don't think there is much under /var that I usually consider necessary to
> back up.
It's always bugged me about /var/named/
--
Nigel Andrews
From | Date | Subject | |
---|---|---|---|
Next Message | Nigel J. Andrews | 2003-11-22 15:42:52 | Re: uploading files |
Previous Message | Carmen Wai | 2003-11-22 14:23:50 | Invalid page header in block xxxx |