Using minicopy for backing up data

[Nicolau Roca]

Yes, our external backup application is Veritas' NetBackup. But all I have is a BPCD_STARTUP.COM. This DCL script is run by UCX when a BPCD connection is received.

It runs BPCD_AXP.EXE, so I cannot use it to mount/dismount the target disk, as far as I can see.

Thank you anyway Jim

[Wim Van den Wyngaert]

Nicolau,

Why not ?
If you mount the disk just before the run it should work. Unless it does a run/detached ?
Could you post the .com file (as txt) ?

Wim

[Nicolau Roca]

This is the BPCD_STARTUP.COM file. NBU$BPCD is a logical name in the system table which translates to NBU$DIR:BPCD_AXP.EXE

$ !
$ DEFINE/PROCESS SYS$OUTPUT NL:
$ DEFINE/PROCESS SYS$ERROR NL:
$ !
$ ! Netbackup BPCD startup command file
$ ! run by UCX when it receives a connection
$ ! and the BPCD service is enabled
$ !
$ SET PROC/PRIV=ALL
$ !
$ ! define a logical for the netbackup directory
$ ! (you can specify a directory of your own choice)
$ ! THIS DIRECTORY MUST EXIST - CREATE IF NECCESSARY
$ !
$ !DEFINE/SYSTEM NBU$DIR SYS$SYSDEVICE:[OPENV.NETBACKUP]
$ DEFINE/SYSTEM NBU$DIR SYS$COMMON:[NETBACKUP.FILES]
$ !
$ ! define a logical name for the logs file directory
$ ! (you can specify a directory of your own choice)
$ ! THIS DIRECTORY MUST EXIST - CREATE IF NECCESSARY
$ !
$ !DEFINE/SYSTEM NBU$LOGS SYS$SYSDEVICE:[OPENV.NETBACKUP.LOGS]
$ DEFINE/SYSTEM NBU$LOGS SCI:[SCI$BACKUP.NTLOGS]
$ !
$ ! define a logical name for the executable _VAX.EXE or _AXP.EXE
$ ! THIS EXECUTABLE MUST BE INPLACE FOR THE CLIENT TO RUN
$ !
$ ! find out hardware type....VAX, ALPHA or IA64
$ HW$TYPE="VAX"
$ IF F$GETSYI("NODE_HWTYPE").EQS."ALPH" THEN HW$TYPE="AXP"
$ IF F$GETSYI("NODE_HWTYPE").EQS."IA64" THEN HW$TYPE="I64"
$ !
$ DEFINE/SYSTEM NBU$BPCD NBU$DIR:BPCD_'HW$TYPE'.EXE
$ !
$ ! define a logical name for the BP.CONF configuration file
$ ! THIS FILE MUST EXIST - CREATE IF NECCESSARY
$ ! AND MUST CONTAIN THE LINE:-
$ ! SERVER = your_server_host_name
$ !
$ DEFINE/SYSTEM NBU$CONFIG NBU$DIR:BP.CONF
$ !
$ ! define process only logical names
$ ! sys$output/sys$error catch BPCD runtime errors
$ ! assign to file if runtime errors
$ !
$ ! actually run the correct BPCD image VAX or AXP
$ !
$ RUN NBU$BPCD
$ !
$ EXIT

Whenever I interactively try to mount/over=id the target disk and then run NBU, it raises the error "%NBU-E-OPENERR, error opening for input
-RMS-E-DNR, device not ready, not mounted, or unavailable". So I guess running nbu$bpcd implies a detached process...

[Jan van den Ende]

Nicolau,

the end of your procedure:


$ ! define process only logical names
$ ! sys$output/sys$error catch BPCD runtime errors
$ ! assign to file if runtime errors
$ !
$ ! actually run the correct BPCD image VAX or AXP
$ !
$ RUN NBU$BPCD
$ !


This is where you have some control!

First, there may be some useful displays, if you do not discard them.

$ define sys$error NBU.ERR
$ define sys$output NBU.OUT
( if those filenames are already used, pick any other convenient name)

Now, insert:
$ MOUNT/OVER=ID

I _ASSUME_ that in NBU$CONFIG the target defvices of the backup are specified?
If so, you have to remove the shadow set(s) from there, and replace it/them by the dismounted member spec.

I _ASSUME_ that the "%NBU-E-OPENERR, error opening for input
-RMS-E-DNR, device not ready, not mounted, or unavailable" comes from a specification in NBU$CONFIG that does not reflect the private-mounted disk.

And before you can restore she shadow set, you DISMOUNT the member(s) again.
( well, since you mount them process-private, they SHOULD be dismounted if the process finishes, but I prefer to explicitly do it)



HTH.
Success!

Proost.

Have one on me.

jpe

[Volker Halle]

Nicolau,

you would want to check the Veritas Netbackup documentation for references to 'NBU$START.COM and NBU$END.COM' - as mentioned by Jim. These may just be some kind of prologue and epilogue procedures, which Netbackup can run before and after the backup of the disk itself.

Changing the generic TCPIP service startup command file for Netbackup may cause all other possible problems and side effects.

Volker.

[Nicolau Roca]

Bingo!!

Jim (and Volker) were on the right way, so now I'm afraid I submitted only 8 points to Jim's reply :(

Mounting/over=id the target disk in NBU$START (and subsequently dismounting it in NBU$END, following Jan's advice) works properly!!
So I have rewritten our DCL script as there is no need to mount the target disk system-wide, neither changing its label.

Thanks a lot to Jim and Volker, and also to Jan, Wim and John, for your replys, your advices and your time

I'll be closing this thread in a few days

Regards

Nicolau

[Nicolau Roca]

So I finally can use minicopy :)