Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MB Written to Tape stays at 0

Status
Not open for further replies.

FrauW

MIS
Jul 24, 2003
126
US
Relevant ArcServe Version: 9.0

Problem: From Device->Details, the MB Written on the tape stays at 0.

Impact: Admins cannot estimate the space left on the tape and therefore cannot change tapes in fashion to prevent backup jobs being broken due to lack of space.

Workaround: Tried to go to Database->Devices->Tape Device and then click on 'Statistics' to see the MB Written however this also didn't work; the number representing MB written remains unchanged.

PLEASE HELP!
 
Suggetsion:

Do a "Regular Inventory" on the tape and then see what the deails show you. I am thinking that there has been a quick erase plus done (or some sort of erase) on the tape(s)...??

Hope this helps...

Brandon
 
This has been happening for months and occurs regardless of the tape that is in the machine. We change the tapes daily i.e. have jobs that run on odd days and on even days. So it has nothing to do with the tape but rather the installation of ArcServe. More ideas? They are all very welcome!

:)
 
Make sure it is current with the updates.

If remote management is used via any third party program, (vnc, pcanywere, terminal services) try it locally from the server itself. The CA way to do remote management is to do a Manager only installation on the local system, and then just select the remote server.

Database corruption, start with asmedia.
 
I had suspected that it is database corruption. Does that mean that we should install fresh? People here are too lazy to reinstall and think that there is some other 'patch' to solve the problem. If they are right please let me know. By the way, the only remote manager is terminal server. However this problem also occurs when one works directly on the server.
 
Reinstall should not be necessary.

Either check and repair the database or just initilize it. The quick fix is to initilize go to the ARCserve Server Admin/Database. To repair see the dbutils doc in the ARCserve home directory, there is also information at the CA support site, support.ca.com. Select ARCserve and then there will be a link to the technical documents. There is also some good info here in the faqs.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top