Mark a DIRECTORY as NOBACKUP?

[Volker Halle]

Jan,

would it be possible to create and mount a LD container file (set /NOBACKUP) and have the temporary files be created in a directory on that 'disk' ?

Volker.

[Jan van den Ende]

David,
that would require investing in an extra disk. Because the current dusk connectivity is exhausted, that would require adding an extra controller (which I do not even know if a slot is available). See above, no way!

John,
request coming up.
Setting NO access to the DIR file will not help much. It is not only BYPASS, which the account does not have, but also READALL, which it DOES have, and VERY probably needs.
I don't think I even DARE try without.

Volker,
THAT might be an idea! I will pass it on, and if they do it and it works, I definitely will report!

Proost.

Have one on me.

jpe

[Chris Davis_9]

Hi Jan,

You say that a batch job produces the report files in this directory.

Would it not be possible to either:

1. Modify the batch job to set the /NOBACKUP flag on the files after creation

2. Have another job run (batch or detached) which sets the /NOBACKUP flag on any files in

the directory. This could be set to start at a specific time, run until a specific time, checking every 30 seconds, 1 minute or whatever.

In our setup we have some detached jobs running every 30 seconds or so to check if there is any work for them to do.

Some check specific database files for header records showing that a batch of work is

complete, allowing us to separate printing tasks from data entry programs.

Some check specific pathworks directories for files of a certain specification. This

allows us to automatically process files submitted by PC users.

a simple

$LOOP:
$ set file /nobackup [dir.subdir]*.*;*
$ wait 00:01:00
$ goto loop

...either running constantly as a detached job or submitted to start at a specific time
and with a time check in it should do the job.

Regards

Chris

[Robert_Boyd]

If you really wanted to get carried away with a process that set the files to /NOBACKUP status as each one was put in place and can't modify the batch script that creates them:

1. Create an identifier like NO_BACKUP_DOORBELL

2. set appropriate access control entries on the directory to trigger an alarm for successful writes

3. Create a detached process to listen for security alarms for the NO_BACKUP_DOORBELL identifier. When an alarm comes in, set the proper file(s) to /NOBACKUP.

It would obviously be much simpler to be able to alter the create so that the script does this directly rather than having to write something fancy to clean up after the script.

Robert

[Jan van den Ende]

All,

I entered an enhancement request in Advocacy.

As soon as it gets a number I will report here again, asking for your "I agree"'s.

In the meantime, the "watching procedure" road was chosen.
Ugly, but workable.

Proost.

Have one on me.

jpe

[Klaes-Göran Carlsson]

Hi all

Could a backup/before be a solution?

[Jan van den Ende]

Hi all,

if you think you might have some future use for this:

http://www.hpuseradvocacy.org/node/1987

Add your "I agree" and report here, please.

Proost.

Have one on me.

jpe

[Jan van den Ende]

ping

Proost.

Have one on me.

jpe

[Duncan Morris · Accepted solution]

I have added my support on the advocacy site.

[Ian Miller.]

been there, done that :-)