there are many gzip-libraries, so gzip could be directly linked into SAPDB if required, but a simple "pipe" would do for me personally.
I have a backup wrapper script that does a backup and then compresses the data afterwards, this has the nice advantage of getting the backup done in a hurry (so the users don't start to complain).
that leads to the question, how much a backup blocks the database, or does it at all?
I'd say that the best possible solution is to simply support piping data to a process, that way the administrator can descide how to actually store the data, like driving a bank of dvd burners directly, manipulating a taperobot or simply compressing the data and storing it in /backups with a sane name.
that would be coolest of course:
append date/time to your backup-filename etc. - and - of course - gzip the data *g*
_______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
