Ask the Expert [Video]: How to Create Directives on NetWorker
Welcome to our new Ask the Expert video approach. On this thread we’re introducing a How-To Support video and an EMC Subject Matter Expert. We invite you to watch and post any questions, thoughts or feedback, based on the topic at hand. During the time this event is live our assigned SME (s) will be answering your inquiries as they get posted. After the assigned period has ended we'll leave it open so that everyone in the community can collaborate.
The following video demonstrates how to create directives on Networker. Our Support SME, will be around to assist January 11 - 15. We're looking forward to your replies.
Here is your featured How-To video
Share this event on Twitter or LinkedIn:
>> Ask the Expert [Video]: How to Create Directives on #NetWorker http://bit.ly/22NJ3JC #EMCATE<<
Hi bingo, I'm not sure you received the private message I sent to you Thursday. I requested that we take this discussion privately, hence I offered my email. I never received your email message, yet you insist on taking this publicly. I understand that this is your preference so I will respect it.
I appreciate your interest in helping us and the community to improve the quality of the content. Yesterday, based on your observations, we made edits to the title and description on this thread. If you still object the terminology being used, could you please provide details on your concern. We will be sure to once again take a look and revise if necessary.
This Ask the Expert session is now open for questions. For the next couple of weeks our SMEs will be around to reply to your questions, comments or inquiries about our topic. Let's make this conversation useful, respectful and entertaining for all.
Let me kick off this with few question. Imagine you are under UNIX/Linux. You have following structure of file systems:
/
/data
/data/goo/gle
/home
/nsr
/opt
/usr
/var
I do have some data under /data/goo/foo/somewhere_below which I wish to skip, but not under /data/goo/gle/foo/somewhere below.
Questions:
is directive, when placed against << /data >> applicable only to that file system/partition or does it spawn onto /data/goo/gle too in case of "+action"? (like +skip: *.bzz)
how does directive act (or how does save act in combination to directive) if you have symlink which goes to some other place (like another partition or even same partition but where target location is not originally covered by initial directive range - for example, if I have directive for << /data/goo >> and under /data/goo/foo there us symlink to /data/bar - will skip action work or not?
I assume for special characters in terms of localization, one needs locale on both server (directive owner) and client (save owner) to be the same so they would understand each other?
unfortunately I did not receive any mail - I just noticed that my comment has been deleted. But I also noticed the corrections you made.
Please understand that it is just my intention to just name the details correctly ... especially as an ex NW instructor I am keeping an eye on this issues. I just want to make sure that all the people speak the same proper language. It surely improves understanding an especially helps novices.
"Directives are resources that contains special instructions that control how the NetWorker client software processes files and directories during backup and recovery. ..."
Directives are "specific rules for uasm" and consequently ... like 'save' & 'recover' a client specific program.
Directives are resources that contains special instructions that control how the NetWorker server processes files and directories during backup and recovery. NetWorker administrators can create directives to customize the NetWorker software to your specific needs, maximize the efficiency of backups, and apply special handling to individual files or directories.
I agree, you are absolutely right. I will start posting some examples and advanced options of directives here. That might be useful for wide audience.
Example which you have mentioned is very muchuseful. We always tend to use C:\, D:\ etc specifically for windows clients. Mostly we modify existingdirectives readily available in NetWorker, rather than building new one.
Please post more similar advanced options here, it will be good candidate for discussion.
I'm not sure if this is still applicable to current code, but in old days, with dense file/folder structure, save/uasm walk was spending some time on checking if there is client side directive (nsr.dir on Windows and .nsr on UNIX/Linux). If such directives were not your thing, and they can cause some issues if you forget about them, then placing ignore as part of standard directive for all (or most) of your clients could cause some performance gains. That was in old days of NW5 and maybe 6 - since then code and box performance overall have changed (increased) so I do not have any benchmarks whether this is applicable nowadays.
bingo.1
1 Rookie
•
2430 Posts
3036
0
Posted January 9th, 2016 03:00
@Roberto,
removing my post once again does not improve the terminology fault you state here.
Anyone can read the correct window title and verify the facts.
Please be correct. And be fair.
---------------------------------------------------
Hi Roberto,
is this a new feature? - Directives are created from the NW Admin GUI which must be opened via NW NMC.
To avoid confusion, please do not set wrong expectations and use the correct terminology.
Thank you.