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 gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Usage parameter MB written not set unequal 0

Status
Not open for further replies.

bahrruse

Programmer
Jun 25, 2003
5
DE
Hello,

I have ARCserve backup version 9.0 running with a HP SureStor Jukebox. In the device window for the Jukebox I do not see for all media the usage parameter MB written set. These are ofcourse media I know that data were written but ARCserve displays 0 MB written in the device window.
Does any body else do know about this problem and has a solution?

Thanks
Rüdiger
 
First off check it from the Database Media view to see if it also fails to show all the details for the tapes.

If it does then it might be a problem with corruption in the Database.
 
Michel, thank you for your reply.
It is the case that I also do not see the media details in the DataBase view. I see the sessions stored but only zeros in the statistics view of the tapes.
Is this enough indication to run a recover DB?
Thanks
Rüdiger
 
It might be better to hold off on the Recover, for fear of recovering a corrupt database. As long as you are uses the default VLDB database the following might help.

A quick test to see if it is database corruption is this:
1) stop all ARCserve services and the Manager
2) make a backup copy of the database directory
3) initilize all the Databases
4) run a quick test backup
5) check the Database

If it still does not work then the data is probably not being sent to the Database by the Tape Engine.

If it now shows the information correctly you know it is database corruption. Now shut down ARCserve again and copy the original database back. Use dbcheck first to look for errors and inconsistancies in the databases. Don't do astpsdat, at least right now. It is the largest database and contains the data on all the files and directories backed up. Start with asobject and asmedia. If there are any errors or even inconsistancies reported then do first a dchain and then a keybuild on them. The larger these databases get and the less frequint the utilities are run the longer it takes and the slower it runs. That is why it is better to leave astpsdat off for now.
 
Hello David,
thankyou very much for your comprehensive and detailed response. It is a great help for me.
Best regards
Rüdiger
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top