I Faced the same issue coupe of times & First it got resolved by re-creating the DD resource from the Networker NMC.
Do You have any existing devices configured from this DD?
If yes , we need to delete them (Make sure you dont select the option delete data from the device ) & then recreate the DD device from NMC & once its done , recreate the old devices back (Uncheck the Label Option while recreating - If you wish the existing data to be retrieved back)
Thanks for your response. I followed your instructions and removed devices (unchecked label option) and then removed the DD from NMC. Then I recreated the DD, recreated old devices and tested again. Unfortunately, that didn’t do anything. “Max write streams” is still set to zero.
Simple query - can you write anything to DD (with and without NW)? If answer to any of those is yes, forget max writes on DD. One thing which might be related, though it should not according to compatibility guide, is that you use DDOS 5.2 while 8.1 was built against 5.4 (also, currently recommended 5.2 version is 5.2.4.2 due to DD Boost potential data loss during over-subscription).
Yes, I have no issues writing to DD both with and without NW. But it's the VMware Protection Policies which aren't working. I think I will try updating OS on our DD. As I am running an older version; that may be the issue as you suggested. Thanks for the suggestion.
I'm not trying to say that is the issue - it might be which also equally means it might not be as well. I would rather update NW version first as you have very early build so I would start with that being updated. Here is link to latest release of 8.1 you run:
From there, I would update DDOS, but if you plan to use DDOS 5.4, I would engage support first to confirm this is known issue and that is resolved by such action.
One thing less to take into equation then... NSR is supposed to take this value from DDOS, but since you can write to DD this does not seem to make some sense so it looks more as an issue with DDBoost API or whatever they use to obtain this value. This could be either due to DDOS plugin NW uses or DDOS itself in respect to given NW version or something third. To avoid too many changes, which may bring some other undesirable effects, I would suggest to contact support - especially since they might have to deal with this in the past (though this is not the best part of the year to contact support in the first place).
Even if the workaround works, you should still upgrade your DDOS as the earliest DDOS supported for the EBR solution is 5.3.0.6, so you are likely to run into other issues with this also.
Go with upgrading the DD system or you could try this as a workaround: A similar issue was found by someone else and the following suggested as a workaround by DataDomain Support:
Please set the following system parameter settings and restart the filesystem on the DD box as a workaround for this issue.
TheStorageProto
27 Posts
0
January 1st, 2014 06:00
The error you are facing was observed during beta phase and was caused by:
1. On DD: SNMP ro-community string having restricted hosts
2. known issue
Solution:
1. Check if there is any restrictions on the SNMP; [ snmp show ro-communities ]
2. Upgrade to 5.4.0.8 (DDOS) which is supported
Hope this helps!
kshariprakash
29 Posts
0
December 30th, 2013 08:00
Hi Farhan,
I Faced the same issue coupe of times & First it got resolved by re-creating the DD resource from the Networker NMC.
Do You have any existing devices configured from this DD?
If yes , we need to delete them (Make sure you dont select the option delete data from the device ) & then recreate the DD device from NMC & once its done , recreate the old devices back (Uncheck the Label Option while recreating - If you wish the existing data to be retrieved back)
Regards
Hari Prakash.
FJaved
12 Posts
0
December 30th, 2013 09:00
Hi Hari,
Thanks for your response. I followed your instructions and removed devices (unchecked label option) and then removed the DD from NMC. Then I recreated the DD, recreated old devices and tested again. Unfortunately, that didn’t do anything. “Max write streams” is still set to zero.
Regards,
Farhan Javed
kshariprakash
29 Posts
0
December 30th, 2013 21:00
Hi Farhan,
Can you disable the DD filesystem & enable & verify?
filesys disable - To Disable the DD filesystem
filesys enable - To Enable the DD Filesystem.
I came across a BUG in DD end where in the Max write & read streams were set to Zero.
Regards
Hari Prakash.
ble1
4 Operator
•
14.4K Posts
0
December 30th, 2013 23:00
I would verify that from DD side first. Also, if this happens only by trying to add VBA, I doubt DD filesys is the culprit.
FJaved
12 Posts
0
December 31st, 2013 07:00
As Hari mentioned, I disabled and enabled filesys. That didn't fix it. I restarted the Data Domain and that also didn't work.
How do I verify the max streams from DD side?
ble1
4 Operator
•
14.4K Posts
0
December 31st, 2013 08:00
Simple query - can you write anything to DD (with and without NW)? If answer to any of those is yes, forget max writes on DD. One thing which might be related, though it should not according to compatibility guide, is that you use DDOS 5.2 while 8.1 was built against 5.4 (also, currently recommended 5.2 version is 5.2.4.2 due to DD Boost potential data loss during over-subscription).
FJaved
12 Posts
0
December 31st, 2013 08:00
Yes, I have no issues writing to DD both with and without NW. But it's the VMware Protection Policies which aren't working. I think I will try updating OS on our DD. As I am running an older version; that may be the issue as you suggested. Thanks for the suggestion.
ble1
4 Operator
•
14.4K Posts
0
December 31st, 2013 10:00
I'm not trying to say that is the issue - it might be which also equally means it might not be as well. I would rather update NW version first as you have very early build so I would start with that being updated. Here is link to latest release of 8.1 you run:
ftp://ftp.legato.com/pub/NetWorker/Cumulative_Hotfixes/8.1/Cumulative_8.1_readme.txt
From there, I would update DDOS, but if you plan to use DDOS 5.4, I would engage support first to confirm this is known issue and that is resolved by such action.
FJaved
12 Posts
0
December 31st, 2013 10:00
I have updated NW to 8.1.0.3 Build.219 and that hasn’t worked.
Regards,
Farhan Javed
ble1
4 Operator
•
14.4K Posts
0
December 31st, 2013 16:00
One thing less to take into equation then... NSR is supposed to take this value from DDOS, but since you can write to DD this does not seem to make some sense so it looks more as an issue with DDBoost API or whatever they use to obtain this value. This could be either due to DDOS plugin NW uses or DDOS itself in respect to given NW version or something third. To avoid too many changes, which may bring some other undesirable effects, I would suggest to contact support - especially since they might have to deal with this in the past (though this is not the best part of the year to contact support in the first place).
coganb
736 Posts
0
December 31st, 2013 23:00
Even if the workaround works, you should still upgrade your DDOS as the earliest DDOS supported for the EBR solution is 5.3.0.6, so you are likely to run into other issues with this also.
-Bobby
coganb
736 Posts
0
December 31st, 2013 23:00
Hi,
Go with upgrading the DD system or you could try this as a workaround: A similar issue was found by someone else and the following suggested as a workaround by DataDomain Support:
Please set the following system parameter settings and restart the filesystem on the DD box as a workaround for this issue.
ddsh -s se sysparam set BACKUP_WRITE_STREAMS=16
ddsh -s se sysparam set BACKUP_READ_STREAMS=4
-Bobby
kshariprakash
29 Posts
0
January 1st, 2014 00:00
You can view the Current Valur of Write & read streams set @ DD end by logging in to SE mode & run these commands as mentioned.
se sysparam show
EX :
se sysparam show BACKUP_WRITE_STREAMS
se sysparam show BACKUP_READ_STREAMS
This should give us the current WRITE & READ streams values set on the DD.
HTH
Regards
Hari Prakash.
FJaved
12 Posts
0
January 2nd, 2014 08:00
Thanks everyone for the suggestions. Here is what fixed it:
1- Upgraded DD OS to latest 5.4.0.8 version; however, this step alone didn't fix the problem.
2- The ro-community string was restricted to Networker server only. Removed that restriction on DD.
3- Removed devices and DD device from Networker.
4- Added the DD device again and now it correctly shows max stream values.
5- The VMware Protection Policy error is fixed.