Re: Are your 7.1 backups/restores ok?
Posted in 1995
Topics: Backup & Restore, Storage & Space Management, Logging & Checkpoints
Billy Wheeler (bw000001@pixie.co.za) wrote: : Petros, : Your points are all noted and pretty much accepted. Unfortunately, I : don't have a lot of OnArchive experience, as I consult to people and : my own internal systems certainly do not warrant OnArchive for : backups! : However, given that you are running a 100GB database, you *are* in the : OnArchive league. : The problem with OnTape is the "all-or-nothing" approach. However, : OnArchive actually merits a more complex backup system than you seem : to have. You should, ideally, have one backup device per DBSPACE : (extravagant, I know!). You should then backup each DBSPACE in : parallel and you would then be able to restore in parallel. As you realize yourself this is not possible, it is ideal but far away from the truth...Even if I was to dedicate a tape drive per dbspace I would have to make onarchive work first..... : I am extremely wary of unattended backups at the best of times. Are : you certain that the cron jobs to fire up the OnAutoVOps is actually : running? Are you aware that each OnAutoVOp only handles one job in the : queue? (Sorry if I'm belabouring the obvious!) Yes, onautovop does run and yes it is supposed to handle one job in the queue. Running onatuovop manually makes the utility pause for a few secs (My guess is that it is talking to the cataloger) and then it quits with no output (nor stderr either). A visit to onarchive afterwards still lists the requests as ready, therefore onautovop either didn't like the request(s) or it didn't even get to them. Starting the cataloger again does not fix the problem by the way... : I would rather attempt to get attended backups going via OnArchive and : then look at the unattended option once that was stable. I'd like to : reiterate that you should seriously consider getting some additional : backup devices. Billy, attended backups run fine from the onarchive point of view, unfortunately from the user's point of view this is a disaster since some blobspaces do not have logical logs (the reason for this is an entirely different issue) and onarchive freezes their pages as it backs them up... I would not consider buying more drives for a utility that refuses to backup anything! The main focus here is getting onautovop to execute a request even for a single dbspace, if that works then everything else can be considered as well.... : Hope this helps. : -- : Cheers, : Billy Thank you for the reply, Regards, Petros -- Petros Michalis // email: Derivative Products Group \\\\ // michalis@dpg.rnb.com Republic National Bank of New York \\X/ michalis@panix.com