Re: Archive Options - 5.0 OnLine

Chris Youll wrote: > We are moving from SE to OnLine and one of the changes is the archive > method. One option presented was to mirror all the raw dbspaces to cooked > dbspaces, and use the existing backup procedures to just backup the > mirrored dbspaces. > > About the only down side that I can think of is performance, and I have > been able to prove this. I am looking for any other reasons not to mirror > dbspaces to cooked dbspace and only backup the cooked dbspace. When we switched from SE to ONLINE-5.0 we decided it was good enough to mirror only the root dbspace, and use transaction loggin, with the logs being dumped to a UNIX file (that then was compressed and backed up later). We needed some of the stability of transactions, but didn't need the entire DB to be mirrored. We ran all of the dbspaced as raw. Cron ran tbtape to dump the transactions to tape & compress them, keeping a log & renaming the file based on date/time. -- wilcoxon@pioneerplanet.infi.net ********************************************************************** ... this is only a test ... if this had been a real signature it would have been interesting **********************************************************************