10-12-2009 05:30 AM
10-12-2009 05:35 AM
10-13-2009 02:41 AM
Hi Colin,
Thanks for getting back to me so quickly. The ADAMM is located on the same SQL server as the BE database for each of the MMS's.
I have the following entries in each of the MMS's registry:
ADAMM
Database Instance Name REG_SZ BEV
Database Server Name REG_SZ SQL-01
BEDatabase
Catalog Database Instance Name REG_SZ BKUPEXEC
Catalog Database Server Name REG_SZ <local MMS>
Server Database Instance Name REG_SZ BEV
Server Database Server Name REG_SZ SQL-01
The CASO has a folder for each MMS in <BEhome>\catalogs containing catalogs and also each individual MMS has a folder locally in <BEhome>\catalogs containing catalogs but the folders on the CASO contain far more files so I think that the local repository only holds the catalogs of locally created and ran jobs?
I would like if possible to have each individual MMS hold all catalogs for the jobs run on it irrespective of whether they were run locally or via the CASO.
Do you know whether this can be configured?
Thank you very much for your help so far
Jenni
10-13-2009 02:56 AM
10-13-2009 04:47 AM
10-13-2009 06:15 AM
Yep the presence of SSO forces certain settings on you.
Removing SSO is not that simple - unless somehow the MMS servers were not made into SSO Secondary servers as well
to find out if your MMS servers were also SSO configured, go to one of the MMS servers and run Regedit.
Look in
HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec for Windows\\Backup Exec\Server
for
SSOState
if it is not there or set to 0 it was not configured for SSO
1 = SSO Primary (your CASO will have this, the MMS serevrs should not)
2= SSO Secondary
WARNING: do not change this key using regedit unless insctuctred by Symantec - there are processes for removing SSO.
Note having SSO allows you to configure more options and can be very useful if slow links between servers are involved, however the process of removing SSO might be a lengthy one for an existing environment and you may want to actually have a proper support case open with Symantec for assistence.
Also I am actually surprised things are working well if the CASO is the SSO primary but does not have access to the library.