cancel
Showing results for 
Search instead for 
Did you mean: 

OST API issue

Flyinraptr
Level 5

Wondering if anyone has figured out a work around for this issue.   NB 7.0.1 running on Windows 2003 SP2 - setting up OST with Quantum DXi devices - using the Quantum OST plugin.  OST requires the same id configured with Host Access on the DXi's used to start various NB services and for authentication when creating the Storage Server.  In this case we are using an AD account (we also have NAS shares configured).  The first problem encountered when creating the Storage Server is case sensitivity - although AD is not case sensitive - the DXi and the OST plugin are.  We managed to work through that however, we've encountered an issue where some media servers can only pass the initial authentication check by including the domain in the username (i.e.  domain_name\user_id) and others can pass with only the user_id specified.   Trying to figure out why the name resolution is being handled differently and come up with something that allows all media servers to pass the initial authentication check.  Have tried putting qoutes around it but running a 'tpconfig -dsh -all_hosts' command after creating the Storage Server I'm  seeing cases where Netbackup is not interpreting the 'domain_name\user_id' correctly and subsequently the Disk pool creation fails.   Any ideas?

1 ACCEPTED SOLUTION

Accepted Solutions

Flyinraptr
Level 5

Surprised no one has come across this .... have uncovered a bug or anomoly with Netbackup and OST.  We have a AD process ID created beginning with the letter 'n'.  This ID is used for Access Control on the DXi's and subsequently was trying to use it for the creation of the Storage Servers in Netbackup.  In the both the Disk Storage Server Wizard (and command line method) was using the syntax domain_name\user_id (again the user id begins with 'n').  As it turns out the '\n' is an escape sequence in Unix - and so Netbackup was interpreting it as such and the end result was a carraige return in the middle of the user id (verified using tpconfig -dsh -all_hosts).  As a workaround - tried using a different process id - this time beginning with the letter 'x' and as it turns out '\x' is also a escape sequence - Netbackup replaced the '\x' with an 'F'.  Symantec tech support has confirmed that \p will work - the bug\anomoly is being esclated to Engineering.   Go figure ...  

View solution in original post

3 REPLIES 3

RonCaplinger
Level 6

Assuming the DXi's have a similar setup, we had to make sure the Data Domain hosts file and the media server's /etc/hosts file included the names and IP's for both the media servers and the Data Domains.  This was part of the problem with the initial setup with the DD's, as one of the media servers was also new and I had not added it to one of the DD's. 

With the DD's the host file is changed via a command line, not directly in /etc/hosts.

Flyinraptr
Level 5

Surprised no one has come across this .... have uncovered a bug or anomoly with Netbackup and OST.  We have a AD process ID created beginning with the letter 'n'.  This ID is used for Access Control on the DXi's and subsequently was trying to use it for the creation of the Storage Servers in Netbackup.  In the both the Disk Storage Server Wizard (and command line method) was using the syntax domain_name\user_id (again the user id begins with 'n').  As it turns out the '\n' is an escape sequence in Unix - and so Netbackup was interpreting it as such and the end result was a carraige return in the middle of the user id (verified using tpconfig -dsh -all_hosts).  As a workaround - tried using a different process id - this time beginning with the letter 'x' and as it turns out '\x' is also a escape sequence - Netbackup replaced the '\x' with an 'F'.  Symantec tech support has confirmed that \p will work - the bug\anomoly is being esclated to Engineering.   Go figure ...  

teiva-boy
Level 6

On the West Coast, I see very little Quantum dedupe anything.  Folks just aren't buying it.  They go with other products like DD, Exagrid, and Symantec's dedupe.  Other regions I have no clue...