I wanto to create two separate instances of BO services running, to support failover situations. The goal is to set the second instance to use its own CMS Database and File Repository.
A plan to achieve this is to copy both DB and FR from the first to the second machine periodically.
In order to to that i create a cluster copying db source from a first instance. Then physical copy of file repository is made. Till now everything works fine.
But when i physically copy CMS DB and FR Data the second instance is not able to respond in a right manner (after log on, it starts to process
something without end).
Is it possible to achive this in a way i’ve planned it. And if yes what should i consider to resolve this issue.
I have a 11 step admin task list that I created from one of the XI guides last year.
It was the vendor’s recommended approach for copying the CMS - and it was more complex than just taking a database snapshot
Not sure if this has changed since then, but it makes sense as the CMS also stores server configuration settings etc
I can’t post the list - probable copywrite violation - and don’t have the time to search - but look through the guides or ‘ahem’ contact me …
The ‘Profile’ setting for your BOBJ nic, is wonderfull for adding personal details such as your mail address i.e. that little email icon below my signature - with my email address - is from those settings …
I would send you info as to which guide and page number - but I’m a tad swamped in playing catchup to try and locate the originals so I have it in an admin spreadsheet …