Setting up media server deduplication. having issue with credentials or ioctl errors

Article:TECH124898  |  Created: 2010-01-04  |  Updated: 2011-03-11  |  Article URL http://www.symantec.com/docs/TECH124898
Article Type
Technical Solution


Environment

Issue



Setting up media server deduplication. having issue with credentials or ioctl errors


Solution



Note:
This procedure is outlined in the Symantec NetBackup 7.0 Deduplication Guide (TECH127071), starting on page 73.  Please note that step 4 outlined below is not currently reflected in the documentation.  This technical note should serve as a temporary replacement for the section entitled Resetting the deduplication registry.
 
While running the 'Configure Disk Storage Servers' wizard to configure a 'Media Server Deduplication Pool' it is possible to encounter errors preventing successful completion.
Common mistakes include:
- Choosing a media server with an unsupported OS for Media Server Deduplication. For example, 32 bit Windows media servers are not supported although they will still be presented as a choice during the wizard.
- Choosing a storage path that does not include a directory/folder name. For example, D:\data is a valid storage path, but D:\ is not. The D:\data directory must exist prior to running the wizard.
Failures at this level are early enough that none of the reconfiguration mentioned next is required, but it should still be checked if problems persist.
If some other issue caused the failure of the wizard to complete, it is possible to remove all traces of the Media Server Deduplication Poll and start over. If no backups have been run to the dedupe storage unit, or if the customer is willing to expire all the images that may have been written -- for example, during initial configuration or a test environment -- these are the steps necessary to remove Media Server Deduplication out of the configuration completely so that the customer may start over.
1) Clear out NBU - Expire the images, delete the STUs, delete the disk pool, delete the storage server and credentials.
 
2) /usr/openv/netbackup/bin/bp.kill_all on media server (\veritas\netbackup\bpdown for Windows media server)
 
3) Delete the storage directory on the media server (for example /MSDO) (and db path, if it was specified)
 
4) Delete the PDDE agent cfg files:
WARNING: Do not remove any of the files ending with .so (libstspipd.so and libstspipdMT.so), and pd.conf. These are the actual PureDisk plug-in and should not be removed.
 
/usr/openv/lib/ost-plugins/ (UNIX)
and
<install>/netbackup/bin/ost-plugins/ (Windows)
on media server (and other credentialed hosts).
for example, /usr/openv/lib/ost-plugins/media1.cfg.
 
Run /usr/openv/netbackup/bin/admincmd/bpstsinfo –pi to make sure the PureDisk plug-in is still listed.
 
5) Erase the PD registry
UNIX: cp  /usr/openv/pdde/pdconfigure/cfg/userconfigs/pdregistry.cfg /etc/pdregistry.cfg
Windows: edit the registry entry HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\postgresql-8.3\ImagePath
change:
"C:\Program Files\Veritas\pdde\pddb\bin\pg_ctl.exe" runservice -N postgresql-8.3 -D "c:\storage\databases\pddb\data" -w
to
"C:\Program Files\Veritas\pdde\pddb\bin\pg_ctl.exe" runservice -N postgresql-8.3"
(remove the -D and everything to the right of it)
 
Also delete the contents of the following keys in the Windows registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\PureDisk\Agent\ConfigFilePath
HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\PureDisk\Agent\EtcPath
 
6) /usr/openv/netbackup/bin/bp.start_all on media server (\veritas\netbackup\bpup for Windows media server)
 
After all of these steps are completed successfully you can re-run the wizard.
 
 
 



Legacy ID



346814


Article URL http://www.symantec.com/docs/TECH124898


Terms of use for this information are found in Legal Notices