Highlighted

Increase parallelism in Networker with subfolders

Hi all.

I've a situation like this:

A directory /oracle/XYZ with some subfolders:

- /oracle/XYZ/directoryA

- /oracle/XYZ/directoryB

- /oracle/XYZ/directoryC

- /oracle/XYZ/directoryD

- /oracle/XYZ/directoryE

...

- /oracle/XYZ/directoryL

If I specify only the directory /oracle/XYZ backup takes a long time.

To make the backup faster I can specify all multiple subdirectory, but in this way if I add a new directory on the server and I forget it in the saveset list i will not backup the directory added.

I would ask you if there is a way to specify as savesets something like:

- /oracle/XYZ/directoryA

- /oracle/XYZ/directoryB

- /oracle/XYZ/directoryC

- /oracle/XYZ/directoryD

- /oracle/XYZ/directoryE

- any other subdirectory of /oracle/XYZ/ not yet specified...

In this way I would be safe to not forget to save any data!

Thank you very much in advace.

0 Kudos
1 Reply
8 Krypton

Re: Increase parallelism in Networker with subfolders

I see two ways to solve this:

1) Use client initiated backup. Create a script that will list the folders name and use that as a parameter to the save command.

2) Create two client instances. One will have the folders you know, and the other one will have /oracle/XYZ/ and a directive to skip all the folders that you have in the first instance. So when you realize there's a new folder, you'll have to add that to the first instance, and include in the directive of the second client.

I believe someone might have better ideas, but those two should work