Agree with Prydonian - the rule of thumb is half the difference - so 30gig would be great compression. But something has changed in what is being backed up. If you turn on detailed logging and insert that second tape you can find out about what point its prompting for another tape.
If you start...
I would say to run a local backup of the media server to determine if the issue is driver related. You report a network backup. The remote agent for 9.x and 10.x will compile the data in tape format and sent it to the media server where your tape device will compress the data. Would I would...
Did the backup span more than one tape. Take a look at the job log and search for the word "media label" If it used more than one tape its possible that one tape of the set got overwritten after the job
So basically the problem is outside of backup exec at this point. Im assuming if you picked more than a gig it would eventually drop off to 250mb in windows as you reported.
Try NTBACKUP to disk. Run a larger job as you would with backup exec. Another test is to take that 1 gig backup folder...
Well that way I look at it its contant moving part or a spinning hardrive so there is the possiblityr of failure. More so than tape. Although I have seen tape drives fail quite often. It a cheap solution but making sure you have backup exec onfigured correctly is the key.
For DR purposed it...
What I would try first is from you ML360 find a file/folder of about 1 gig. In windows explorer copy it over to the shared disk or your SAN drive. Time it on a watch and watch how long it takes windows to copy it.
If it calculates out to the same rate in BE then is something outside of backup...
Backup Exec is working correctly. Your tapes are rated 40/80 . 80gb meaning a compressed text file. So if it gets over the 40 gig mark then compression is working. It all depends on what type of data you backing up. If you backing up images, database files, etc they are already compressed. If...
Using XP firewall? What error do you get when the jobs fail?
Try these two technotes
http://seer.support.veritas.com/docs/241419.htm - I usually got the registry option on ths technote
http://seer.support.veritas.com/docs/238618.htm
I only work from a terminal session. Log into a terminal windows as a root eqivalent and change dir to the install files.
issue the command ./INSTALL
It's case sensitive and use all capa.
After that the options the the screen are easy and self explanatory.
It wont work in 8.6 ..not supported at all. 8.6 is no longer supported by Veritas as well. Your library was made way after the last veritas drive rupdate for 8.6
Upgrade to 9.1 or 10.x and it will work just fine.
Basically the Veritas driver package includes the library support - a list of...
Incorrect on the windows remote agent.
cdex Im assuming your running Backup Exec 9.x
Here is the Mac/Unix Agent
http://seer.support.veritas.com/docs/271744.htm
Basically your going to be prompted for the media server name - your windows media server. I usually use the ip address.
Then you be...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.