06-14-2012 12:29 PM - edited 03-01-2019 08:54 AM
Hello,
Does any one has existing procedure/documents to move the definition from one environment to another brand-new setup envrionment. Basically here is issue we are having:
===========================================================
Issue Description
We are currently running Tidal Enterprise Scheduler on Test Environment:
Master Status - version 6.0.3.147
Plugin (tes-6.0) - version 6.0.3.151
and are ready to set up Tidal Enterprise Scheduler on Production
Environment. What is the best practice you can recommend, or do you have
any existing documents to share of how to migrate (copy) all the job/job group
definitions, trigger file definitions, and user/group information etc.
from one environment to another, or from one database to another.
===========================================================
CISCO help desk suggested Tidal Transporter, but we do not want to go that road.
I understand that I can restore my whole Test environment database for use at Production environment, all the job/action/event/user definitions will be there, but will Production Master/GUI automatically connect to this database? If so, in the new Production environment, should I only need to change the agent information, so the Tidal master will dispatch jobs at the Production agent? How to clean up old job running history and all the logs information in the database coming from the old environment?
Looking forward to your suggestions and help.
XL
06-15-2012 06:46 AM
We use Tidal Transporter for this.
Moving the Tidal database from one server to another is possible, but there is a lot of configuration in the database that would need to be changed in order for your production client to connect. Licensing, connections, etc.
Michelle
06-15-2012 08:53 AM
Hi Michelle,
Would you give more details on how to change the Licensing or Connections part of the configuration in db to allow the client to be able to connect?
Thanks.
Xian
06-15-2012 12:29 PM
Lin - There is no real simple answer to your questions that wouldn't invole Cisco or a Cisco partner to assist in performing the work. Per Michelle even once you have a production environment you will still need transporter to promote from test to prod in the future. If you would like, please feel free to shoot me an email and we can schedule a meeting to discuss your needs in more detail.
Someone might be able to explain the how too but you will be better served getting someone to assist that has the experience.
My contact info is in my profile.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide