Figured out the Import part. The restore still has me puzzled. I have a DB job that runs and just backs up the DB file (1 tape is all that is uses - All LTO4 tapes). Works like a charm on the MMS server (where the jobs are run and kept). I then want to take the tape out to another location by hand and insert it into my BE tape drive at the location (CASO) ... I scan .. see the tape, I inventory and catalog the tape. Then I right clcik the tape and choose restore. I see the file from the previous backup at MMS location on tape. I choose the file I want,, I choose the new server to push the file to .. all is good until I launch run the job.. The job then thinks it's at the old location and asking me to insert the tape in the MMS tape drive so the restore can run. Yes, the job was run there, but I don't want to push 200gb of data over small WAN connection to other location when I can just take the tape over and restore the file to another server for safe keeping. I just can't believe that I have to go over there, run an import job, put the tape in. I have to be doing something wrong. I have tried so many differnt ways till Sunday to get this restore to work. With 12.5 it worked like a charm each and every time. Do I need catalogs to duplicate instead of replicate? I run all my jobs from my MMS and create them there with replication to CASO site. To me I shouldnt have to catalog anything at the CASO site .. it should know the tape that i put in and whats on it.
any clues? I did it again today .. Backup job ran fine over the weekend on MBES server. Took tape out to secondary site CASO server.. Imported the tape ... even inventory it and cataloged it.. Rigth clicked the tape a choose restore .. saw the back up from last night and files. Chose them to restore on different server (just a place to stick them for safe keeping) then shoose the CASO tape library (which it is in) to restore from (location) .. the jobs starts and then within 10 seconds fails with basically "Please choose "CAS Tape location for restore because this is where the tape resides" I do each and everytime. I even choose the server that was used in the backup and try the restore that way. (right clck server choose restore)... Do the jobs need to be run from the CAS server? Im stumped... help! Heres the error - f29 nor 3881 bring up anythign on this error >>> Job Log: BEX_BACK2_00939.xml
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. Final error category: Job Errors For additional information regarding this error refer to link V-79-57344-3881 |
Bump...
1) Did you inventory the tape on the CAS or just import it?
2) Did you make sure that the slot on the MBE that contained that tape either shows as empty slot or a different tape now loaded (if it stil shows the tape that you moved, then inventory that slot to correct it)?
1) I've done everything (import/inventory/catalog)
2) Technically I'm moving it from the MBE server to the CAS server for "restore". I run the job on MBE server. Take the tape out and drive it over to another location. Put the tape in the slot and (inventory/catalog) it. I then request a restore of the tape to a location (differtn server than orginial) over here at the CAS location of the files. Once the job is launched from the CAS server (restore / choose new location / choose the CAS tape library as the location to pull the restore files (tape is now in that tape library) .. The job failes with basically .. Can't run job .. please choose CAS tape library since tape in now in that library! Which I do each and every time... The two files - one shows me choosgn the DR library for the job restore .. the other shows the job failing and telling me to choose the DR library ... SGMON doesn't give me a great "error" of why its happening. I'm truly stumped. I've done this 1000's of times with BE 12.5 with ZERO problems. Fix it and I'll buy you lunch. I pay for support but they won't help becasue it's BE15. I'm stuck at BE15 until I update my Exchange servers for now.
