CTM/Enterprise Manager - ensure availability?
CTM/Enterprise Manager - ensure availability?
Everybody here knows about CONTROL-M Server's methods for ensuring availability. Hot and Cold backups, mirroring, fail-over...
But what about CONTROL-M/Enterprise Manager availability? What is the best practice for doing it? Provide 2 different machines with different hostnames, but with the same database (for example) and export/import data between them?
Or provide 2, exactly the same machines, but the other machines is in "sleep mode", with everyday export database on different location somewhere on the SAN/LAN? In case of CTM/EM fail on first machine, start second machine and import data?
We can use cluster, but in this case, this is not the option.
What methods you use in your environment?
But what about CONTROL-M/Enterprise Manager availability? What is the best practice for doing it? Provide 2 different machines with different hostnames, but with the same database (for example) and export/import data between them?
Or provide 2, exactly the same machines, but the other machines is in "sleep mode", with everyday export database on different location somewhere on the SAN/LAN? In case of CTM/EM fail on first machine, start second machine and import data?
We can use cluster, but in this case, this is not the option.
What methods you use in your environment?
For Control-M/EM version 6.1.03.400
- We made the same instalation on 2 servers.
- We use the same Oracle data base (located on the SAN)
- We use one server in mode "online", one server in mode "stand-by")
- Alias name is defined in DNS to identified the active server.
- "rdist" command is schedule by the crontab to synchronize "on-line" and "stand-by" server for wich files you want to replicate (example: Defaults.rsc, scripts,logs,....)
- In case of switch to the alternate server, just change IP adress and hostname in DNS, start Control-M/EM components (root_menu) and adjust active parameters in "Admin Facility" to reflect the new server.
It's work without problems during our DRP tests.
Regards
Walty
- We made the same instalation on 2 servers.
- We use the same Oracle data base (located on the SAN)
- We use one server in mode "online", one server in mode "stand-by")
- Alias name is defined in DNS to identified the active server.
- "rdist" command is schedule by the crontab to synchronize "on-line" and "stand-by" server for wich files you want to replicate (example: Defaults.rsc, scripts,logs,....)
- In case of switch to the alternate server, just change IP adress and hostname in DNS, start Control-M/EM components (root_menu) and adjust active parameters in "Admin Facility" to reflect the new server.
It's work without problems during our DRP tests.
Regards
Walty
I have in some case configuration with two servers, two hostnames and different IP and also two DB with export/mirroring data.
The solution with only one DB is a good solution that I think now to applicate. Thanks Walty
The solution with only one DB is a good solution that I think now to applicate. Thanks Walty
Last edited by mauriziog on 16 Jul 2008 12:06, edited 3 times in total.
- philmalmaison
- Nouveau
- Posts: 1148
- Joined: 08 Jun 2007 12:00
- Location: Ile de France
don't you have so much datacenter(s) to manage in one EM.
i'm working with 43 DC(s) in one EM, and it's important too to sychronize the online and sleeping one.
The most easier is to do an ecs util export type all, + export the modified tables, and then import all without net and def every 15 minutes for the controlm tables
so ecs util + export
select DATA_CENTER,SCHED_TABLE from DEF_TABLES
where
MODIFIED="1"
order by DATA_CENTER
go
and to record CONFREG on sleeping with the right machine name.
as following :
echo "UPDATE CONFREG set PROCESS_COMMAND=\"ecs gasrv -name ${Com_Name}\"" >> ${Working_Dir}/tmp.$$
echo "where" >> ${Working_Dir}/tmp.$$
echo "PROCESS_COMMAND like \"ecs gas%\"" >> ${Working_Dir}/tmp.$$
echo "go" >> ${Working_Dir}/tmp.$$
#echo "UPDATE CONFREG set PROCESS_NAME=\"${Com_Name}\" where PROCESS_TYPE=2" >> ${Working_Dir}/tmp.$$
#echo "go" >> ${Working_Dir}/tmp.$$
echo "UPDATE CONFREG set PROCESS_NAME=\"${Com_Name}\" where PROCESS_TYPE=3" >> ${Working_Dir}/tmp.$$
echo "go" >> ${Working_Dir}/tmp.$$
echo "UPDATE CONFREG set MACHINE_NAME=\"`uname -n`\"" >> ${Working_Dir}/tmp.$$
echo "go" >> ${Working_Dir}/tmp.$$
echo "UPDATE CONFREG set CURRENT_STATE=0" >> ${Working_Dir}/tmp.$$
echo "go" >> ${Working_Dir}/tmp.$$
echo "UPDATE CONFREG set DESIRED_STATE=0" >> ${Working_Dir}/tmp.$$
echo "go" >> ${Working_Dir}/tmp.$$
isql -U${User} -P${Pswd} -i ${Working_Dir}/tmp.$$
regards
philmalmaison
regards
philmalmaison
i'm working with 43 DC(s) in one EM, and it's important too to sychronize the online and sleeping one.
The most easier is to do an ecs util export type all, + export the modified tables, and then import all without net and def every 15 minutes for the controlm tables
so ecs util + export
select DATA_CENTER,SCHED_TABLE from DEF_TABLES
where
MODIFIED="1"
order by DATA_CENTER
go
and to record CONFREG on sleeping with the right machine name.
as following :
echo "UPDATE CONFREG set PROCESS_COMMAND=\"ecs gasrv -name ${Com_Name}\"" >> ${Working_Dir}/tmp.$$
echo "where" >> ${Working_Dir}/tmp.$$
echo "PROCESS_COMMAND like \"ecs gas%\"" >> ${Working_Dir}/tmp.$$
echo "go" >> ${Working_Dir}/tmp.$$
#echo "UPDATE CONFREG set PROCESS_NAME=\"${Com_Name}\" where PROCESS_TYPE=2" >> ${Working_Dir}/tmp.$$
#echo "go" >> ${Working_Dir}/tmp.$$
echo "UPDATE CONFREG set PROCESS_NAME=\"${Com_Name}\" where PROCESS_TYPE=3" >> ${Working_Dir}/tmp.$$
echo "go" >> ${Working_Dir}/tmp.$$
echo "UPDATE CONFREG set MACHINE_NAME=\"`uname -n`\"" >> ${Working_Dir}/tmp.$$
echo "go" >> ${Working_Dir}/tmp.$$
echo "UPDATE CONFREG set CURRENT_STATE=0" >> ${Working_Dir}/tmp.$$
echo "go" >> ${Working_Dir}/tmp.$$
echo "UPDATE CONFREG set DESIRED_STATE=0" >> ${Working_Dir}/tmp.$$
echo "go" >> ${Working_Dir}/tmp.$$
isql -U${User} -P${Pswd} -i ${Working_Dir}/tmp.$$
regards
philmalmaison
regards
philmalmaison