Recent content by jamkey

Did you plan on letting us know what the error message in the failed job was?

if you are going off of the readout from the job history, I think that's broken in 9.0. It always says there is no compression. But compression is actually happening. The new job reporting xml stuff seems to be a bit buggy, so I'd expect to see some patches for that soon.

"Database specified does not exist" is an error the Backup Exec Device & Media service gives when it is having problems opening the BE PVL.MDB (a MS access db with info about the drives, tapes, and media sets). There are several technotes on this, just put in that exact error on the...

Since you do have a BENT install already on win2k ready to do a restore if necessary, here's a temp solution... Setup NTBackup on the remote Win2k server in question (the backup applet in Win2k, unders Start > Accessories, System Tools, Backup) to backup the local system state to a local file...

Before anyone panics in reading this thread, these are the conditions for this defect to arise and require tapes to be sent into Veritas for recovery (as per the technote): -- SQL and Backup Exec were installed on multi-processor servers. -- SQL was installed as a cluster aware application...

I'm gonna go out on a limb and say its b/c 7.3 was released well before Windows 2000 was released and doesn't support Windows 2000 (thus System State). Sorry for the sass... couldn't resist. It may also be worth noting that 7.3 is no longer supported. So that, in combination with the System...

This is a Veritas Backup Exec forum, not NetBackup... sorry :( I think Veritas has a NetBackup forum on their site, but I'm not sure.

There is no such utility that I know of, certainly not one on Veritas' site. Can you give more detail about this "bad media" error? Does it change the state of the media in the devices tab of BE or is this just something you see in the job log? Can you paste the error here? Also...

If you can still backup the admin shares for these machines (c$, d$, etc.) but just can't push out the new OFO agent then you have 2 options... you can spend a lot of time troubleshooting the peculiar difference on this machine in terms of security, share setup, registry, etc. OR you can simply...

I believe ROBROS is not refering to actual corrupt files per se (PST files) but mailbox "items"/messages, that are listed as corrupt in the mailbox backup. The mailbox backup uses the MAPI protocol transport provided by the MAPI client installed on the Backup server. So BE is...

Hmmm... never seen anything quite like that... I'd recommend checking the System Event viewer on the BE (Backup Exec) server for any errors at the time you ran this job. Also, I had to do some research to figure out what kind of DAT drive you were refering to... If I'm correct in my...

If you check the following technote out, http://seer.support.veritas.com/docs/229867.htm, you will see a link to all the release notes for each version of BE... a great technote to keep handy. If you go to the link for 8.5 rev 3572 (not 3572rc9) you'll see it mentions a corrupt top of...

probably a communication problem w/ the h/w... try powering down everything, then bring up the drive and then the server...

So if you exclude this mailbox then it doesn't hang? Have you considered running repair utilities on the mailbox or exporting the data to .pst, deleting and re-creating it, and then re-importing the data? I believe there's a Microsoft Q article on doing this. Also, you might want to consider...

Do you mind pasting in the part of the job log that showed the error without the carats (^)? I'd like to see it for my own future reference... thanks in advance.