Hello everyone,
I'm wondering if anyone has detailed step by step directions to spin up CPS test environments or mirrors from Production.
We've lost the person with this knowledge and want to get it formally documented in our IT procedures manual.
Thanks!
Jeremy
Keep in mind that we are an FQHC so also have Visualutions and use Active Directory security - and the formatting is lost from our KB system:
1. Identify target license key.
2. Shutdown source DTS server
3. Shutdown source appserver
4. Place source database in single-user mode
a. SSMS>database>properties>Options>Restrict Access
5. Backup source SQL database
6. Place source database in multi-user mode
7. Start source DTS server
8. Start source appserver
9. Identify access user for target databasename
9.1 Copy emr.ini from target DTS server
10. Shutdown target DTS server
11. Shutdown target appserver
11.1. Backup table L3DTS from target database
12. In new location select target database and place in single-user mode
13. Verify all database processes are stopped using Activity Monitor
14. Restore database
a. In Options use Replace and select correct data files
15. Reset security on target database
a. Use databasename exec sp_changedbowner ‘sa’;
b. Alter database databasename set trustworthy on;
c. sp_change_users_login @Action='update_one', @UserNamePattern='cpsuser', @LoginName='cpsuser';
d. sp_change_users_login @Action='update_one', @UserNamePattern='Hermes', @LoginName='Hermes';
16. Place target database in multi-user mode
16.1 Restore table L3DTS from to database
17. Start target DTS server
18. Start target appserver
19. On appserver
a. Run Server setup>Server Configurator. Enter access user and password and click "Change Password"
b. Run Server setup>Advanced>utilities>security. Enter credentials
c. Also run setup>Advanced>licensing and enter target license key
20. On appserver verify CCC files
21. On all terminal servers run Visualutions update and copy CCC files
22. Set Visualutions license
Stephen,
Thanks for posting this. We are also an FQHC and use the CHC module so this helps.
Our next step is merging this with the Centricity install instructions to create a process for a new Test / dev server build. If anyone else has documentation, we'd love to see it.
Thanks,
Jeremy
I'm in a VMware environment so I just made a copy of my SQL and my JBOSS virtual guests and put them on their own virtual network. Then I booted them up exactly as-is, leaving the same server names, ip addresses and anything else, without it bothering my production db. Worked great. I can also take vm snapshots along the way so if I want to try again I can easily take it back to my starting point.
Steve Peterson
Director of I.T.
Circle of Life Women's Center
@jwood, I think you'll find many of the instructions different depending on your environment for example my process is significantly different than @swestfisher. However with that being said I'd be happy to do a quick call with you or someone else on your team and give them the low down of what I do for a test environment.
-Derrick
Great discussions
As the CEMR 9-10 evaluation kit version is not expected to available any time soon, apparently due to an oracle database issue, is there anyone willing to share a detailed requirements (software) and instructions to install CEMR 9-10 on a stand-alone laptop? Appreciate any advice if this is possible for a stand-alone laptop environment. meanwhile awaiting for the release of a CEMR 9-10 Evaluation kit version similar to the CEMR 9-8 for forms testing on the road and training purposes.
Jaisan
We use Veeam with Nimble Storage SAN volume snap. Allows us to create test db environment without having full footprint of the vms.
Still steps you need to worry about like turning off subscriptions (data feeds to qvera) etc.
For cemr I have servers built with same drives and copy data files, control files, etc (taking care to disable the external interactions prior to copy)
Gets more complicated every year..... Good ole days I'd just export and import, then the test system could have different drives, etc.