Dustin J. Mitchell wrote:
On Fri, Mar 26, 2010 at 1:02 PM, Michael Mueskens <[email protected]> wrote:
Well ok, we don't have to talk about backing up running databases, the best way
in my opinion to do a db-backup is to dump the databases (e.g. mysqldump) and
then backup these dumps via amanda.
Or, if you're using postgres, use ampgsql.
http://code.v.igoro.us/archives/50-Whats-New-in-Amanda-Postgres-Backups.html
Now that is amazingly cool!
Does that mean that the planner understands this and will arrange for
fulls and incrementals in the same fashion as for ordinary partition
backups with ufsdump or gnutar?
Now, what about MySQL? I know that starts to conflict with ZRM for
MySQL, but it's sort of different, in that it changes the management of
the database backups. ZRM can be managed by the DBA and then the
sysadmin handling network backups can capture that with Amanda and get
it on tape. If it were ammysql as a plug-in for the Application API,
then it is totally managed by the sysadmin handling backups, and the DBA
has to go through the sysadmin. So, in the corporate environment, ZRM
would still be preferred. In the Academic Department environment, an
ammysql plug-in would be preferred.
--
---------------
Chris Hoogendyk
-
O__ ---- Systems Administrator
c/ /'_ --- Biology & Geology Departments
(*) \(*) -- 140 Morrill Science Center
~~~~~~~~~~ - University of Massachusetts, Amherst
<[email protected]>
---------------
Erdös 4
