OPENVMS 7.2 remote backup

[ie3]

Dears,

i have tow speart server ds with openvms 7.2 not cluster  i want cpy from server1 to anther server2.

$copy mok.lis vms3"system 12345678"::$1$DGA1:[SYS0.fawzi]/log

the error was ocure 

$ copy mok.lis vms3"system 12345678"::$1$DGA1:[SYS0.fawzi]/log
%COPY-E-OPENOUT, error opening VMS3"system password"::$1$DGA1:[SYS0.FAWZI]MOK.LI
S;1 as output
-RMS-E-CRE, ACP file create failed
-SYSTEM-F-NOSUCHNODE, remote node is unknown
%COPY-W-NOTCOPIED, DDR1$DKA0:[SYS0.F1]MOK.LIS;1 not copied

i check the decnet status:

$ show net

Product: DECNET Node: DDR1 Address(es): 1.4
Product: TCP/IP Node: ddr1.ddr1 Address(es): 10.1.3.160

$ mcr ncp
NCP>show exec

Node Volatile Summary as of 22-APR-2019 12:52:59

Executor node = 2.20 (DDR1)

State = on
Identification = HP DECnet for OpenVMS Alpha

regards,

[Volker Halle]

You could use the DECnet address of the second node (2.nn) instead of the nodename (vms3), if that node name is not defined in the local DECnet database:

$copy mok.lis 2.nn"system 12345678"::$1$DGA1:[SYS0.fawzi]/log

Volker,

[Maurizio De Tommaso_ · Accepted solution]

There is an incongruence with Decnet definition Address of the DDR1 node, basing on your information :

$ show net

Product: DECNET Node: DDR1 Address(es): 1.4
Product: TCP/IP Node: ddr1.ddr1 Address(es): 10.1.3.160

$ mcr ncp
NCP>show exec

Node Volatile Summary as of 22-APR-2019 12:52:59

Executor node = 2.20 (DDR1)
State = on
Identification = HP DECnet for OpenVMS Alpha

Did you try to reconfigure the DDR1 decnet executor address / scssystemid system parameter ? You should fix the above issue before to go forward with the following steps.

The problem you reported is related to “-SYSTEM-F-NOSUCHNODE, remote node is unknown” system error message.
It means that VMS3 node is not defined into the decnet local DB of DDR1 node.

I suspect you are running Decnet Phase IV (please send me the output of the “mc ncp show exec char” and “$ product show product *” ).

In case of Decnet phase IV:

1- Logon into VMS3 node and capture its decnet node name and address
    $ mc ncp show exec

    From node DDR1
    $ mc ncp
    NCP> Define node VMS3 address y.x
    NCP> Set node VMS3 all

If you are running Decnet Phase V the procedure will be different :

$ run sys$system:decnet_register

DECNET_REGISTER - Manage node registrations in network directory services

Use Return, Ctrl/N, and Ctrl/P to move between input fields
Use "?" to obtain help, Ctrl/Z to cancel

1 - Show information about registered node names
2 - Register or modify node names
3 - Update registered node towers using information from the nodes
4 - Rename a registered node name
5 - Repair the synonym and address links for registered node names
6 - Deregister node names
7 - Export node names to a data file
8 - Import node names from a data file
9 - Set preferences and network values
10 - Manage the directory service
11 - Spawn to DCL
* Option (use Ctrl/Z to exit):

The node VMS3 must be into the same Decnet area of DDR1 node, otherwise you will need a “Routing IV” or an “Area Routing”.

Best regards,
/Maurizio

[ie3]

Thanks alot maurizio,