The process cannot access the file because

[eskolnik]

If I have a null asm for the P drive , why am I getting process cannot access the file messages.

<< / >>
+compressasm: .
<< &quot;F:\ &quot; >>
+null: *
<< &quot;I:\ &quot; >>
+null: *
<< &quot;P:\&quot; >>
+null: *


save group output

nottelling:I:\ savegrp: suppressed 16 lines of output

* nottelling:I:\ save: I:\WS5xxx4\WS5xxx4.ndf: cannot open (The process cannot access the file because it is being used by another process.)

* nottelling:I:\ save: I:\WS5xxx5\WS5xxx5.ndf: cannot open (The process cannot access the file because it is being used by another process.)

* nottelling:I:\ save: I:\WS5xxx6\WS5xxx6.ndf: cannot open (The process cannot access the file because it is being used by another process.)







Ed Skolnik

 

[sdeb]

Maybe try the following:

+null: * *.*

 

[605]

&quot;null&quot; or &quot;nullasm&quot; does not backup the file but it creates
an entry in the client file index (weird, but null is more
a &quot;phylosophical&quot; directive). Consequently, the file needs
to be accessed.

&quot;Skip&quot; should work better.

 

[eskolnik]

I agree skip would be better EXCEPT I want to back up whatever directory structure exists at any pount in time. I trying to skip backing up Files (non-directory) , but keeping the directory sturcture intact.

Ed

Ed Skolnik

 

[605]

Then null is the only choice. As a consequence you must
make sure that the files are not blocked and most likely
shutdown the application prior to the backup with a backup
command script.