On Fri, 1 Dec 2000, John R. Jackson wrote:
> >Switching all of the tablespaces into and out of hot backup mode once at
> >the start and end of the backup is definitely simpler. ...
>
> And then what? How does the data get to Amanda?
I'm not totally familiar with Amanda so off the top of my head (and
assuming we're using gnu tar) we could rename the gnu tar binary and write
a script which wraps it, performing the start and end hot backup commands
when the real user ID is amanda. A bit of a kludge. I'm sure Amanda must
able to be configured to run an arbitrary backup script but I haven't
looked for this feature.
> I talked with my Oracle person a bit more and it was clear from him and
> some documentation he looked up that each tablespace should be done one
> at a time, not all of them at once.
Yeah, you should try to have the database in hot backup mode for the
minimum time possible. The problem with this is that complicates the
scripting significantly. None of the site that I've worked at which have
a centralised backup system like Amanda do the tablespaces or
datafiles individually. It seems to be more sites which use local tape
drives.
> >The backup user has
> >to be running essentially as root for a backup anyway so it should be
> >possible to do a 'su oracle -c command' at the start and end of the
> >backup.
>
> Absolutely not. Very few people run Amanda as root.
The binaries are SUID root. It couldn't do the backup otherwise.
