MMS Server priority in CASO environment

I think you created the job on the CAS.  You can either copy the job to the MMS or create the job on the MMS.  This will ensure that the job runs on the MMS.  See page 1029 in the BE 2012 Admin Guide.

Hi,

What do you want your CASO to do? Delegate jobs to the MMS, or just report on it basically? If you want it to delegate then the catalogs need to be centralised on the CASO. If you want it to simply report on the MMS, then you localise on the MMS.

Read below on catalog location in a CASO/MMS environment.

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

Thanks!

Hi, 

Thanks for your suggestions. The problem is that we basically want the two servers to work in tandem:

We need the MMS in the server room to take the backup, to it's local iscsi drive (it could do the copy to the CASO drive aswell, if needed). Then we want the CASO to copy that backup first to the CASO's local iscsi drive and then to the tape.

We have been unable to share the tape drive in the CASO/MMS setup, so having the job copied to the MMS causes the MMS to stop working when it tries to duplicate the tape, as it has no tape drive to duplicate to.

We need the backups on tape on our Major site as a 80 km trip every day to change tapes in the server room, is not a good plan.

Hi,

Then it seems like your setup is incorrect. It should be as follows:

1. CASO delegates job to the MMS. MMS backs up to iSCS drive attached locally.

2. Stage put in place on the CASO that duplicate those backups from the MMS to the CASO. You need a drive attached (locally/DAS/SAN) to the CASO.

3. Stage put in place on the CASO to duplicate the backups from the local B2D that the MMS duplicated too, to tape.

This is an optimal setup, Disk is pretty cheap now, and you can use a NAS, or even internal disk in the CASO for this.

Doing what you are doing as it stands means backups are going to take a long time. I am under correction, but if you can't share a locally attached tape drive/autoloader/library to a remote server if it isn't SAN-attached.

Thanks!

Hi Craig,

Thanks for you assistance. Can you please describe how I would create the job, so the backup part is deligated to the MMS. Below you can find a screen shot of the backup properties of one of our servers.

In the storage pool names BES01 is the MMS and BES02 is the CASO, meaning pools with BES01 in the name is physically connected to the MMS. The disks on MMS is shared with the CASO, so it can access the data for copying.

I'm thinking it's got something to do with the below setting... The problem is that it seems to be global for the entire job. Meaning if I force it to the MMS, it again cannot do the 2 past parts of the backup job (duplicate to major site and duplicate to tape.)

You assistance is greatly appreciated! 

...can't quite see that image, but your flow i as follows:

1. Backup to B2D on MMS;

2. Add in a stage to duplicate to B2D on CASO;

3. Add in a stage to duplicate to tape on CASO once #2 completes.

hanks!

When I create the jobs, I'm doing it on the CASO.

1. New B2D job, I specify the MMS storage pool as target.
2. I then add a stage to D2D , specify CASO storage pool as target
3. Then I add the D2T stage, and specify the tape drive as destination.

How do I FORCE 1 to run on the MMS. For some reason the CASO seems to take the B2D job for itself.

...you're saying that the initial B2D job runs across your WAN to the CASO instead of locally on the MMS?

How are your catalogs located?

Thanks!

The catalogs are located on the CASO (Centralized)

...what happens if you specifically select the MMS in the initial jobs, and then the CASO in the duplicate jobs?

Thanks!