Databases are a bit of an odd animal when it comes to backups. If a
single entry in a table changes, to the outside world, it appears that
the entire database (as a file) needs to be backed up. That's why most
real databases come with their own backup mechanisms (often transaction
logs).
ob suggestion.
> Amanda won’t “prune” databases … but she’ll back up the file that’s on the
> disk.
>
> Others: correct me if I’m wrong, of course.
> Debra Baddorf
> Fermilab
>
>
>
>> On Jan 5, 2018, at 2:22 PM, Chris Miller wrote:
>>
>> Hi Folks,
>>
On Jan 5, 2018, at 2:22 PM, Chris Miller wrote:
> I can't find any explicit guidance for databases, so I assume that
> I do any database preparation in the cron job before I invoke amdump,
> and then tell Amanda to prune the database. Am I right? OR, is there
> an agent for the
Amanda just runs OS provided backup programs, such as DUMP and TAR.
Any other work your database needs must be done in advance, as you suggest with
your cron job suggestion.
Amanda won’t “prune” databases … but she’ll back up the file that’s on the disk.
Others: correct me if I’m wrong, of
Hi Folks,
I can't find any explicit guidance for databases, so I assume that I do any
database preparation in the cron job before I invoke amdump, and then tell
Amanda to prune the database. Am I right? OR, is there an agent for the common
databases, like MySQL, and PostgresSQL?
--
