Unsolved
This post is more than 5 years old
116 Posts
0
1536
pool name vs. underscore
Dear Colleagues,
Is there anyone using underscore character in pool name which is associated with a ddboost device?
Only "NetWorker and Data Domain Devices Integration Guide" guide tells me the following restriction:
"Except for pool names and hostnames, use standard alphanumeric characters,
including dot (.), hyphen (-), and underscore (_), with no spaces and no special
characters. Pool names and hostnames may not use underscores (_).""
I'm not sure that this is still valid and I also don't know how to get someone from support who can really validate it (we opened a case, but the support colleague could confirm only that this sentence exists in the guide but when he tries it it works.
Underscore could be very useful for us, the pool names could be much more readable.
TIA,
Istvan
ble1
2 Intern
2 Intern
•
14.3K Posts
0
November 27th, 2015 02:00
I'm using underscore with pool names.
crazyrov
4 Operator
4 Operator
•
1.3K Posts
0
November 27th, 2015 03:00
For pools the the "_" are valid but when it comes to the label the "_" is not accepted. Usually when a pool is being created the label for the pool is automatically created and incase you use a "_" you will face difficulty while labeling the tape.
bingo.1
2.4K Posts
0
November 27th, 2015 03:00
@crazyrow
Your statement seems to be incorrect, at least for the current version 8.2.x
This is obvious as NW itself proposes the "_" as separator in the label template creation window.
crazyrov
4 Operator
4 Operator
•
1.3K Posts
0
November 27th, 2015 04:00
You should be referring to the "separator" field. I assume the discussion is on the resource names.
nsradmin> create type: nsr label; name: Test_01
type: nsr label;
name: Test_01;
Create? y
create failed: Character `_01' is invalid in name `Test_01'
nsradmin> create type: nsr label; name: Test_
type: nsr label;
name: Test_;
Create? y
create failed: Character `_' is invalid in name `Test_'
nsradmin> . type: nsr
Current query set
nsradmin> p
type: NSR;
name: vailankanni-pc;
version: NetWorker 8.2.0.5.Build.510 Enterprise Edition;
comment: ;
bingo.1
2.4K Posts
0
November 27th, 2015 06:00
Hi crazyrov,
from nsradmin you are lucky - at least you get a clear statement.
From the NW Admin GUI, the story is even more weird - i just verified that with NW 8.2.18 again:
- There is no problem to create a pool "A_B_C"
- You will be asked to confirm the default/auto label template.
No issue - NW will even show the pool's label template in the Admin GUI !
But you will not be able to use it.
- Once you try labeling, a window will popup saying:
Could not find 'NSR label' resource 'A_B_C' because NW never created it :-(
- But using a "_" in a volume label is no issue at all.
Isn't that crazy, rov ;-)
bingo.1
2.4K Posts
0
November 27th, 2015 07:00
I just verified with NW 9 that here the default label template for the pool will be auto-corrected in the background without any notice (in the GUI) - the underscores will be deleted.
If confirmed by the admin, the pool "A_B_C" will automatically get the label template "ABC" assigned.
crazyrov
4 Operator
4 Operator
•
1.3K Posts
0
November 30th, 2015 03:00
Yep, that is exactly what i had encountered. its the just that the name of the label template resource again cannot contain the "_".
NetWorker sometime acts Crazy indeed
oldhercules
116 Posts
0
November 30th, 2015 23:00
Hi,
Thx for the replies. Do I have to use an auto label template in the newer NW versions?
I always used to create label template first and then the pool.. or to be more precise I don't know how to ask NW to auto-create the label template for me
... so what's the conclusion? May I safely use '_' character in pool names?
bingo.1
2.4K Posts
2
December 1st, 2015 00:00
Of course you are free to use your own label template. NW will just make sure that there is one in case he needs it.
The way you work will almost never lead you to create an auto label template.
If you have create a new pool and did not have a label template assigned, then NW will prompt you whether it shall create one by itself.
Yes, it is (currently :-) safe to use underscores in pool names.
ble1
2 Intern
2 Intern
•
14.3K Posts
1
December 1st, 2015 03:00
In my case, I use _ in pool and for template I use default. Because I want to label volumes manually, I always used for disk devices what I would type (unlike with tape, once I create disk devices I rarely add more so labeling is one time only action). When using labeling that way, I can use underscores as well, for example:
# mminfo -r pool,volume | sort -u
pool volume
NYC_bVLAN666 NYC_bVLAN666.001
NYC_bVLAN666 NYC_bVLAN666.002
NYC_bVLAN123 NYC_bVLAN123.001
NYC_bVLAN123 NYC_bVLAN123.002
NYC_bVLAN123 NYC_bVLAN123.003
NYC_bVLAN123 NYC_bVLAN123.004
NYC_bVLAN123 NYC_bVLAN123.005
NYC_cVLAN666 NYC_cVLAN666.001
NYC_cVLAN666 NYC_cVLAN666.002
NYC_cVLAN123 NYC_cVLAN123.001
NYC_cVLAN123 NYC_cVLAN123.003
NYC_cVLAN123 NYC_cVLAN123.004
NYC_cVLAN123 NYC_cVLAN123.005
BST_bVLAN666 BST_bVLAN666.001
BST_bVLAN666 BST_bVLAN666.002
BST_bVLAN123 BST_bVLAN123.001
BST_bVLAN123 BST_bVLAN123.002
BST_bVLAN123 BST_bVLAN123.003
BST_bVLAN123 BST_bVLAN123.004
BST_bVLAN123 BST_bVLAN123.005
BST_cVLAN666 BST_cVLAN666.001
BST_cVLAN666 BST_cVLAN666.002
BST_cVLAN123 BST_cVLAN123.001
BST_cVLAN123 BST_cVLAN123.002
BST_cVLAN123 BST_cVLAN123.003
BST_cVLAN123 BST_cVLAN123.004
BST_cVLAN123 BST_cVLAN123.005