Re: How to continue log backups automatically?
Posted in 1997
Topics: Storage & Space Management, Logging & Checkpoints
Ofer Inbar wrote: > > Richard Stanford <richards@herald.net.REMOVE> writes: > >On 24 Jun 1997, Ofer Inbar wrote: > >> Hold on - you mean to say that if a continuous log backup is left > >> running, it will just keep overwriting from the beginning of the tape > >> each time it has a log to back up? If that's true, what was the point > >> of including this feature in the first place? That doesn't make any > >> sense! > > > >Not in the slightest. It does this whenever it is /restarted/, which was > >what spawned this thread in the first place. > > That doesn't seem to make any more sense. Why should restarting cause > it to overwrite already backed up files? What's the catalog for? Why > are there vsets and multiple volumes defined? Isn't it supposed to > keep track of what it backs up, and ask for new tapes when it needs > more space? > > I don't have a lot of experience with ON-Archive, but I *did* read the > entire manual cover to cover, and nothing in the manual that I > remember gave me the impression that anything would be deleted from > tape unless I specifically asked for it to be deleted. > Once your dbspacesets, volume sets and volumes are defined, you create backup requests which you then execute. If you create a request with syntax similar to: BACKUP/LOGFILE/CONTINUOUS/VSET=logs then potentially your tape volume will fill. (You need to have onautovop running to monitor what is happening and backup the logfiles as they fill) You monitor the free space on your tape volume by issuing the LIST/VOLUME=*/VSET=logs request. If it is almost full (i.e. no space for another logical log file) you run stop_autovop. You then protect the current tape volume using the MODIFY/VOLUME=nnn/VSET=logs/PROTECTION=R and then define a new one (on a new tape if you're sensible). Next, you issue the BACKUP/LOGFILE... request again and restart onautovop. Hope this makes sense - its what we're using at the moment and it works rather well. OnArchive is rather fragile, though. A bit like a china teacup (if you'll pardon the tenuous comparison). Treat it well, and it will perform its job. Mess around with it and it gets rather confused (or cracked and leaks tea!). Danny