Ontape - Onbar - Ontape

Posted in 2003

Topics: Backup & Restore, Logging & Checkpoints

Emilio Alejandro Garza Reyes — Fri, 17 Jan 2003 19:09:21 — source: IIUG Forums & Mailing Lists

Hi Guys, I've been working with this problem since 1 week ago, we have a Storage Manager that was Set up last month, before this we used ontape to make full backups and for logical logs, the software(Legato) was configured on the server and then we migrate from ontape to Onbar .. everything worked fine until we need to restore a onbar a full backup on another server, the onbar utility could not read the tape and then we switch to ontape again to restore on that server, the software vendor is working on finding what went wrong with onbar .. but that's not the problem that i'm having, when we configure again ontape on the server, we made a rollback of every change... BUT the onbar utility still working on the machine trying to make backups of the logical logs, we need to kill the onbar_d process and then launch a ontape -c forcontinous backups, i find out that the ALARMPROGRAM variable is the one that detects a log full and then starts the onbar -d -l to backup the logical log, do I need to the change that variable to no_log.sh ?????? Before we migrate from ontape to onbar the ALARMPROGRAM was set with log_full.sh, so we didn't make any change on that ...

↪ replying to Emilio Alejandro Garza Reyes

Butler, Debbie — Fri, 17 Jan 2003 20:51:06 — source: IIUG Forums & Mailing Lists

This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C2BE69.1777FEFE Content-Type: text/plain; charset="iso-8859-1" You are correct in that you do not want to mix ontape and onbar. You can edit the log_full.sh and comment out the onbar line or have it kick off an ontape -a or point to no_log.sh. However we use log_full at our site to trap and check for other event alarms so you want to carry over any logic you have there. As to your Legato issue the secondary machine must match the configuration of the first machine and you need to tell Legato that you want to restore the backup taken from the primary machine. I think the correct env variable to user there is NSR_CLIENT. The client name is connected to the backup restore request. Hope this helps Debbie -----Original Message----- From: Emilio Alej.... [mailto:egarza@citi.com.mx] Sent: Friday, January 17, 2003 2:09 PM To: ids@iiug.org Subject: Ontape - Onbar - Ontape [33] Hi Guys, I've been working with this problem since 1 week ago, we have a Storage Manager that was Set up last month, before this we used ontape to make full backups and for logical logs, the software(Legato) was configured on the server and then we migrate from ontape to Onbar .. everything worked fine until we need to restore a onbar a full backup on another server, the onbar utility could not read the tape and then we switch to ontape again to restore on that server, the software vendor is working on finding what went wrong with onbar .. but that's not the problem that i'm having, when we configure again ontape on the server, we made a rollback of every change... BUT the onbar utility still working on the machine trying to make backups of the logical logs, we need to kill the onbar_d process and then launch a ontape -c forcontinous backups, i find out that the ALARMPROGRAM variable is the one that detects a log full and then starts the onbar -d -l to backup the logical log, do I need to the change that variable to no_log.sh ?????? Before we migrate from ontape to onbar the ALARMPROGRAM was set with log_full.sh, so we didn't make any change on that ... ------_=_NextPart_001_01C2BE69.1777FEFE Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Diso-8859-1"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 5.5.2655.35"> <TITLE>RE: Ontape - Onbar - Ontape [33] </TITLE> </HEAD> <BODY> You are correct in that you do not want to mix ontape = and onbar. You can edit the log_full.sh and comment out the = onbar line or have it kick off an ontape -a or point to = no_log.sh.  However we use log_full at our site to trap and check = for other event alarms so you want to carry over any logic you have = there. As to your Legato issue the secondary machine must = match the configuration of the first machine and you need to tell = Legato that you want to restore the backup taken from the primary = machine.  I think the correct env variable to user there is = NSR_CLIENT.  The client name is connected to the backup restore = request. Hope this helps Debbie -----Original Message----- From: Emilio Alej.... [<A = HREF=3D"mailto:egarza@citi.com.mx">mailto:egarza@citi.com.mx</A>]= Sent: Friday, January 17, 2003 2:09 PM To: ids@iiug.org Subject: Ontape - Onbar - Ontape [33] Hi Guys, I've been working with this problem since 1 week ago, = we have a Storage Manager that was Set up last month, before this we used = ontape to make full backups and for logical logs, the software(Legato) was = configured on the server and then we migrate from ontape to Onbar .. everything worked = fine until we need to restore a onbar a full backup on another server, the = onbar utility could not read the tape and then we switch to ontape again to = restore on that server, the software vendor is working on finding what went wrong with = onbar .. but that's not the problem that i'm having, when we configure again ontape on = the server, we made a rollback of every change... BUT the onbar utility still working = on the machine trying to make backups of the logical logs, we need to kill the onbar_d = process and then launch a ontape -c for continous backups, i find out that the ALARMPROGRAM = variable is the one that detects a log full and then starts the onbar -d -l to backup = the logical log, do I need to the change that variable to no_log.sh ?????? Before we migrate from ontape to onbar the = ALARMPROGRAM was set with log_full.sh, so we didn't make any change on that ... </BODY> </HTML> ------_=_NextPart_001_01C2BE69.1777FEFE--

Ontape - Onbar - Ontape

Related threads

Glossary

Your privacy choices