On the Windows 2008 NetBackup Client, disable the Symantec API called NTIO. This will cause NetBackup to use the Microsoft API called 'BackupRead' - which does not encounter the same timing error.
STEPS TO DISABLE NTIO
1. Click Start | Run, type regedit, and click OK
Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.
2. Browse toHKEY_LOCAL_MACHINE\Software\VERITAS\NetBackup\CurrentVersion\Config
3. In the Config registry key, create a new key called NTIO
4. In the NTIO registry key, create a REG_DWORD value, give it the name UseNTIO and the valuedecimal 0 (zero)
1. Click Start | Run, type regedit, and click OK
Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.
2. Browse toHKEY_LOCAL_MACHINE\Software\VERITAS\NetBackup\CurrentVersion\Config
3. In the Config registry key, create a new key called NTIO
4. In the NTIO registry key, create a REG_DWORD value, give it the name UseNTIO and the valuedecimal 0 (zero)
Please Note :- This has been fixed in Netbackup Version 7.5
If you have a Filer which is serving your CIFS share then please check if SMB2 version was enabled as both server and filer should use same SMB version.
You can check this using the below command check if it was on
If you are using SMB1 in your server and want to use the same in filer as well you can very well change the value in filer on fly it will not disturb your CIFS sessions but what ever the session going to be started after enabling will be running under SMB1.
If you have a Filer which is serving your CIFS share then please check if SMB2 version was enabled as both server and filer should use same SMB version.
You can check this using the below command check if it was on
If you are using SMB1 in your server and want to use the same in filer as well you can very well change the value in filer on fly it will not disturb your CIFS sessions but what ever the session going to be started after enabling will be running under SMB1.
No comments:
Post a Comment