Title: RE: [ADMIN] Automation/scheduling of Backup stratetgy
You mean WAL. When your server goes down, you can restore from the last backup, and then reapply the WAL to recreate all transactions that were in committed between the backup and the crash. WAL is due for 7.1, I believe.
Cheers
] [mailto:[EMAIL PROTECTED]]On Behalf
Of Trewern, Ben
Sent: Thursday, October 19, 2000 9:32 AM
To: [EMAIL PROTECTED]
Subject: RE: [ADMIN] Automation/scheduling of Backup stratetgy
It is already built in. Use pg_dump or pg_dumpall when online. Only problem
is OIDs and large objects. pg_dump
Title: RE: [ADMIN] Automation/scheduling of Backup stratetgy
It is already built in. Use pg_dump or pg_dumpall when online. Only problem is OIDs and large objects. pg_dump -o to keep OIDs not sure about large objects.
Hope this is what you mean by live/hot backup.
Ben
> -Origi
: Thursday, October 19, 2000 6:04 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [ADMIN] Automation/scheduling of Backup stratetgy
>Is it posible to schedule / automate a backup task and functions to execute
>at a pre-defined time at a pre-defined recurrence rate?
yes, using the cron daem
>Is it posible to schedule / automate a backup task and functions to execute
>at a pre-defined time at a pre-defined recurrence rate?
yes, using the cron daemon and the commands pg_dump or pg_dumpall.
The following entry in the postgres user crontab will backup the
database every day at 03:01 A
Is it posible to schedule / automate a backup task and functions to execute
at a pre-defined time at a pre-defined recurrence rate?
Cornè Scheepers
SQL DBA/Developer
Mindport BIS
021 9150327
