Posted on 2004-04-08
I am running veritas 8.60 rev 3878 on a file server with a c:\ drive with 2.24GB and a d:\ drive with 53.6gb. This is a total of 55.84 gigs of data that is fully backed up every night. The last known good backup I have had was around 43.5GB. It has grown as usuall to the 55.84gb of total data. It is around 46.5GB that it stops trying to backup at and gives me a error telling me to remove the media from the drive and then prompts me to insert media into the drive. If I keep trying to use the same media tape it will do this endless loop of asking me to remove and insert media. If I insert new media then It continues the backup on a second tape. After it finishes the backup on the second tape then it will want me to insert the 1st tape for verification, and I am assuming the second tape but I have not gotten that far yet.
For the compression setting I have "hardware if available (otherwise none)" set for this nightly backup job. The taped drive That I am using specifies 40GB native and 80GB compressed.
I think I am exceeding the amount of data that my backup can handle.
This drive is a DLTVS80 using DLTtape IV tapes 40GB/80GB.
I have downloaded dells powervualt DLTVS80 tools and tested the drive out. It reads and writes to tape media just fine. I am finding no errors with this drive.
I tried updating veritas to the latest 8.60 revision.
I have tried cleaning the tape drive 2 different times just because.
I have hardware compression enabled in veritas on this drive. Under devices, DLT drive, properties on the configuration tab I have hardware compression enabled with the following settings
high water cound=0
What am I doing wrong here shouldn't this tape be able to handle 80gigs of data as long as its getting compressed. I thought this is where the 40GB native and 80GB compressed came into play. I should be able to back up 80GB of data as long as its getting compressed to the tape drive right? I have tried to find if this powervualt DLTVS80 drive supports hardware compresion but I have not been able to verify it yet. Maybe I have the wrong driver installed, but I doubt it.