sparkyputerguy
IS-IT--Management
Hi there-
Went through a very strange experience with a customer's server. They're running BE 9.1 on Win2K server SP4 that is a domain controller. The server is also running SQL 2000 Std (SP3). Using an older Exabyte Eliant 820 drive on an AHA 2940AU controller. Also using a recent copy of McAfee/NAI virus software.
It started with failed backups because it couldn't back up the WMI repository. Went through the prescribed steps to fix it (reinstalling the WMI ODBC drivers from the Win2K CD, backing up the WMI manually, etc.) No luck.
Tried installing the newest SP for Veritas (SP2?) but couldn't because BE was originally installed on the C: drive and there was only 485MB of free space left. Got error 1711's because of the lack 'o space. Tried uninstalling BE but it wouldn't let me until I had 500+ MB free on the server. Kinda silly, but whatever!
Ended up moving some other stuff, making room to uninstall, uninstalled and rebooted. Installed 9.1 on a larger partition and ran through the setup. Ran the Veritas SP for good measure and rebooted again.
The job that I scheduled ran that night but failed as it started hitting the System State. It gave me an I/O error writing to the tape device. Chalked it up to a bad tape or driver. Updated the driver to use Veritas (I usually prefer vendor or MS provided) and put in another tape. Same thing happened.
Pulled the System State out of the job and got a happy full backup. I've been all over looking for answers but haven't found any. I either hope this helps someone else in the same boat or that someone knows what the heck was going on there...
Thanks!
Went through a very strange experience with a customer's server. They're running BE 9.1 on Win2K server SP4 that is a domain controller. The server is also running SQL 2000 Std (SP3). Using an older Exabyte Eliant 820 drive on an AHA 2940AU controller. Also using a recent copy of McAfee/NAI virus software.
It started with failed backups because it couldn't back up the WMI repository. Went through the prescribed steps to fix it (reinstalling the WMI ODBC drivers from the Win2K CD, backing up the WMI manually, etc.) No luck.
Tried installing the newest SP for Veritas (SP2?) but couldn't because BE was originally installed on the C: drive and there was only 485MB of free space left. Got error 1711's because of the lack 'o space. Tried uninstalling BE but it wouldn't let me until I had 500+ MB free on the server. Kinda silly, but whatever!
Ended up moving some other stuff, making room to uninstall, uninstalled and rebooted. Installed 9.1 on a larger partition and ran through the setup. Ran the Veritas SP for good measure and rebooted again.
The job that I scheduled ran that night but failed as it started hitting the System State. It gave me an I/O error writing to the tape device. Chalked it up to a bad tape or driver. Updated the driver to use Veritas (I usually prefer vendor or MS provided) and put in another tape. Same thing happened.
Pulled the System State out of the job and got a happy full backup. I've been all over looking for answers but haven't found any. I either hope this helps someone else in the same boat or that someone knows what the heck was going on there...
Thanks!
