Upgrading Distributed Installation while minimizing downtime

[delawless]

I currently have a Cognos installation that involves 2 servers where cognos in a distributed directly structure (webserver, gateway, app and cm are all installed in separate directories).

While upgrading to 10.2.2, I'll be moving to a more distributed installation wherein the webserver/gateway will be installed on 2 geographically redundant servers, and the application and content manager tiers installed on separate directories across 3 different servers.

What I would like to do is turn up the Cognos 10.2.2 installation in such a way that I'll have the current installation's database copied to the new database, but I need to have all scheduled jobs disabled upon startup so that no reports are executed due to the old Cognos 10.1.1 system still being live.

Essentially I need them to exist in parallel, but with the new installation have schedules turned off until the go-live date is established.

Does anyone have a high level plan on how I can accomplish this given that I'll be using a copy of the old installation's database (and performing an upgrade on it), and schedules will start running immediately upon startup?

[sunosoft]

Hope below link will answer your query.

http://www-01.ibm.com/support/docview.wss?uid=swg21469453

[delawless]

Thanks for the link.  Very enlightening

However, one part of it did catch my eye:

From Cognos Connection Disable all the Schedules (unless you disable all the schedules before you do your import).

Is this strictly necessary?  As our configuration stands, this is not plausible, as we have both disabled and enabled report and job schedules in the system, and there are quite a few disabled ones that are required to be retained (as they are essentially saved report runs that can be executed on an as-needed basis instead of having to manually work through all the prompts each time a report is needing to be run. 

If it is necessary, is there a way to identify or batch update (from disabled to enabled) schedules in the content store?

[cognos810]

Hello delawless,
Not sure if it helps you at all, but we were in a similar situation. We had close to 300 schedules with a mix of enabled and disabled ones. Once we disable everything, there is no way to later identify the prior status of schedules as enabled or disabled. There were two options discussed, you can choose which would be best for you. We went with the first one because we had no constraint on NOT letting the enabled schedules run at all, as long as they did not send out emails.
1) Let the schedules run in the target environment, we did not have nay problem with them running as long as the schedules which sent out emails were stopped somehow. For that, in our cognos configuration we would not provide the Mail Server configuration. Result: the enabled schedules ran, but never sent out the notifications. One other variant of this could be securing the data sources and NOT give anyone execute permissions until you are ready to go-live. This would again let the enabled schedules run but would fail to complete execution.
2) Other more complicated solution is to employ SDK, and get a list of schedules(example dump it to a file) which are enabled and then disable them. Later, post deployment with slight modification of the SDK code, run it in the target environment to ONLY enable the schedules from the list that was gathered from the source environment as enabled.

Hope it helps,
-Cognos810

[sunosoft]

I believe still there is a simple way. Just disable event management service in your environment, it will not allow your schedules to execute. Once you are ready with all your work, enable the event management service your schedules will be executing fine.