Forum Discussion
Findings so far:
not imcp for ping (solved in EEB nbcheck)
limit on user name and group name on 20 characters
Local domain group cannot be used only global works.
In the latest update (New Netbackup.msi) only the 20 character limit is still there.
I am told that the findings will be put into the 8.1 installer and in the 81350 technote, which hopefully will get an Active Directory user section.
So I will set this as solved.
- DigPVB7 years agoLevel 4
Just going to add my findings for those who have run into problems with the WSL in NBU 8.0 as well:
- The issues with WSL are OS independent. We have had this issue with both 2008 R2 and windows 2012 R2 servers.
- Running nbcheck manually with the same parameters as the ones used during installation returns no error, the only time nbcheck fails when using a domain user instead of a local user is when it is used during installation.
- The only way to use WSL on a clustered environment is by using a domain user/group, so local user/group is not an option
- The only way to get around this issues is to use the NBPREINSTALL_CRITICAL_OVERRIDE YES option as described in http://www.veritas.com/docs/000020600
- There is a high probability that even though the installation finishes correctly, afterwards you will have issues with WSL. We had to add the WSL user/group to the local admin group on both nodes to keep it running stable.
- Make sure not to deviate from the standard naming for both group and user. For some reason we have had issues when using a different name for both and had to reconfigure WSL as per http://www.veritas.com/support/en_US/article.000116317.html - Michael_G_Ander7 years agoLevel 6
Most of the problems with the AD user account except the 20 character limit should be solved in the latest Netbackup.MSI that was made for us in case 22051390.
What kind of problems have you seen after the installation ? Curious as we generally does not grant administrator privilege and we will deviate from the nbwebsvc and nbwebgrp names.
- DigPVB7 years agoLevel 4
Michael,
.msi for installation was the one that was downloaded from my.veritas portal. I cannot verify whether this is the latest .msi that was created for you in said case.
The issues we saw:
- folder with username under /var/global/Vxss/nbcertservice was generated with the standard username instead of the modified username that was used during installation.- commands to inquire or generate certificates (nbcertcmd) were generating handshake issues or invalid answers
- After reconfigure, the service would boot and keep running but crash whenever the admin console was opened or any calls were passed to said service. This was resolved by adding the user/group to the local admins.
- Michael_G_Ander7 years agoLevel 6
Seems that we might still hit some bumps with 8.0, have not gotten around to test more than installation due to other work.
Related Content
- 6 years ago
- 2 months ago