Re: IDS 9.21 Backup/Recover strat with HDR

Great explanation Martin. Danke sehr. I would like to add something about HDR, usually HDR complains when having different values for TAPEDEV and LTAPEDEV on both servers. One way to accomplish that is to keep the values same on both primary and secondary and then links should be creaed on the secondary to send those values to /dev/null if needed. Hope this helps. Ravi. "Martin Fuer...." <MARTINFU@de.ibm.com> wrote: Hi, since you now use ON-Bar, with which storage manager do you use it ? - ON-Bar: - can do backup and restore in parallel, which generally will be faster than serial ontape. - can work unattended, especially helpful for log backup. - you have to use a storage manager. - you can use ISM, but it doesn't do remote operation, so restore for secondary (HDR) will be "imported restore" which is somewhat complicated. - ontape: - no storage manager needed. - transfer of backup to secondary and restore is simple. - only serial operation, nothing is parallel. - continuous log backup with ontape will (periodically) halt and require user interactivity to change tapes (LTAPEDEV). - 2 GB limit for files may hit you (I see you're already aware of this). - changes necessary: - switching from current ON-Bar to ontape: - you probably backup the logs via ALARMPROGRAM and ON-Bar (now), so you should change ALARMPROGRAM parameter in onconfig file (e.g. from .../log_full.sh to .../no_log.sh). This change will require a server restart, but not a long down time. - alternatively you can directly edit the shell script currently configured in ALARMPROGRAM. This can be done without server down time. Though eventually you should change ALARMPROGRAM to reflect the reality, but that can be done during some other, planned down time. - LTAPE... and TAPE... onconfig parameters are mainly used by ontape only. The only significant value for the server is, whether LTAPEDEV is "/dev/null" or not. Since you do not have "/dev/null" now, you can change LTAPEDEV to any value (other than "/dev/null") without effect on server. That means LTAPE... and TAPE... parameters can be changed without requiring server down time. - switching ON-Bar from backup to tape to backup to disk: - I've not done this particular thing before, but I think it will require changes in storage manager only. Therefore no server down time should be required. Hopefully this gives you some ideas. As already recommended by others, I strongly advice to test things, possibly with a small HDR pair of test instances. Include the restore for secondary in your tests, so you get a good picture (and a step-by-step procedure) of how to do that in your particular environment. Regards, Martin -- forum.subscriber@iiug.org wrote on 01.07.2005 00:08:22: > I have IDS 2000 9.21.UC4 running on SUNOS 5.8. I'm using HDR, currently have onbar running for nightly > level 0 archive and logical log backups. Its writing to a small unsupported Legatto tape drive. > > I need to change the Backup and Recovery strategy from tape to disk and am looking for the best/easiest transition. > I have disk space now, but not sure if it will be better to switch to ontape or stay with onbar and use ISM. > I have limited down time, no test system and need to be sure I can back out if necessary. > > We're working on scripts to break the archive into 2 gig files and > an alarmprogram script. > I believe I need to change the tapedev and ltapedev parameters and utilize the ISM parameters in both onconfig > files. Short down time required. > > If anyone has some advice or direction it would be greatly appreciated. --------------------------------- Yahoo! Sports Rekindle the Rivalries. Sign up for Fantasy Football