Storage Server Configuration Wizard: RDSM has encountered an STS error: ioctl failed (2060017)
In playing a bit with Media server deduplication in NetBackup 7.0 GA, I have run into an issue where the Storage Server Configuration Wizard comes up with an error during the configuration phase, on Windows:
database system error.
RDSM has encountered an STS error: ioctl failed (2060017)
Here is a screenshot of the wizard in this state:
After reproducing this error a number of times on the same machine (reimaging in between tests), we had some engineers take a look at the system. As it turns out, the NBU 7.0 GA code, during the PD engine configuration, expects that the system is able to ping itself (have self name resolution). Not an unreasonable request, however in this case my host could not ping itself because it had an incorrect hosts file.
As it turns out, patches since the GA release change the behavior during configuration to use localhost, instead of the host's name.
In our case we fixed the name resolution problem, and the wizard has gone on its merry way, and has completed successfully.
The main purpose of this blog is to ensure that someone else looking under this error message one day can find this information, as I couldn't.
About Backup & Recovery Community Blog
The Backup and Recovery Community Blog is the perfect place to share short, timely insights including product tips, news and other information relevant to the Backup and Recovery community. Any authenticated Connect member can contribute to this blog.
Comments
I met the same problem with
I met the same problem with you, but I do not know how to solve, can you help me?
We have the same problem
We have the same problem while creating 'Media Server Deduplication Pool' on the master ifself.
Of course the master can ping itself and adding hostname in hosts file doesn't help.
------------------------------------------------
We have made a simple mistake. The master server we try to create dedup storage server is 32-bit which doesn't meet the system requirement.
Now we add another 64-bit media server as dedup storage server, everything is fine.
Pay attention to
Pay attention to the error code number... I've seen different ioctl error numbers mean different errors.
Definitely the 32-bit versus 64-bit will cause this issue. However you will notice from this technote that the ioctl error code is different: http://seer.entsupport.symantec.com/docs/336606.htm (at least in this case).
Another one that doesn't work is when you install this on Windows and use pure drive letters (e.g. G:\) as the storage and/or database path. Apparently you must use a folder path, e.g. G:\dedupe_storage\.
Principal Learning Consultant with Symantec Education Course Development
Same error, different problem!
I have the same error, with the same exact error code (2060017), however the issue isn't the server can't ping itself. This issue is the server is seemingly unable to create the servername.cfg file in netbackup\bin\ost-plugins.
During storage server creation the registry edits are successfully made and the files/folders are put in the directory for the disk pool, but the .cfg file cannot be created for some wacky reason. I always get this error in tpcommand:
23:43:51.270 [3540.2124] <16> servername: get_agent_cfg_file_path_for_mount pd_register failed for configuration file C:\Program Files\Veritas\NetBackup\bin\\ost-plugins\servername.cfg
Any Ideas?
Interesting
No, I have no ideas, but would make sure that the networking settings are all setup correctly (nslookup, ipconfig, hosts file, dns, etc)
I didn't look in the tpcommand log for my problem, so can't tell you if the error is consistent with my problem.
Please keep us updated though, esp if you open a support case and get a different response!
Principal Learning Consultant with Symantec Education Course Development
Same or similar issue here
Running a 2008 R2 server I'm experiencing the same issue with error code 2060017. Im able to ping hostname as well as the servers fqdn without any issues.
I haven't been able to roll back the partitially installed media server deduplication pool and if I try to run the wizzard again I got an auth error, since this is an new install it was quite easy to uninstall the entire netbackup installation as well as clearing the associated registry keys manually. I also removed all data in the db and data path prior to the reinstallation.
I noticed the same thing as ZexisStryfe, %programfiles%\Veritas\NetBackup\bin\ost-plugins\fqdn didnt exist.
I figured out that If I placed the db and data in the same folder the installation succeeded but since performance will be degraded this isn't really a good soution...
Thanks for this precious
Thanks for this precious informations !
I am experiencing exactly the same problem (on 2008 R2 64bits server too). Same first error then auth error ... grrrr, too bad that I didn't see this post before :'(
I realy don't feel to re-install because I already configure my robot and my backup tests are ok on tape. Don't like to play in windows registry too ...
I am wondering how same storage path for data and database will affect performance ...
I opened a case to symantec, I keep you inform if support find a solution.
Many thanks for this post, you got my vote :-)
NB-7 Win2003 master server
NB-6.5.5 Linux RHEL AS rel4 media servers x2
PD-6.6.0.2 Linux Suse 10.2 x2
NB-7 Win2008R2 media server x1
To resolve the authorization
To resolve the authorization error, I applied the support note bellow :
http://seer.entsupport.symantec.com/docs/346814.htm
NB-7 Win2003 master server
NB-6.5.5 Linux RHEL AS rel4 media servers x2
PD-6.6.0.2 Linux Suse 10.2 x2
NB-7 Win2008R2 media server x1
I had this error. I got it
I had this error. I got it fixed my creating a log directory:
/usr/openv/volmgr/debug/tpcommand
Then I noticed this:
pdvfs_get_install_path: could not find (/etc/pdregistry.cfg) No such file or directory
I had done some testing and cleaned up everything, but my /etc/pdregistry.cfg was a symbolic link to a non-existing file. So I rm'd the /etc/pdregistry.cfg link and copied in a new one:
cp /usr/openv/pdde/pdconfigure/cfg/userconfigs/pdregistry.cfg /etc
Re-ran the wizard and it worked!
Excellent
Sounds great, Karlhungus.
Note also, there is a tech Article out there which covers how to remove deduplication (e.g. in case you have a failed configuration and want to try again). It is covered here:
http://www.symantec.com/docs/TECH124898
You'll notice that one of the steps is resetting the deduplication 'registry' (on UNIX a la your copy command, but different steps entirely in Windows).
Doh... just noticed it's the same one that digicelfwi mentions, above!
Principal Learning Consultant with Symantec Education Course Development
RDSM has encountered an STS error: ioctl failed (2060053)
I'ev got error "RDSM has encountered an STS error: ioctl failed (2060017)"
When we try to reconfigure the master server dedup option. We have used the atricle TECh124898 to removed the old one.
What can be wrong?
I had similar problem but in
I had similar problem but in my case I was trying to re-use old Advanced Disk storage server to run DeDup. After deleting it from NBU, plus providing correct path to DeDup pool and image DB it worked straight away.
Well done Tomer Gurantz
Would you like to reply?
Login or Register to post your comment.