Search results for query: *

All I have to say is, you should clean when the drive tells you to clean.

You NEED to inventory for BE to see the tape - it is not a bug - I have always had to inventory a single tape drive with BE and with BE since 9.x you can now schedule an inventory before backup. When you restart the services, an inventory takes place when the drive is checked.

I thing to note with EV - the cab file size you create is the maximum size - with the latest EV6 Sp2, the mx cab file size is 99mb. From experience, you will find that you will rarely hit the maximum cab file size. What will kill your backup speed is the Index locations - backing up hundreds...

All I can say about encryption is - soon.

you will be surprised how many times i have heard, i have replaced the drive and still getting the errors. you either have a bad scsi card, cable, terminator, tape or drive :) lots of choices. the error is coming from the operating system. u tried updating scsi card drivers? MS drivers are...

schedule a job on hold. only way to do it.

Bad tape drive/controller? are u getting any events in teh system log when u get the I/O error? have u tried driver from dell for the drive?

u have to inventory every time u change the tape. just setup a scheduled inventory job to run 10 minutes before the job starts.

would say, if nothing has changed, that the tape drive is having a problem reading the tapes. check the tapes to see if there are any soft/hard read errors. also try a redirected restore, see how fast it goes.

You tried stopping the FSA service and run a backup of the share, just to make sure it isn't EV. Are you using AOFO on the file server? maybe try turning that off.

why not use the RSG?

It's an option you don't have - though I thought they got rid of Intelligent Image option in 10 - anyways.. don't worry too much about it. And no you don't include backup exec AOFO store in the the backup - I actually think there is a hard coded exclusion of it anyway.

sure he isnt using Netbackup 5?

No the database does not maintain catalogs - these are separate.

It can - do u want BE to be cluster aware? or just install it on the physical nodes? Either way BE will do both.

you may want to upgrade to 9.1 - its free. Also is the network between the BE server and Snap good? B2D likes to fall offline when the BE server loses contact. You will prob find just restarting the BE services brings the B2D folders back online.

Are the reports in BE any help to you? I think they are written in Crystal reports - you should be able to open one of them that closely resembles your needs - so you can see where it is pulling stuff from in the db.

Check the System logs for any errors - particularly Event ID 7,9,11 and 15 - these signify hardware errors on the tape drive/tapes themselves. Also - do you know which part of the backup is taking longer? brick level mailbox backups?

this should help you out. http://support.veritas.com/docs/248314

You will probably get answers if you post to the Netbackup forum