Symantec backup exec 2010 r3 end of life

#SYMANTEC BACKUP EXEC 2010 R3 END OF LIFE FULL#

Saturday morning I discovered I had received repeated emails, from BENT, asking me to remove the media. This puts the tape, as you probably already know, into the scratch media pool. For this I simply put the new tape in the drive and ran a label job on it. LastР’В Friday I inserted a brand new tape intoР’В the backupР’В rotation. Single HP Ultrium 3 internal SAS tape drive. I'm having a similar problem with Backup Exec. Shortening them might fix the problem with a job running onto a new tape when I'm in early to change a tape but doesn't address the auto eject on fail or cancel.Р”Р„s for capacity the LTO tape is plenty big enough right now. There are already time limits on the jobs but they do spill over into the next working day. Now I have to go back to the remote site to put the tape back in!

Fail the job by all means, but don't eject the tape. I created the job and forgot to tell it to use the LTO tape media set so BE decided to fail the job as the correct media wasn't available and then eject the tape. This happened today when trying to backup a database using a newly created job (again, I didn't check the 'eject media when complete' check-box). At no point have I told BE that I want it to eject the tape. When the running job stops, the tape ejects.

#SYMANTEC BACKUP EXEC 2010 R3 END OF LIFE FULL#

If a job is running I want to stop it so I can put the tape in the correct media set and start a full backup (After the full backup I can leave it so the scheduled backups jobs do their work). I then log in remotely to rename the tape. Where things get annoying/interesting is when I put in a new blank tape. I would expect the tape to eject when it is full.

Symantec backup exec 2010 r3 end of life