Backup Exec 2012 - Media remove autoresponse not possible

I guess the only way to backup multiple servers with various selections is to define one job pr. server. I must say - I think its a bad approach on how to backup multiple servers. And the overview is gone in the new version. (thinking about downgrading to 2010).

You can use groups to backup multiple servers. 

Refer to 

http://www.symantec.com/docs/HOWTO73364

http://www.symantec.com/docs/HOWTO74306

I haven't looked into this yet but I believe a Group is just an administrative container and that separate job definitions per server will still be created within the group. 

Kiran is partially right. You can create a backupjob by using groups, but only so far as the selections is identical (complete servers).

I found that described ind the administrators manual.

Tom

OK I have now looked into this

If you create a Group and then create the job from the group during the creation of the job definition the selections are identical. When you click OK to save the definition it actually states the Jobs (plural) are being created. If you then Click the Arrow Button called Group <Group Name> (on right side below ribbon bar) to look within the Group itself and then look at the Jobs list you have 2 separate job definitions  that are scheduled to start at the same time.

And then if you edit each job definition you can then customize what is selected for backup.

As such you still don't end up with a job containing multiple servers.

You CAN configure an auto-response for the media remove alert in BE 2012. Click on the BE button and then select alert categories. See screenshot below

Then select the media remove alert.  The auto-response is not greyed out.

Hello PKH

Actually if You look closer, the autoresponse I´m talking about is just beneath the filed you have marked in the red circle. I´ts called "Respond with" and is grayed out. Also in Your screendump.

If You navigate so the same place on the alert for Media Insert/Media overwrite - You can se what I mean.

Tom

Hi Colin

Thanks for the input. I have also come that far.

But my problem is about the schedule and how the media is handled.

Lets say I backup up two servers to tape which I configured as a group.

How does the two jobs (which are set to the same runtime) handle owerwrite/append/eject ?

Lets say the first server is backed up and the setting is overwrite - what about the next server ? - Will this overwrite again (and erase the backup of the first server) - should I edit the settings so that the first server backup is set to overwrite and the next to append ? - and what about the start times - do I have to make them indivudually as well to make sure I get the servers backed up in the right order ?

If I have to make all these indivual settings afterwards - what the point in using groups ?

It has been sometime since I used a stand-alone tape drive.  When you respond with a clear, wouldn't it clear the alert and stop the job?  The portion that is greyed out is for configuring a cancel which probably is not valid in this case.  All the alert needs is an acknowledgement.  It does not matter whether the O.K. or the Cancel button is clicked.

For BE 2010, the "response with" is also greyed out.

I´m sure the "clear after x time" only clears the popup on the screen. But the alert is still active in the background.

I already tried this the first time the job waited for the respons. But the next day it was the same. I still had to open the active alert and click ok before the job ended.

But I found another solution - which is not so optimal as just setting the checkmark in the job.

But you can shedule a seperate eject job - which unfortunattely has some drawbacks.

For instance if I have multiple jobs configured (as described in other posts in this string, with multiple servers in separat jobs because of overwrite/append problem) - how can I be sure not to eject the tape between jobs ? (datasize will increase over time - and therefore also the backuptime.)

Can I be sure that the jobs will run in scheduled order no matter what ? (No - not If I get the automatic cancel af x time) configured in the wrong way and the second job somehow gets cancel before it has run.)

I still think these options is a step back compared to earlier versions. It might be a matter of habits that I need to change myself. I hope someone can convince me that the last applies...

Solution