W3828 Unable to find this media or blank media

[Teknoratti]

There is a strange error occurring in the Activity logs. I've noticed this happened on Monday:
W3828 Unable to find this media or blank media(MEDIA=Friday SEQ=4)

This error shows up continuously in the activity log.

It seems like ArcServe is looking for MEDIA with Fridays ID.

I thought the tapes may have been a problem, used some known good tapes, and ran a test backup. What was strange was the backup was running on the job monitor, but I still kept getting the W3828 error. I ran a test backup, and restore of a PC. I was able to backup successfully, and restore successfully. The backup and restore log entries showed up, but right after the job was complete the errors appeared again.

I stopped, all the engines, then restarted the engines. I checked previous days logs to see what happened before I got this error and I noticed this:

E4115 Unable to register media (EC=Error Code = -2009)
W3502 Unable to add session to database (EC = -2009)

Then it tried to mount Friday's media which was sequence #4
I got the W3828 errors soon after. The only thing I can remember that was not right was over the weekend the database engine was stopped during a backup.

I also received a tape alert saying the library has been manually turned offline and is unavailable for use.

But I believe that error is because the media ArcServe was looking for was not available.

Any thoughts on this strange occurance?

 

[vschumpy]

Database problem:

http://supportconnect.ca.com/sc/redir.jsp?reqPage=search&searchID=TEC376895

 

[Teknoratti]

Did I mention that this error occurs even if Im not running a backup. We have backups scheduled for 9:00PM, but I get the errors all day.

 

[Teknoratti]

vschumpy,

You think this may have something to do with the database?
Please explain

 

[vschumpy]

E4115 Unable to register media (EC=Error Code = -2009)
W3502 Unable to add session to database (EC = -2009)

clearly indicates a problem accessing the db - if you can't access the db or have problems updating it, the predicted media for re-use will be out of whack, which is exactly what you are seeing here. The doc in the link explains how to check and fix it.