pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedbackups
19+ messages / 9 participants
[nested] [flat]
* backups
@ 2006-05-10 15:49 mcelroy, tim <tim.mcelroy@bostonstock.com>
0 siblings, 1 reply; 19+ messages in thread
From: mcelroy, tim @ 2006-05-10 15:49 UTC (permalink / raw)
To: pgsql-admin
Greetings,
Does the pg_dump command 'backup' the pg_xlog files?
Thank you,
Tim
^ permalink raw reply [nested|flat] 19+ messages in thread
* Re: backups
@ 2006-05-10 15:56 mcelroy, tim <tim.mcelroy@bostonstock.com>
0 siblings, 2 replies; 19+ messages in thread
From: mcelroy, tim @ 2006-05-10 15:56 UTC (permalink / raw)
To: Scott Marlowe <smarlowe@g2switchworks.com>; +Cc: pgsql-admin
Thanks for the quick answer Scott. I thought so but wanted to double-check.
I was asked by the person who performs our system backups if just backing up
the directory where I put the nightly backups (created with pg_dump) was
enough. I also have them backing up /var/lib/pgsql and everything under
that and they're complaining that it's taking too long. I would think we
would also want to back up the pg_xlog directory though. Or is that
overkill? Is there a standard in the PG community I should follow? Is just
performing the pg_dump and saving that to tape enough? I just don't want to
get bit in the butt if I tell him to not back something up that should be
backed up.
Tim
-----Original Message-----
From: Scott Marlowe [mailto:smarlowe@g2switchworks.com]
Sent: Wednesday, May 10, 2006 11:57 AM
To: mcelroy, tim
Cc: 'pgsql-admin@postgresql.org'
Subject: Re: [ADMIN] backups
On Wed, 2006-05-10 at 10:49, mcelroy, tim wrote:
> Greetings,
>
>
>
> Does the pg_dump command 'backup' the pg_xlog files?
No. Those are internal files used by the database to maintain
transactional integrity. The pg_dump command backs up the database as
snapshotted at a specific point of time.
What are you trying to accomplish?
^ permalink raw reply [nested|flat] 19+ messages in thread
* Re: backups
@ 2006-05-10 15:57 Scott Marlowe <smarlowe@g2switchworks.com>
parent: mcelroy, tim <tim.mcelroy@bostonstock.com>
0 siblings, 0 replies; 19+ messages in thread
From: Scott Marlowe @ 2006-05-10 15:57 UTC (permalink / raw)
To: mcelroy, tim <tim.mcelroy@bostonstock.com>; +Cc: pgsql-admin
On Wed, 2006-05-10 at 10:49, mcelroy, tim wrote:
> Greetings,
>
>
>
> Does the pg_dump command ‘backup’ the pg_xlog files?
No. Those are internal files used by the database to maintain
transactional integrity. The pg_dump command backs up the database as
snapshotted at a specific point of time.
What are you trying to accomplish?
^ permalink raw reply [nested|flat] 19+ messages in thread
* Re: backups
@ 2006-05-10 16:11 Scott Marlowe <smarlowe@g2switchworks.com>
parent: mcelroy, tim <tim.mcelroy@bostonstock.com>
1 sibling, 0 replies; 19+ messages in thread
From: Scott Marlowe @ 2006-05-10 16:11 UTC (permalink / raw)
To: mcelroy, tim <tim.mcelroy@bostonstock.com>; +Cc: pgsql-admin
On Wed, 2006-05-10 at 10:56, mcelroy, tim wrote:
> Thanks for the quick answer Scott. I thought so but wanted to
> double-check. I was asked by the person who performs our system
> backups if just backing up the directory where I put the nightly
> backups (created with pg_dump) was enough. I also have them backing
> up /var/lib/pgsql and everything under that and they're complaining
> that it's taking too long. I would think we would also want to back
> up the pg_xlog directory though. Or is that overkill? Is there a
> standard in the PG community I should follow? Is just performing the
> pg_dump and saving that to tape enough? I just don't want to get bit
> in the butt if I tell him to not back something up that should be
> backed up.
Generally speaking, backing up with pg_dump is plenty.
The /var/lib/pgsql directory backups aren't necessarily useful since the
files may not be backed up in the same "state" i.e. some transaction
might be in two places at once, partially written, etc... pg_dump
doesn't not have this problem.
If you want something more up to the second, look for point in time
replication in the postgresql docs.
^ permalink raw reply [nested|flat] 19+ messages in thread
* Re: backups
@ 2006-05-10 16:54 mcelroy, tim <tim.mcelroy@bostonstock.com>
0 siblings, 0 replies; 19+ messages in thread
From: mcelroy, tim @ 2006-05-10 16:54 UTC (permalink / raw)
To: Scott Marlowe <smarlowe@g2switchworks.com>; +Cc: pgsql-admin
Great, exactly the answer I was looking for. Thank you again Scott.
Tim
-----Original Message-----
From: Scott Marlowe [mailto:smarlowe@g2switchworks.com]
Sent: Wednesday, May 10, 2006 12:12 PM
To: mcelroy, tim
Cc: 'pgsql-admin@postgresql.org'
Subject: RE: [ADMIN] backups
On Wed, 2006-05-10 at 10:56, mcelroy, tim wrote:
> Thanks for the quick answer Scott. I thought so but wanted to
> double-check. I was asked by the person who performs our system
> backups if just backing up the directory where I put the nightly
> backups (created with pg_dump) was enough. I also have them backing
> up /var/lib/pgsql and everything under that and they're complaining
> that it's taking too long. I would think we would also want to back
> up the pg_xlog directory though. Or is that overkill? Is there a
> standard in the PG community I should follow? Is just performing the
> pg_dump and saving that to tape enough? I just don't want to get bit
> in the butt if I tell him to not back something up that should be
> backed up.
Generally speaking, backing up with pg_dump is plenty.
The /var/lib/pgsql directory backups aren't necessarily useful since the
files may not be backed up in the same "state" i.e. some transaction
might be in two places at once, partially written, etc... pg_dump
doesn't not have this problem.
If you want something more up to the second, look for point in time
replication in the postgresql docs.
^ permalink raw reply [nested|flat] 19+ messages in thread
* Re: backups
@ 2006-05-10 19:11 mcelroy, tim <tim.mcelroy@bostonstock.com>
0 siblings, 1 reply; 19+ messages in thread
From: mcelroy, tim @ 2006-05-10 19:11 UTC (permalink / raw)
To: Bruno Wolff III <bruno@wolff.to>; +Cc: pgsql-admin
Excellent point Bruno, thanks. I must admit that I did think of that and
have already copied all my .conf files to the backup directory. I should
have noted that earlier.
Thanks,
Tim
-----Original Message-----
From: Bruno Wolff III [mailto:bruno@wolff.to]
Sent: Wednesday, May 10, 2006 3:12 PM
To: mcelroy, tim
Cc: 'Scott Marlowe'; 'pgsql-admin@postgresql.org'
Subject: Re: backups
On Wed, May 10, 2006 at 11:56:20 -0400,
"mcelroy, tim" <tim.mcelroy@bostonstock.com> wrote:
> Thanks for the quick answer Scott. I thought so but wanted to
double-check.
> I was asked by the person who performs our system backups if just backing
up
> the directory where I put the nightly backups (created with pg_dump) was
> enough. I also have them backing up /var/lib/pgsql and everything under
> that and they're complaining that it's taking too long. I would think we
> would also want to back up the pg_xlog directory though. Or is that
> overkill? Is there a standard in the PG community I should follow? Is
just
> performing the pg_dump and saving that to tape enough? I just don't want
to
> get bit in the butt if I tell him to not back something up that should be
> backed up.
You might want to make sure you have the configuration files backed up as
well.
^ permalink raw reply [nested|flat] 19+ messages in thread
* Re: backups
@ 2006-05-10 19:11 Bruno Wolff III <bruno@wolff.to>
parent: mcelroy, tim <tim.mcelroy@bostonstock.com>
1 sibling, 0 replies; 19+ messages in thread
From: Bruno Wolff III @ 2006-05-10 19:11 UTC (permalink / raw)
To: mcelroy, tim <tim.mcelroy@bostonstock.com>; +Cc: Scott Marlowe <smarlowe@g2switchworks.com>; pgsql-admin
On Wed, May 10, 2006 at 11:56:20 -0400,
"mcelroy, tim" <tim.mcelroy@bostonstock.com> wrote:
> Thanks for the quick answer Scott. I thought so but wanted to double-check.
> I was asked by the person who performs our system backups if just backing up
> the directory where I put the nightly backups (created with pg_dump) was
> enough. I also have them backing up /var/lib/pgsql and everything under
> that and they're complaining that it's taking too long. I would think we
> would also want to back up the pg_xlog directory though. Or is that
> overkill? Is there a standard in the PG community I should follow? Is just
> performing the pg_dump and saving that to tape enough? I just don't want to
> get bit in the butt if I tell him to not back something up that should be
> backed up.
You might want to make sure you have the configuration files backed up as well.
^ permalink raw reply [nested|flat] 19+ messages in thread
* Re: backups
@ 2006-05-10 19:35 Scott Marlowe <smarlowe@g2switchworks.com>
parent: mcelroy, tim <tim.mcelroy@bostonstock.com>
0 siblings, 0 replies; 19+ messages in thread
From: Scott Marlowe @ 2006-05-10 19:35 UTC (permalink / raw)
To: mcelroy, tim <tim.mcelroy@bostonstock.com>; +Cc: Bruno Wolff III <bruno@wolff.to>; pgsql-admin
On Wed, 2006-05-10 at 14:11, mcelroy, tim wrote:
> Excellent point Bruno, thanks. I must admit that I did think of that
> and have already copied all my .conf files to the backup directory. I
> should have noted that earlier.
>
> Thanks,
> Tim
Another thing to check is that your global data (i.e. user accounts) are
being backed up. pg_dumpall does this, but individual pg_dumps do not.
In our prod environment we run a backup of those accounts with
'pg_dumpall -g' every night as well.
^ permalink raw reply [nested|flat] 19+ messages in thread
* Re: backups
@ 2006-05-10 19:43 mcelroy, tim <tim.mcelroy@bostonstock.com>
0 siblings, 1 reply; 19+ messages in thread
From: mcelroy, tim @ 2006-05-10 19:43 UTC (permalink / raw)
To: Scott Marlowe <smarlowe@g2switchworks.com>; +Cc: pgsql-admin
Thanks Scott, great idea. Does one use pg_restore to restore the files that
pg_dumpall creates?
-----Original Message-----
From: Scott Marlowe [mailto:smarlowe@g2switchworks.com]
Sent: Wednesday, May 10, 2006 3:35 PM
To: mcelroy, tim
Cc: 'Bruno Wolff III'; 'pgsql-admin@postgresql.org'
Subject: Re: [ADMIN] backups
On Wed, 2006-05-10 at 14:11, mcelroy, tim wrote:
> Excellent point Bruno, thanks. I must admit that I did think of that
> and have already copied all my .conf files to the backup directory. I
> should have noted that earlier.
>
> Thanks,
> Tim
Another thing to check is that your global data (i.e. user accounts) are
being backed up. pg_dumpall does this, but individual pg_dumps do not.
In our prod environment we run a backup of those accounts with
'pg_dumpall -g' every night as well.
^ permalink raw reply [nested|flat] 19+ messages in thread
* Re: backups
@ 2006-05-10 20:14 Joshua D. Drake <jd@commandprompt.com>
parent: mcelroy, tim <tim.mcelroy@bostonstock.com>
0 siblings, 0 replies; 19+ messages in thread
From: Joshua D. Drake @ 2006-05-10 20:14 UTC (permalink / raw)
To: mcelroy, tim <tim.mcelroy@bostonstock.com>; +Cc: 'Scott Marlowe' <smarlowe@g2switchworks.com>; pgsql-admin
mcelroy, tim wrote:
> Thanks Scott, great idea. Does one use pg_restore to restore the files
> that pg_dumpall creates?
No, oddly you use psql.
Sincerely,
Joshua D. Drake
>
>
> -----Original Message-----
> From: Scott Marlowe [mailto:smarlowe@g2switchworks.com]
> Sent: Wednesday, May 10, 2006 3:35 PM
> To: mcelroy, tim
> Cc: 'Bruno Wolff III'; 'pgsql-admin@postgresql.org'
> Subject: Re: [ADMIN] backups
>
> On Wed, 2006-05-10 at 14:11, mcelroy, tim wrote:
> > Excellent point Bruno, thanks. I must admit that I did think of that
> > and have already copied all my .conf files to the backup directory. I
> > should have noted that earlier.
> >
> > Thanks,
> > Tim
>
> Another thing to check is that your global data (i.e. user accounts) are
> being backed up. pg_dumpall does this, but individual pg_dumps do not.
>
> In our prod environment we run a backup of those accounts with
> 'pg_dumpall -g' every night as well.
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
^ permalink raw reply [nested|flat] 19+ messages in thread
* Backups
@ 2010-02-20 17:11 Nilesh Govindarajan <lists@itech7.com>
0 siblings, 1 reply; 19+ messages in thread
From: Nilesh Govindarajan @ 2010-02-20 17:11 UTC (permalink / raw)
To: pgsql-admin
I want a script to backup all databases table by table in different .sql
files.
How to do this ?
Also since it is a script, there has to be some role having read access
to all tables on all databases. How to grant that ?
--
Nilesh Govindarajan
Site & Server Adminstrator
www.itech7.com
^ permalink raw reply [nested|flat] 19+ messages in thread
* Re: Backups
@ 2010-02-20 17:44 Kevin Grittner <Kevin.Grittner@wicourts.gov>
0 siblings, 1 reply; 19+ messages in thread
From: Kevin Grittner @ 2010-02-20 17:44 UTC (permalink / raw)
To: lists@itech7.com; pgsql-admin
Nilesh Govindarajan wrote:
> I want a script to backup all databases table by table in different
> .sql files.
My first question would be whether they all need to be from the same
point in time? Is it a requirement that if they were all restored
they would provide a database with referential integrity, etc.? Or
is it OK if each table represents a different moment in time?
Either way, you probably want pg_dump. If you don't care about
having these separate files to collectively provide a consistent
image of a moment in time, or you can prevent any modifications while
you are running a set of backups, you could use pg_dump with the -t
option. Otherwise you probably need to use pg_dump (or pg_dumpall)
and parse the output to split it into the required files. Or you
might be able to do pg_dump to the custom format and extract each
table into a separate file.
> Also since it is a script, there has to be some role having read
> access to all tables on all databases. How to grant that ?
If you don't want to use the database superuser and don't already
have some other role with the appropriate rights, you will have to
grant them. It's hard to provide details without more information
about what's already there.
-Kevin
^ permalink raw reply [nested|flat] 19+ messages in thread
* Re: Backups
@ 2010-02-20 17:53 Scott Marlowe <scott.marlowe@gmail.com>
parent: Nilesh Govindarajan <lists@itech7.com>
0 siblings, 1 reply; 19+ messages in thread
From: Scott Marlowe @ 2010-02-20 17:53 UTC (permalink / raw)
To: Nilesh Govindarajan <lists@itech7.com>; +Cc: pgsql-admin
On Sat, Feb 20, 2010 at 10:11 AM, Nilesh Govindarajan <lists@itech7.com> wrote:
> I want a script to backup all databases table by table in different .sql
> files.
Why? It may be that pg_dump / pg_restore already provide the
functionality you are looking for.
> How to do this ?
pg_dump -t tablename dbname
rinse repeat
> Also since it is a script, there has to be some role having read access to
> all tables on all databases. How to grant that ?
Can they just be a superuser? Or can you grant them the role that has
ownership of the tables?
^ permalink raw reply [nested|flat] 19+ messages in thread
* Re: Backups
@ 2010-02-21 01:57 Nilesh Govindarajan <lists@itech7.com>
parent: Scott Marlowe <scott.marlowe@gmail.com>
0 siblings, 1 reply; 19+ messages in thread
From: Nilesh Govindarajan @ 2010-02-21 01:57 UTC (permalink / raw)
To: Scott Marlowe <scott.marlowe@gmail.com>; +Cc: pgsql-admin
On 02/20/2010 11:23 PM, Scott Marlowe wrote:
> On Sat, Feb 20, 2010 at 10:11 AM, Nilesh Govindarajan<lists@itech7.com> wrote:
>> I want a script to backup all databases table by table in different .sql
>> files.
>
> Why? It may be that pg_dump / pg_restore already provide the
> functionality you are looking for.
>
>> How to do this ?
>
> pg_dump -t tablename dbname
>
> rinse repeat
>
>> Also since it is a script, there has to be some role having read access to
>> all tables on all databases. How to grant that ?
>
> Can they just be a superuser? Or can you grant them the role that has
> ownership of the tables?
I don't feel safe to key in the root password in the script.
I was previously using MySQL, in which I had a user called backup
without password having SELECT access on all tables and databases.
I need something similar in PgSQL. A possible solution seems to me is to
use the trust auth for a user in pg_hba.conf, but if the user is given
superuser status, then it will have write access to all databases, which
is extremely dangerous.
--
Nilesh Govindarajan
Site & Server Adminstrator
www.itech7.com
^ permalink raw reply [nested|flat] 19+ messages in thread
* Re: Backups
@ 2010-02-21 01:59 Nilesh Govindarajan <lists@itech7.com>
parent: Kevin Grittner <Kevin.Grittner@wicourts.gov>
0 siblings, 0 replies; 19+ messages in thread
From: Nilesh Govindarajan @ 2010-02-21 01:59 UTC (permalink / raw)
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>; +Cc: pgsql-admin
On 02/20/2010 11:14 PM, Kevin Grittner wrote:
> Nilesh Govindarajan wrote:
>
>> I want a script to backup all databases table by table in different
>> .sql files.
>
> My first question would be whether they all need to be from the same
> point in time? Is it a requirement that if they were all restored
> they would provide a database with referential integrity, etc.? Or
> is it OK if each table represents a different moment in time?
>
> Either way, you probably want pg_dump. If you don't care about
> having these separate files to collectively provide a consistent
> image of a moment in time, or you can prevent any modifications while
> you are running a set of backups, you could use pg_dump with the -t
> option. Otherwise you probably need to use pg_dump (or pg_dumpall)
> and parse the output to split it into the required files. Or you
> might be able to do pg_dump to the custom format and extract each
> table into a separate file.
>
>> Also since it is a script, there has to be some role having read
>> access to all tables on all databases. How to grant that ?
>
> If you don't want to use the database superuser and don't already
> have some other role with the appropriate rights, you will have to
> grant them. It's hard to provide details without more information
> about what's already there.
>
> -Kevin
That is what exactly. I can prevent the changes to the database when the
backup is going on, but how do I grant the permissions ? I don't want to
key in the password for the superuser in the script.
--
Nilesh Govindarajan
Site & Server Adminstrator
www.itech7.com
^ permalink raw reply [nested|flat] 19+ messages in thread
* Re: Backups
@ 2010-02-21 02:06 Kevin Grittner <Kevin.Grittner@wicourts.gov>
0 siblings, 0 replies; 19+ messages in thread
From: Kevin Grittner @ 2010-02-21 02:06 UTC (permalink / raw)
To: lists@itech7.com; +Cc: pgsql-admin
Nilesh Govindarajan wrote:
> I can prevent the changes to the database when the
> backup is going on, but how do I grant the permissions ? I don't
> want to key in the password for the superuser in the script.
There are so many ways to deal with that that it's hard to make a
suggestion without knowing more. You could just use CREATE USER and
GRANT to set things up, you could use trust authentication in the
pg_hba.conf to grant a database superuser permission from a secure
machine, or you could use a pgpass file. (Check the documentation
for details.) If I got creative I could probably come up with more,
but I'm shooting in the dark here.
-Kevin
^ permalink raw reply [nested|flat] 19+ messages in thread
* Re: Backups
@ 2010-02-21 02:33 Scott Marlowe <scott.marlowe@gmail.com>
parent: Nilesh Govindarajan <lists@itech7.com>
0 siblings, 0 replies; 19+ messages in thread
From: Scott Marlowe @ 2010-02-21 02:33 UTC (permalink / raw)
To: Nilesh Govindarajan <lists@itech7.com>; +Cc: pgsql-admin
On Sat, Feb 20, 2010 at 6:57 PM, Nilesh Govindarajan <lists@itech7.com> wrote:
> On 02/20/2010 11:23 PM, Scott Marlowe wrote:
>>
>> On Sat, Feb 20, 2010 at 10:11 AM, Nilesh Govindarajan<lists@itech7.com>
>> wrote:
>>>
>>> I want a script to backup all databases table by table in different .sql
>>> files.
>>
>> Why? It may be that pg_dump / pg_restore already provide the
>> functionality you are looking for.
>>
>>> How to do this ?
>>
>> pg_dump -t tablename dbname
>>
>> rinse repeat
>>
>>> Also since it is a script, there has to be some role having read access
>>> to
>>> all tables on all databases. How to grant that ?
>>
>> Can they just be a superuser? Or can you grant them the role that has
>> ownership of the tables?
>
> I don't feel safe to key in the root password in the script.
Why would you need to have a password in your script? Just use
.pgpass file for whichever unix account is going to connect, and then
grant that user the SQL privileges to dump the db. I think you need
to do more reading of the docs on user accounts etc under pgsql.
> I was previously using MySQL, in which I had a user called backup without
> password having SELECT access on all tables and databases.
There are lots of ways to attack this, some of which do not require a
password to be stored anywhere. At no time should a unix root account
be involved.
> I need something similar in PgSQL. A possible solution seems to me is to use
> the trust auth for a user in pg_hba.conf, but if the user is given superuser
> status, then it will have write access to all databases, which is extremely
> dangerous.
trust auth works but has the issues you mention. the .pgpass file is
the easiest way to pass a password without including it in a script or
anything.
http://www.postgresql.org/docs/8.3/interactive/libpq-pgpass.html
Note that the user account in unix doesn't have to map directly to the
same name in postgresql.
^ permalink raw reply [nested|flat] 19+ messages in thread
* Backups
@ 2018-01-19 02:16 Azimuddin Mohammed <azimeiu@gmail.com>
0 siblings, 1 reply; 19+ messages in thread
From: Azimuddin Mohammed @ 2018-01-19 02:16 UTC (permalink / raw)
To: pgsql-admin
Hello admins,
What is thr best backup strategy?
I am planning to setup my pg cluster with streaming replication.
My criteria
1. I should not be restarting my master server and slave.
2. Shiuld take a huge performace cpu or memory (Ram) consumption.
3. Compression is ok.
^ permalink raw reply [nested|flat] 19+ messages in thread
* Re: Backups
@ 2018-01-19 02:19 Aldo Sarmiento <aldo@bigpurpledot.com>
parent: Azimuddin Mohammed <azimeiu@gmail.com>
0 siblings, 0 replies; 19+ messages in thread
From: Aldo Sarmiento @ 2018-01-19 02:19 UTC (permalink / raw)
To: Azimuddin Mohammed <azimeiu@gmail.com>; +Cc: pgsql-admin
I have had lots of success using streaming replication for potential
failover as well as read only hot stand by to assist with my master db.
Additionally we use pg backrest for PITR in the event that we need to roll
back for some unforeseen reason (hacking, corruption, etc).
*Aldo Sarmiento*
President & CTO
8687 Research Dr, Irvine, CA 92618
*O*: (949) 223-0900 - *F: *(949) 727-4265
aldo@bigpurpledot.com | www.bigpurpledot.com
On Thu, Jan 18, 2018 at 6:16 PM, Azimuddin Mohammed <azimeiu@gmail.com>
wrote:
> Hello admins,
> What is thr best backup strategy?
> I am planning to setup my pg cluster with streaming replication.
> My criteria
> 1. I should not be restarting my master server and slave.
> 2. Shiuld take a huge performace cpu or memory (Ram) consumption.
> 3. Compression is ok.
>
^ permalink raw reply [nested|flat] 19+ messages in thread
end of thread, other threads:[~2018-01-19 02:19 UTC | newest]
Thread overview: 19+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2006-05-10 15:49 backups mcelroy, tim <tim.mcelroy@bostonstock.com>
2006-05-10 15:57 ` Scott Marlowe <smarlowe@g2switchworks.com>
2006-05-10 15:56 Re: backups mcelroy, tim <tim.mcelroy@bostonstock.com>
2006-05-10 16:11 ` Scott Marlowe <smarlowe@g2switchworks.com>
2006-05-10 19:11 ` Bruno Wolff III <bruno@wolff.to>
2006-05-10 16:54 Re: backups mcelroy, tim <tim.mcelroy@bostonstock.com>
2006-05-10 19:11 Re: backups mcelroy, tim <tim.mcelroy@bostonstock.com>
2006-05-10 19:35 ` Scott Marlowe <smarlowe@g2switchworks.com>
2006-05-10 19:43 Re: backups mcelroy, tim <tim.mcelroy@bostonstock.com>
2006-05-10 20:14 ` Joshua D. Drake <jd@commandprompt.com>
2010-02-20 17:11 Backups Nilesh Govindarajan <lists@itech7.com>
2010-02-20 17:53 ` Re: Backups Scott Marlowe <scott.marlowe@gmail.com>
2010-02-21 01:57 ` Re: Backups Nilesh Govindarajan <lists@itech7.com>
2010-02-21 02:33 ` Re: Backups Scott Marlowe <scott.marlowe@gmail.com>
2010-02-20 17:44 Re: Backups Kevin Grittner <Kevin.Grittner@wicourts.gov>
2010-02-21 01:59 ` Re: Backups Nilesh Govindarajan <lists@itech7.com>
2010-02-21 02:06 Re: Backups Kevin Grittner <Kevin.Grittner@wicourts.gov>
2018-01-19 02:16 Backups Azimuddin Mohammed <azimeiu@gmail.com>
2018-01-19 02:19 ` Re: Backups Aldo Sarmiento <aldo@bigpurpledot.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox