Solved

Veritas Backup Exec 9 backup job fails during scheduled backup with "unable to attatch to one of the drives" but test completes fine

Posted on 2004-08-19
10
1,566 Views
Last Modified: 2013-12-01
I'm running 3 servers.  One is running backup exec 9 server, the other two have the remote agent installed and all are running Windows 2000 server.  The server backup exec is installed on was a domain controller.  Before yesterday all the backups ran fine.  I demoted the server because I moved Active Directory to another server.  After that all remote backups started failing with "unable to attach to one of the drives" but the data on the server itself backs up fine.  Only the remote server backup attempts cause this error.   The backup is running under the domain administrator account.  I deleted the old backup job and created a new one.  It passes the test but fails during scheduled backup with same error.  None of Veritas' suggestions on their site helped.  I’m not sure if demoting the server somehow broke backup exec, or if this is somehow a permissions problem.  I can browse all of the others servers files fine when I edit or create jobs.
0
Comment
Question by:adminjasonk
  • 4
  • 3
10 Comments
 
LVL 22

Expert Comment

by:dovidmichel
ID: 11844808
Up front let me say I have limited experience with BE but a lot with backups, so my suggestions might not fit in with the way BE works.

For the security information use an account that is local to the target system, and enter it in the format of MachineName/UserName.

Is there an acknoledgement at the client end? Some agent can be monitored at the time of the backup or have an activity log that can be checked.

When setting up the job does it connect to the agent and browse the remote system?
0
 

Author Comment

by:adminjasonk
ID: 11845189
Yes, I can browse any computer when setting up or editing a job.  I'm not 100% sure about there being client logs, though I dont see any that looked like BE made them.   One of the servers is a Domain Controller, so there is no local accounts just domain accounts and I've tried a couple different ones.  On the other server I did try local accounts also and still had no luck.
0
 
LVL 22

Expert Comment

by:dovidmichel
ID: 11845517
It was not specified so just to make sure where the names entered in the format of DomainName/UserName or MachineName/UserName?
0
Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

 
LVL 22

Expert Comment

by:dovidmichel
ID: 11845624
If there is a log it would probably be in the installation directory of the client agent.
When setting up/editing is there a way to verify that the client agent is being used and not that it is browsing via a standard network connection.
Check the activity log to see if it is connecting to the agent.
Maybe Backup Exec has some debug modes that can help.
0
 

Author Comment

by:adminjasonk
ID: 11845706
I've tried both, nothing seems to work.  I'm pretty sure its not a login issue because I can see all the files and all the mailboxes on the exchange server.
0
 
LVL 22

Accepted Solution

by:
dovidmichel earned 500 total points
ID: 11846071
Well I'm out of ideas but the Veritas support site has a bunch of things on it.
Take a look at
http://seer.support.veritas.com/docs/266177.htm
http://seer.support.veritas.com/docs/259874.htm

Most of the suggestions are along the lines of user/permissions but there is probably some details there that I'm leaving out. By the way the final error code in the message is important. So you will want to get that from the end of the message in the log.
0
 

Author Comment

by:adminjasonk
ID: 11846624
I think the new job did fix it, I was just given the wrong information.  I'll see if it runs tonight.  Thanks for the help!
0
 
LVL 3

Expert Comment

by:prav007
ID: 11901945
Did you try this simple thing ?

Just re-install remote agent on both of the servers . I have faced this problem and the remote agent re-installation seemed to fix this issue.

Best Regards,
Praveen
0

Featured Post

NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud

Question has a verified solution.

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

In this article we will learn how to backup a VMware farm using Nakivo Backup & Replication. In this tutorial we will install the software on a Windows 2012 R2 Server.
Many businesses neglect disaster recovery and treat it as an after-thought. I can tell you first hand that data will be lost, hard drives die, servers will be hacked, and careless (or malicious) employees can ruin your data.
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 …
Two types of users will appreciate AOMEI Backupper Pro: 1 - Those with PCIe drives (and haven't found cloning software that works on them). 2 - Those who want a fast clone of their boot drive (no re-boots needed) and it can clone your drive wh…

840 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