alternative location for Postgres dumps

Due to a recent increase in the number of things being
managed by our  
Bricolage instance, the amount of data being stored in our
nightly  
Postgres dumps has grown unwieldy and is filling up disk
space faster  
than we can assign it. Does anyone have any suggestions?
Perhaps we  
should reconfigure Postgres to dump to an external storage
device?  
What would be involved in something like that? What do
others with   
90MB-per-day Postgres dumps do?

Thanks,
Ashlee

--------------------

This email message is for the sole use of the intended
recipient(s) and
may contain privileged information. Any unauthorized review,
use,
disclosure or distribution is prohibited. If you are not the
intended
recipient, please contact the sender by reply email and
destroy all copies
of the original message.

I back it up to the same file every night and let the tape
backup system
worry about versioning.  I also gzip it which saves space.

-----Original Message-----
From: Ashlee Caul [mailto:acaulrand.org] 
Sent: Wednesday, September 26, 2007 2:34 PM
To: Bricolage Users
Subject: alternative location for Postgres dumps

Due to a recent increase in the number of things being
managed by our  
Bricolage instance, the amount of data being stored in our
nightly  
Postgres dumps has grown unwieldy and is filling up disk
space faster  
than we can assign it. Does anyone have any suggestions?
Perhaps we  
should reconfigure Postgres to dump to an external storage
device?  
What would be involved in something like that? What do
others with   
90MB-per-day Postgres dumps do?

Thanks,
Ashlee

--------------------

This email message is for the sole use of the intended
recipient(s) and
may contain privileged information. Any unauthorized review,
use,
disclosure or distribution is prohibited. If you are not the
intended
recipient, please contact the sender by reply email and
destroy all
copies
of the original message.

On Wed, Sep 26, 2007 at 02:33:33PM -0400, Ashlee Caul
wrote:
> Due to a recent increase in the number of things being
managed by our  
> Bricolage instance, the amount of data being stored in
our nightly  
> Postgres dumps has grown unwieldy and is filling up
disk space faster  
> than we can assign it. Does anyone have any
suggestions? Perhaps we  
> should reconfigure Postgres to dump to an external
storage device?  
> What would be involved in something like that? What do
others with   
> 90MB-per-day Postgres dumps do?

Hey Ashlee -- we deal with ~270MB/day and keep some locally
stored (for quick retrieval if it's possible), and offline
(rsync'd, I believe) as well. The local copies are pruned
occasionally so that only the most recent are kept.

If you're not doing offline (external machine, tape, etc.)
storage already, it'd be worth considering. If the local
disk you're storing the data on fails and is inaccessible,
backups on it are useless, whether there's room for them or
not.

> Thanks,
> Ashlee
> 
> --------------------
> 
> This email message is for the sole use of the intended
recipient(s) and
> may contain privileged information. Any unauthorized
review, use,
> disclosure or distribution is prohibited. If you are
not the intended
> recipient, please contact the sender by reply email and
destroy all copies
> of the original message.
> 
> 

-- 

-bch
http://www.methodlogic.net

On Sep 26, 2007, at 11:33, Ashlee Caul wrote:

> Due to a recent increase in the number of things being
managed by  
> our Bricolage instance, the amount of data being stored
in our  
> nightly Postgres dumps has grown unwieldy and is
filling up disk  
> space faster than we can assign it. Does anyone have
any  
> suggestions? Perhaps we should reconfigure Postgres to
dump to an  
> external storage device? What would be involved in
something like  
> that? What do others with  90MB-per-day Postgres dumps
do?

Are you compressing your dumps? I would just keep the last n
dumps,  
myself.

Best,

David