OTman5
This is my first post and have normally managed to find all what was needed but I am a bit stuck at the moment.
I am running Netbackup 5.0mp3 on windows server 2003 with a tape library attached, all the equipment is old but trying to get budget for new stuff at the mo isn’t working.
Anyway, I have taken over looking after the server and so far have been able to find most solutions, but i am having trouble with this one.
Each weekend we do a full backup of our PST files which goes straight to tape, the PST share is held on a cluster and all has fibre channels to the SAN. For the past few weekends the PST backup gets to around 275GB and then fails. this will then cause the cluster to fail over to the other node.
The errors coming up is: Error Otman5 <Date> 3 Driver or device is incorrectly configured for .
Followed by
Informational Disk <Date> 119 The driver for device \Device\Harddisk0\DR0 delayed non-paging Io requests for 0 ms to recover from a low memory condition.
The pst server has just had a memory upgrade, disk space is ok.
If anyone has any information that may be able to help me out it would be greatly appreciated.
Many thanks
Andy
PS Also i cannot find the OTM_USE regkeys
Comments
OTMAN5
This version of NBU is getting old now (and unsupported I think by Symantec)!
OTMAN is the old "open transaction manager" - it's purpose was to backup open files by creating a cache to handle ongoing transactions.
It was never recommended, however, to try to backup large outlook PST files (or other databases) and could never really
give you a guaranteed restore capability. The way to backup PST files (at this version of NBU) is to shut them down first.
Otman errors were mostly system resources and often disk space issues. If this is a live server and there is activity on it, then OTman will start to use up considerable resources itself and cause delays to disk I/O (possibly related to your error message).
If your PST files (and they sound pretty big) are active while you are running this backup then it may never work (and is not a secure recovery point anyway).
Perhaps try first closing the PST files before backup, and then backing up (and disable OTM for the client). Otherwise look at agents (if these are exchange servers, you would want to be looking at NetBackup Agent for MS Exchange).
Best recommendation, of course is to start by upgrading to NetBackup 6.5.3 or 6.5.4
Dhammica De Silva
"It's better to keep my mouth shut and be thought a fool rather than open it and remove all doubt." (Margaret Thatcher 1975)
Hello and many thanks for the
Hello and many thanks for the quick reply
The backup have been working like this for a number of years and have been OK for 99% of the time just been having these troubles for the past 4 or 5 weeks.
the PST's are on an exchange server and have been working in the past, the info store and individual backups are fine.
how do i go about disabling OTM?
also is there a way i can check if the backup is over fiber or network?
Sorry a few thing in the set up i am still not sure on
Thanks
Andy
how do i go about disabling
how do i go about disabling OTM?
Try this
Open Transaction Manager Registry Settings
These are located in HKEY_LOCAL_MACHINE/Software/Veritas/Netbackup/CurrentVersion/Config:
OTM_USE (if this is not present the default setting is YES and Open Transaction Manager is enabled)
Applicable Settings: "NO" = disabled "YES" = enabled
Whether you need a reboot of the Netbackup Client I cant remember.
Tip: Get overview/document your NBU environment. Run 'nbsu' and review the output.
• If this provides help, please vote or mark appropriate solution.
HelloMany thanks for the
Hello
Many thanks for the replys, the thing is i cant figure out why this has just started to happen....
this week, the backup failed at 250gb again seems to be the same spot each week with the error code 13.
i have had a look around and found info on using Microsoft VSS, i am not worried about enabling this but would like to know why this has started to happen?
sorry forgot to mention that
sorry forgot to mention that the exchange backup are fine from the same server cluster, and this seems to make the cluster fail from on to the other?
Would you like to reply?
Login or Register to post your comment.