Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

2022

October 17th, 2018 08:00

NetWorker 9.2.1.5 global directive problems

Hi there,

we've got a fresh installed NetWorker 9.2.1.5 environment running on CentOS 7.5 Linux. We have five database servers running Oracle 10g on it. The database files are stored in the following folders:

Server 1 => /oracle1

Server 2 => /oracle2

...

Server 5 => /oracle5

For the database backup we're using the NMDA Module so we have this and the NetWorker client software (9.2.1.5) installed on this systems (CentOS 5.11). I want to do a file system backup for this systems as well and don't want to save the oracle folders because they are very big. I decided to create a directive that looks as follows (due to NetWorker Admin Guide):

<< */oracle[1-5] >>

+skip: *

In the client setup I chose this directive for each client and set the save set to All.

When I start the Workflow for this group the backup action monitor shows the following save sets:

Server 1:

/

/boot

/oracle1

Server 2:

/

/boot

/oracle2

and so on...

It seems, that the directive is not working. I can't find anything in the logs that says the client tries to use the directive.

I also created a directive for each client because I wasn't sure about the new wildcard syntax for the folders:

<< /oracle1 >>

+skip: *

Can someone please help me with this?

Regards

Hendrik

263 Posts

October 19th, 2018 06:00

After the backup completes, and you browse the client's files that were backed up, you will see the oracle directory backed up, but not the files within the oracle directories.

In addition, you will see the hidden files too, because your skip "+skip: *" does not skip the hidden files (those that only have extension and no file name).


To skip all files in a directory, use:

  +skip: * .?*

263 Posts

October 19th, 2018 06:00

Actually, using something like: << */oracle[1-5] >> is supported in NetWorker 9.2.x.


The preceeding * prepares NetWorker to expect wildcard characters.

2.4K Posts

October 19th, 2018 06:00

As NW does not recognize a 'set' you need to specify each directory separately.

Do not forget that this will make its way to result in an absolule pathname.

3 Posts

October 22nd, 2018 05:00

Thank you very much. It is as you described. Thanks for that.

2.4K Posts

October 23rd, 2018 04:00

Thank you Wallace for pointing that out.

I wish this feature would have made its way to the Release Notes ....

3 Posts

October 23rd, 2018 04:00

Bingo, you can find it in the NetWorker Admin Guide for Version 9.2.x

No Events found!

Top