Good day,
I'm nearly done with initial pass on porting the MySQL::Backup
module to DBA::Backup and DBA::Backup::mysql. Then of course comes
debugging and discovering all the things I broke. ;-} One of the pieces
I just finished in the main run method, which really initiates all the
work. It needs to sensibly order all the possible actions, even if some
database extensions never call for them (via the conf).
For example, I have an option for locking the database(s) up front
as soon as it's a particular servers turn to be backed up. In the MySQL
extension I wont use that action, instead choosing to lock the
database(s) one at a time when I dump them. [let's leave discussing the
pro's and con's of that to a separate thread] I've added possible
actions for things like stopping and starting servers, etc.
If anyone here backs up other server types (particularly
PostgreSQL), I'd appreciate it if you could list the common steps you
take. I don't think I need to many details at this point, just the order
things are generally done in, including the preferred order of log
backups in relation to databases (since Backup.pm generally backs up
logs daily but DB's only when specified, once a week by default).
Thanks!,
--
Sean Quinlan <sean-30eWsgqlZS5AfugRpC6u6w@xxxxxxxxxxxxxxxx>
signature.asc
Description: This is a digitally signed message part
_______________________________________________
Boston-pm mailing list
Boston-pm-PqP1ghmmPMdAfugRpC6u6w@xxxxxxxxxxxxxxxx
http://mail.pm.org/mailman/listinfo/boston-pm
|
