OK - assuming they are on a late enough version of UniData, the best way is to use the dbpause to pause the updates, then backup - yes using mirrors would make that an easier process - then dbresume. If they are not on a late enough version, then get them to upgrade... (Late enough in my view would be 6.0 onwards).
If they use mirroring then the process becomes even more straightforward: dbpause break mirror dbresume Backup the mirror set If you use triple mirroring then you maintain data resiliency AND the ability to do backups. And in terms of scheduling this - you use the Friday 3-5AM gap of time - not that the scripted dbpause, break mirror and dbresume should take more than a few seconds of course! HTH This e-mail is for the use of the intended recipient(s) only. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not use, disclose or distribute this e-mail without the author's prior permission. We have taken precautions to minimize the risk of transmitting software viruses, but we advise you to carry out your own virus checks on any attachment to this message. We cannot accept liability for any loss or damage caused by software viruses. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
