Here is my effort to summarize some of the activities which are often taken care by Control-M administrators. Please give your suggestions in comments so I can add more points. Thanks for reading.
Administration activities:
1. Designing Control-M installation architecture as per the environment and customer's need with respect to Control-M.
2. Control-M installation (stand alone, High availability) with different types of database (SQL, Oracle or Postgres)
3. Setting up Control-M DR(Diasaster recovery) environment
4. Creating Hot backups scripts
5. Performing database restoration as and when required.
6. Troubleshooting Control-M Enteprise Manager, Server and Agent related Issues.
7. Agent Installation/Add-on and Plugins installation.
8. Integration with LDAP/Remedy/SMTP
Control-M Admin Daily Check list
1. Check jobs in Control-M are running or not
2. Check all the components are up and running state
a. Configuration Manager
b. GUI Server
c. GCS Server
4. Self Server
5. Web Server
6. Other add-ons(SAP BO, Database, Informatica etc)
3. Check services in services console are up and running
a. From Services.msc or
b. from Cluster Administrator manager
4. Check there is sufficient space for Control-M to run properly or not. This is also called disk space monitoring. You may also create a script which can monitor the space and once space is filled more than 80% you can get one critical email alert to take immediate action.
5. Control-M Database backups are taken properly
a. Control-M Server Database Backup (Hot backup)
b. Control-M Enteprise Manager Database Backup (Hot Backup)
6. Cleanup activities
a. Make sure no jobs are in Control-M which is put on hold and not getting cleared because of being on hold.
b. Delete all the logs which are no more required.
c. Delete older logs from Control-M Server proclog and proclog.save directory
d. Delete older logs from Control-M Enteprise manager log directory.
e. Delete all the XAlerts
f. Delete runinfo history
g. Delete backups which are older than last 10 backups or as per the requirement of your client. You can also create a script to automate this job.
h. Remove older postgres database logs which are no longer required.
7. Check new day procedure logs by using ctmlog utility and see if the new day procedure completed successfully without any warning. Look for something suspicious.
8. Check Control-M Enterprise Manager's logs to see if there is any warning or failure messages which may result in an issue in near future. Take appropriate action if any suspicious warning is found.
9. Check Control-M Server's logs to see if there is any warning or failure messages which may result in any issue in near future. Take appropriate action if any suspicious warning is found.
10. Check Control-M Enteprise Manager's database logs to see if there's any warning or error messages and take necessary actions.
11. Check Control-M Server's database logs to see if there's any warning or error messages and take necessary actions.
12. Creating Users/Groups as per the requirement.
13. Installation of new Plugins and patches/fix packs as and when required. Please note that all the fix packs supplied by BMC has release notes which clearly states why the fix packs are required and it also has detailed installation steps. Please follow those instructions to install fix packs. Please take appropriate consideration before installing for example what will be the impact in your environment of installing that fix packs etc.
14. If any agent is not available then troubleshooting the issue.
15. Performing checks on Job implementation and acceptance.
16. Loading Ad-hoc jobs as per user or customer's demand.
17. Creating different types of reports(Daily execution report, Hourly execution report etc)
18. Maintaining all the other environments: Production, Non Production, Quality, Testing, Development etc.
Administration activities:
1. Designing Control-M installation architecture as per the environment and customer's need with respect to Control-M.
2. Control-M installation (stand alone, High availability) with different types of database (SQL, Oracle or Postgres)
3. Setting up Control-M DR(Diasaster recovery) environment
4. Creating Hot backups scripts
5. Performing database restoration as and when required.
6. Troubleshooting Control-M Enteprise Manager, Server and Agent related Issues.
7. Agent Installation/Add-on and Plugins installation.
8. Integration with LDAP/Remedy/SMTP
Control-M Admin Daily Check list
1. Check jobs in Control-M are running or not
2. Check all the components are up and running state
a. Configuration Manager
b. GUI Server
c. GCS Server
4. Self Server
5. Web Server
6. Other add-ons(SAP BO, Database, Informatica etc)
3. Check services in services console are up and running
a. From Services.msc or
b. from Cluster Administrator manager
4. Check there is sufficient space for Control-M to run properly or not. This is also called disk space monitoring. You may also create a script which can monitor the space and once space is filled more than 80% you can get one critical email alert to take immediate action.
5. Control-M Database backups are taken properly
a. Control-M Server Database Backup (Hot backup)
b. Control-M Enteprise Manager Database Backup (Hot Backup)
6. Cleanup activities
a. Make sure no jobs are in Control-M which is put on hold and not getting cleared because of being on hold.
b. Delete all the logs which are no more required.
c. Delete older logs from Control-M Server proclog and proclog.save directory
d. Delete older logs from Control-M Enteprise manager log directory.
e. Delete all the XAlerts
f. Delete runinfo history
g. Delete backups which are older than last 10 backups or as per the requirement of your client. You can also create a script to automate this job.
h. Remove older postgres database logs which are no longer required.
7. Check new day procedure logs by using ctmlog utility and see if the new day procedure completed successfully without any warning. Look for something suspicious.
8. Check Control-M Enterprise Manager's logs to see if there is any warning or failure messages which may result in an issue in near future. Take appropriate action if any suspicious warning is found.
9. Check Control-M Server's logs to see if there is any warning or failure messages which may result in any issue in near future. Take appropriate action if any suspicious warning is found.
10. Check Control-M Enteprise Manager's database logs to see if there's any warning or error messages and take necessary actions.
11. Check Control-M Server's database logs to see if there's any warning or error messages and take necessary actions.
12. Creating Users/Groups as per the requirement.
13. Installation of new Plugins and patches/fix packs as and when required. Please note that all the fix packs supplied by BMC has release notes which clearly states why the fix packs are required and it also has detailed installation steps. Please follow those instructions to install fix packs. Please take appropriate consideration before installing for example what will be the impact in your environment of installing that fix packs etc.
14. If any agent is not available then troubleshooting the issue.
15. Performing checks on Job implementation and acceptance.
16. Loading Ad-hoc jobs as per user or customer's demand.
17. Creating different types of reports(Daily execution report, Hourly execution report etc)
18. Maintaining all the other environments: Production, Non Production, Quality, Testing, Development etc.
No comments:
Post a Comment