Unsolved
This post is more than 5 years old
6 Posts
0
571
December 12th, 2007 05:00
OpenVMS client and open files
I have created a .NSR file in the root of my disks to add the OpenVMS /ignore=interlock directive, but it doesn't seem to work.
Since I installed it, i still get the error that some files are not backed up because they are open.
My save set information has the two disks I want to backup
nodea_01$DISQUE:
nodea_02$DISQUE:
and on each of the disk roots [000000], I have a .NSR file containing
<<"nodea_01$DISQUE:">>
+NULL: *.LOG;*
+NOLOCK: *.*;*
and
<<"nodea_02$DISQUE:">>
+NULL: *.LOG;*
+NOLOCK: *.*;*
Is there something wrong with my syntax?
I should be able to force this directive into the saveset on the server-side, no?
Since I installed it, i still get the error that some files are not backed up because they are open.
My save set information has the two disks I want to backup
nodea_01$DISQUE:
nodea_02$DISQUE:
and on each of the disk roots [000000], I have a .NSR file containing
<<"nodea_01$DISQUE:">>
+NULL: *.LOG;*
+NOLOCK: *.*;*
and
<<"nodea_02$DISQUE:">>
+NULL: *.LOG;*
+NOLOCK: *.*;*
Is there something wrong with my syntax?
I should be able to force this directive into the saveset on the server-side, no?
0 events found
No Events found!


dpinink_silva
2 Intern
•
724 Posts
0
December 12th, 2007 05:00
<<"sys$sysdevice:[000000]">>
I mean, may be in your case it should be:
<<"nodea_01$DISQUE:[000000]">>
As I told you, I know nothing about this, so ignore my post if it's totally wrong
RobertC2
6 Posts
0
December 12th, 2007 10:00
I even tried <<"/">>, but that didn't work either.
VolkerHalle
9 Posts
0
July 28th, 2009 07:00
you might need to use the correct Logical Volume Name for your disks. You can obtain this with:
$ WRITE SYS$OUTPUT F$GETDVI("your-disk-name","LOGVOLNAM")
USERDISK1
Then create the .NSR file as:
$ CRE your-disk-name:[000000].nsr
<<"USERDISK1:[000000]">>
+null: *.log;*
+nolock: *.*;*
This worked fine for me with Networker for OpenVMS Client v7.3.4
Volker.