Solved

Veritas Backup Exec 9.1 - Capacity Check Status: Failed

Posted on 2006-10-30
12
3,910 Views
Last Modified: 2013-12-01
Hi

i have a client with a new windows 2003 server network - Dell PE2600, Dell DAT72 drive and Veritas Backup Exec v9.1.

The first couple of jobs ran ok as did a couple a few weeks ago.  All other jobs have failed with timeouts - says that job was cancelled due to a timeout (auto cancel is set @ 6 hours).  I've created new backup jobs and they fail as well.

All test runs fail with the message "Capacity Check Status: Failed"

SCSI ID of drive is 6 - I've found an article on Symantec's site that says to try changing ID to 2-5 but that doesn't explain why some jobs have run.

Any help would be much appreciated.

This question is very urgent - 500 points
0
Comment
Question by:cmdown
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
  • 2
  • +3
12 Comments
 
LVL 11

Assisted Solution

by:jimbecher
jimbecher earned 100 total points
ID: 17838669
What is in the job logs? Have you tried checking the volumes for errors with chkdsk?
0
 
LVL 6

Expert Comment

by:camacho_marco
ID: 17840899
Did you check if there is connectivity form the BAckup Exec server to the target Servers???
0
 
LVL 1

Expert Comment

by:MHurtares
ID: 17843415
Are the backups local or on another server?
0
Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

 
LVL 88

Assisted Solution

by:rindi
rindi earned 100 total points
ID: 17848483
Try using new backup media. Also check that you have enough space on the backup media. Have you used cleaning tapes?
0
 
LVL 55

Expert Comment

by:andyalder
ID: 17849351
Ignore the capacity check failure on the test run, it doesn't allow for compression and requires overwritable media to be present, also fails if set to a pool of devices rather than individual ones.
0
 
LVL 1

Expert Comment

by:MHurtares
ID: 17849894
If it fails while backing up remote data, try reinstalling the open-file remote agent.  This service sometimes gets stalled and starting/stopping doesn't fix it.
0
 
LVL 1

Author Comment

by:cmdown
ID: 17892376
Thank you to everyone that has replied so far.  I'l respond in order:

jimbecher: logs as per question.  yes volumes have been scanned with no errors found
camacho_marco: yes, connectiivty exists
mhurtares: backups are local to the server containing the Dell DAT72 drive unit
rindi: new tapes make no difference - i am running a clean at the moment
andyalder: this is my default setting ! ;o)

mhurtares: pls could you let me have a bit more information. can this be done without upsetting the rest of the veritas installation ?
0
 
LVL 55

Assisted Solution

by:andyalder
andyalder earned 100 total points
ID: 17892413
How mich data is there in the job?
0
 
LVL 1

Assisted Solution

by:MHurtares
MHurtares earned 100 total points
ID: 17892705
If the data you are backing up is on the backup server, the open-file remote agent is not an issue.  This remote agent is used to backup data on other servers on the network.
0
 
LVL 1

Author Comment

by:cmdown
ID: 17941686

Thank you everyone for your comments.  The problem appears to have been caused by two corruptions within Veritas.  First, it looks as if Veritas 'lost' its connection with the tape drive, even though it still showed in the Veritas device log and second the actual backup job seemed to be casuing problems.

I have (hopefully) resolved these problems as follows:

1. Force veritas to re-identify the TBU by deleting it from the device pool.  Close veritas and stop all veritas services. Restart veritas services and open Veritas - TBU should now be correctly detected.

2. Delete all backup jobs.  Close veritas.  Restart veritas, create new backup job using newly identified TBU

3. Hey presto - it works

Although I've fixed this myself, I'd like to award the points split equally between contributors to this thread.  Admin, if possible please award 100 points each to above contrbutors.  Thank you.

0
 
LVL 6

Accepted Solution

by:
camacho_marco earned 100 total points
ID: 17942684
Well done amigo glad you got it to work.

Salu2
0
 
LVL 88

Expert Comment

by:rindi
ID: 17946330
You can close and distribute the points yourself (actually you are meant to do so).
0

Featured Post

How our DevOps Teams Maximize Uptime

Our Dev teams are like yours. They’re continually cranking out code for new features/bugs fixes, testing, deploying, responding to production monitoring events and more. It’s complex. So, we thought you’d like to see what’s working for us. Read the use case whitepaper.

Question has a verified solution.

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

This article is an update and follow-up of my previous article:   Storage 101: common concepts in the IT enterprise storage This time, I expand on more frequently used storage concepts.
Microservice architecture adoption brings many advantages, but can add intricacy. Selecting the right orchestration tool is most important for business specific needs.
This video teaches viewers how to encrypt an external drive that requires a password to read and edit the drive. All tasks are done in Disk Utility. Plug in the external drive you wish to encrypt: Make sure all previous data on the drive has been …
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…

730 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