[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

Veritas 10.x compression/reporting problems

Posted on 2006-05-15
3
Medium Priority
?
371 Views
Last Modified: 2013-12-01
Hi,
I have an install that is giving me problems.
Win2003 server running Veritas ver 10 build 5484, sp 4. Seagate Travan 40 gig drive - 20 native/40 compressed, PCI drive. I was backing up about 24 to 25 gig onto 1 tape, when last week it took two tapes. The first issue is that when it ran onto two tapes the first tape reports that it used 18.9 Gig, had 16.4 gig available with a compression ratio of 6.59:1. The second tape was written to for about 1 minute, then we went into the verify mode. At this point I was at no service packs on veritas so I installed SP4. I removed some files from the backup schedule so I could get back to 1 tape. On the latest backup it reported 17.8 used capacity, 17.5 available capacity, total capacity 19.3, with a compression ratio 10.0:1. I have the jobs set to overwrite, no append. I did a quick erase of the tapes before the jobs ran last week.
My problems are why does veritas report bogus compression ratios, and how can I really tell how much of the tape is available? The graphic representation does not give me a good picture of how much is used/free.
I think we were running onto 2 tapes because we are backing up large PST files towords the end of the job, and this may cause problems estimating tape usage, etc...
I am using the veritas drivers and no errors are being reported.

I posted on Veritas discussion forums but got no real help......

Thanks - Wayne
0
Comment
Question by:wspjones99
1 Comment
 
LVL 22

Accepted Solution

by:
dovidmichel earned 2000 total points
ID: 16684202
When compression is used there is no way to get an acurate figure on the amount of tape left. The drive does all those calculations based of the native capacity, so compression really screws it up.

One way to find out just how much is going to one tape is to run a job you know will fill the tape and have it cancel instead of spanning.

As you know the amount of compression is up to the type of data more than anything else.

I have no idea about the inability of Backup Exec to report the correct figures.

Oh one more thing that is just a side issue and this also I'm sure you know but just in case, Travan tapes should be retentioned every so often. It takes awhile to do it but with Travan it is important. Certainly any time it gets a read error retention the tape and retry the operation. But like I said this is just a side issue and it is doubtful it will have any effect on this problem.
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Is your phone running out of space to hold pictures?  This article will show you quick tips on how to solve this problem.
A look at what happened in the Verizon cloud breach.
This tutorial will walk an individual through the steps necessary to enable the VMware\Hyper-V licensed feature of Backup Exec 2012. In addition, how to add a VMware server and configure a backup job. The first step is to acquire the necessary licen…
This Micro Tutorial will teach you how to reformat your flash drive. Sometimes your flash drive may have issues carrying files so this will completely restore it to manufacturing settings. Make sure to backup all files before reformatting. This w…
Suggested Courses

873 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question