Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

"Access Denied" when restoring Linux server.

Status
Not open for further replies.
Jan 9, 2003
47
US
Hi, all. I'm trying to restore a Linux server using BE9.1/sp1 and a Unix agent. Most of the restore job goes off ok. However, 1488 files were tagged as exceptions with the error "Access Denied". These 1488 files contain such important things as most of the /etc directory and a good deal of /bin and /usr/bin. Obviously, when I reboot the server it's like it's brain-dead and nothing is really working right.
I'm using "root" as my username to do the restore so it seems to me that I shouldn't be running into permission issues.
Does anyone have any insight into this?
thanks.
 
Backup Exec uses the login that the BE service runs as. That may not have permissions on the Linux box.

I don't use Linux here, but I thought I saw something on Veritas' website saying they were developing an agent for Linux. Maybe the UNIX agent doesn't work for Linux????

-SQLbill
 
I think most probably because it can't overwrite the files that are their at the moment - so giving access denied messages.

SQLBill is talking about RALUS - Remote Agent for Linux and Unix Servers - this will be released with version 10.
It will use NDMP like the windows agent does.
 
Ok. Problem solved.
1. I had the "don't overwrite newer files" option set. I somehow didn't take into consideration that this would be a big problem. ha! After I tried it again without this option I ended up with only 15 files. I was confused about the actual error messages. It listed the newer files as exceptions & I mentally connected this with "Access Denied" & there you go.
2. The 15 files that really did have Access Denied were, in fact, in use at the time. I pulled them down individually into /tmp & replaced them by hand.

The only other issue I'm having with the system now is that my ldap authentication mechanism for ssh is busted. I'm not sure why a complete restore of the system did not bring that back to life but if it turns out to be related to the backup/restore I'll post info here.
thanks for all the info, y'all.
 
Looks like you solved the problem...just a note Backup Exec is not designed to protect a linux box fully or a disaster recovery solution. Only designed to backup user data - thats in the manual If you tried to restore some crutial OS files then I can see why you linix is not working.
 
Yeah. So I've discovered. ;)

I have it all back & restored fine now. My ldap problems were not related to the backup & just happed to be coincidental to the restore.

So here's a quick recap for future generations that might need to do a full system-level restore for Linux:
1. Load the OS up using identical partitions, etc.
2. Load & start the beagent
3. Do a full system restore. Take note of files that failed to restore. Reboot.
4. Stop all the processes & daemons that you can before you do it.
5. Do a second restore of just the failed files over to /tmp & then you should be able to copy them over by hand.
6. Reboot. You should be good to go.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top