Saveset with wildcard - limitations?

what is your question?

Wildcard support (for savestes and directives) was added some times ago in 7.x ( I dont know the exact version, but I read it recently)

And it is mentionend as limited and in the first place even experimental.

But again, what is your question?

Question here is whether I am doing right thing and what limitations are to be expected.

Also, where does recover problem comes from.

Thank You

Zlatko

Hello

What you have found in the nsr_client is correct.

I just ran a test but on a linux saveset with wild card

/root/Desktop/TR*
/root/Desktop/lin*

It failed immediately with No such file or directory error.

Mohamed El Hossary

EMC Customer Service

Hi,

did you check powerlink?

When I search for "saveset" AND "wildcard" (All of these words in solutions for product networker

it gives me 14 results, which are are useful. If I switch to "Documents" it gives me the admin guide,

did you check these? If so, which part of the doc is not clear to you?

Thank you, Holger

I did search through documentation, I even cited command reference earlier ..

I will do additional search as you suggest, thak you.

Meanhile, while testing, I backed up saveset "F:\company\homes\a*" and now ALL savesets ("F:\company\homes\a*"  ....  "F:\company\homes\z*") are visible / browsable in Networker User (?!)

How do you think that came about?

Thank You

z

Hello Holger,

Please could you dig more for the document stating wildcards in save sets are allowed now.

I know for sure that using wildcrads in save sets has been forbidden in earlier versions of NetWorker (5.x, 6.x) definitely.

Now time goes on and NetWorker changes, I must have missed something for I cannot remember such document even working every day with them.

I would be interested very much in this.

An other situation for directives, here wildcards have been allowed all time.

Thanks.

Reagrds,

Guenter

Hi Z,

regarding visibility of files when browsing CFI  exist different possible reasons, I would need a support case to do analyze on this.

In older versions are problems with overlapping savesets, it might be mmdb related issue. Not easy to say here.

Regards, H

Hello Guenter,

it was only about two weeks ago when I was in the same situation as you now.

Reading acustomers nsrdb, client definition I saw wildcards and wondered if this could work and is supported.

It works. His daemon.raw and savegroup notification and even mminfo shows it.

And it is supported:

https://solutions.emc.com/emcsolutionview.asp?id=esg57531

There are a lot more solutions, when you search for "saveset" and "wildcard" in powerlink for product networker.

Some of them state, it is a RFE, some of them describe limitations.

Hello Holger,

Thanks a lot for your effort and the link given.

That's really intersting for NW Admin Guide doesn't tell about this.

I'll play around with that .....

Reagrds,

Guenter

Hi Z,

I'm quite sure what you are doing is wrong

If we just focus on EMC statements which says: "Wildcards can only be used at the file system level but NOT at the sub-directory level." it means that if your:

- F:\company\homes\a*

- F:\company\homes\b*

- F:\company\homes\c*

[etc]

.. are part of same fs that you are doing the wrong thing.  I assume they are as otherwise they would be by default stanadlone savesets.  If these are shares coming from some NAS device, then you probably wish to switch to NDMP for NAS device.