be 2014

4 Topics

Final error: 0xe0000f29 - Restore job does not see tape in library for restore job
So I've moved my tapes from my management BE server to the CAS server for a restore off site. I insert the tapes .. scan / inventory. Right click and look at details of the tape and all looks good .. data is was what was backed up at other location and now show in tape library 2 (CAS tape library) all is great... Now when I go run the restore it fails with: Completed status: Failed Final error: 0xe0000f29 - This Backup Exec server cannot access the device selected in the settings for the job. Refer to the job log for details The media required by this job is located on device 'Robotic library 5'. Select device 'Robotic library 5' in the job settings. Well I am doing this... this is the CAS tape library name and it even shows me in the details the tape is located in Library 2. I'm stumped. I've rebooted / stop/start a;; services each location .. made sure I can get to each BE server from each other. Is it my catalogs? can I restart them from scratch? Im just not sure what is causing this to happen.
downsouth
2 years ago Place Backup Exec
987Views
0likes
3Comments
Upgrade from Backup Exec 2012 to 2014 AFTER upgrade to W2012R2
Hi. I upgraded W2008R2 to W2012R2 because of MS end of support without realizing that my installed BE 2012 was not compatible with W2012R2. So now BE2012 won't launch. I have the install media and a license for BE2014. Can I do an install and have it upgrade the existing BE2012 version? If so, is it a straight forward upgrade, and if not what is the best way to install BE2014 and apply my old settings (catalogs, job history, tape drive drivers, etc.)? Thanks
kevsean
6 years ago Place Backup Exec
1.6KViews
0likes
3Comments
Exchange 2013 database restore successful - but database not mountable / dirty shutdown
Hi, Currently testing disaster recovery of an exchange 2013 server with Backup Exec 2014. Backup job taken successfully with BE Windows Agent. Successfully restored the server into a VM using SDR. Afterwards restored Exchange database and logfiles to original location. Instructed BE to overwrite existing. The Exchange restore job is successful - but store is not mounted automatically. Manual mount not possible - getting dirty shutdown error code. Have tried soft repair with eseutil - but it fails and reports that some logfiles are missing. Only option that works is hard repair - but my logfiles should be OK.. 1. Circular logging is disbled on the production server 2. No other backup software in used for Exchange backup - that could possibly interfere with the logfiles /flush them. 3. Log files are flushed correctly after each full backup job What am I missing here? We run full backup job each friday and differential other days. Differentials are logfiles only (logfiles not deleted until after successful full backup) Could there be an inconsistency in my Exchange database that could cause the replaying of log files to fails - or am I just doing the restore wrong? Regards Thomas
Solved
Thomas_Buhr_Hau
8 years ago Place Backup Exec
1.8KViews
0likes
4Comments
Error E000E020 on Backup Exec 2014.
Hello all, I would like to make a question regarding error E000E020, the error message I've been having in a remote site is: "e000e020 - The duration that this job is allowed to remain scheduled has passed. It will be rescheduled. Verify that storage is available and check the job's schedule settings. Ensure that there is enough time for it to begin running before it is considered missed." I've already checked the following article, and I think I can discard options A and C, as I don't think the options for option A is on Backup Exec 2014 (or maybe I am not finding them properly) and C we didn't have a time change here (therefor, there was no time change). So checking option B and normally we run the jobs as the following: Backup to Disk and then Duplicate to Tape. The disk we use for backup has a lot of free space left, as for the tape I wouldn't be surprised if it is not being change daily as it is a remote site where we don't have a lot of control (but then the error would only be on the duplicate job, not on the 1st backup). However the issue happens on the Backup job, where though I will attach some screenshots to see if it helps, I find odd the Job is set to start 9:00:00 PM, so it sometimes starts at 9:00:07 and it has end date of 9:00:04 (!?).
Solved
gabriel_abib
8 years ago Place Backup Exec
7KViews
0likes
3Comments