Forum Discussion

Chrissy_Ginther's avatar
15 years ago
Solved

CASO Database Question

Hello,

 

We have a CASO server with a single MMS.  The database is centralized on the CASO and the catalogs are replicated.  I made a change to the database on the MMS, specifically change the length of time job histories are kept.  I then looked at the CASO expecting for the changes to have propagated to the CASO but they were not.  Should I be able to change the options on any server since it is a single DB hosting on the CASO?

  • ..that change has obviously not made any difference. With a centralised DB, you'd make those changes on the CASO server instead. The reason for you being able to make that change on your MMS is weird given the way you have set up your CASO environment.

    Can you verify that the DB is centralised?

  • HI there,

     

     

     

    The options you can set for each MMS being managed by a CAS include:
     
    • Time thresholds for handling unresponsive managed media servers
    • Time between job status updates
    • Time drift alerts
    • Catalog storage location
    • Job log and history options
     
    Global options set using this procedure only affect newly installed MMSs
     
     
    Media servers already managed by a CAS do not automatically inherit the global MMS default
    settings you establish.
  • ..that change has obviously not made any difference. With a centralised DB, you'd make those changes on the CASO server instead. The reason for you being able to make that change on your MMS is weird given the way you have set up your CASO environment.

    Can you verify that the DB is centralised?

  • Confirmed with support that you need to make the change on the CASO.  It is weird though.