Share:|

Trending in Support: Connect With Control-M: Control-M Database Backup and Recovery Best Practices

 

When was the last time you backed up your Control-M database? When was the last time you tested the backup to make sure everything was working properly?

 

Learn how to schedule a backup of your Control-M database on a regular basis and how to recovery your data and keep your business operations running.

 

This is the link on YouTube for the recorded session:

 

Connect With Control-M: Control-M Database Backup and Recovery Best Practices - YouTube

 

Here is the Q&A for this webinar (Connect With Control-M: Control-M Database Backup and Recovery Best Practices)

 

________________________________________________________________

 

Q: How are you managing how/when you run hot backup and cold backup on Red Hat?  You using crontab job?

A: As mentioned in the presentation, the command line utilities for hot and cold backups may be used in Control-M job definitions to schedule them on a regular basis.

________________________________________________________________

 

Q: Can backups be restored from a setup where EM and Server are hosted on different machines to a setup where EM and Server are on the same machine? If so, how.

A: This is possible and would depend on the type of backup taken and the database configuration as it relates to the Control-M installation, whether the setup on the same machine is a One Install or separate installations on the same host. For example, if EM has its own Postgres database then it would be possible to take the database backup from one machine and restore it on another, then use the restore_host_config  utility (as of version 9.0.00.500) to make the necessary parameter changes.  The utilities that only export data may be used to restore to a different machine, but again care must be taken as host specific values are included in these backups.

________________________________________________________________

 

Q: What is the recommended time to keep older backups and archive logs?

A: This would depend on how far back in the past you would want to have a potential restore point.  The business need would dictate when an older backup is no longer critical to keep.

________________________________________________________________

 

Q: Is there a BMC utility to manage the removal of old archive files, following the execution of the next hot backup?

A: Currently no automated utility exists to manage the removal of old archive log files once a new hot backup is performed. However, a simple delete or move command may be used or create a new directory for these files.

________________________________________________________________

 

Q: Can I just use XML exports instead of backups?

A: This is dependent on your needs, keeping in mind that XML exports save only the data, for example, job definitions, calendars, etc., whereas a backup involves the entire database schema and configuration files and allows the database to be restored in the event of corruption.

________________________________________________________________

 

Q: Does ctm_backup_bcp utility back up all configuration in Control-M/Server and all job definitions?

A: The ctm_backup_bcp utility backs up all data and configuration stored within the database tables of Control-M Server, in bulk copy format.

________________________________________________________________

 

Q: How often do I need to run hot backups?

A: This would depend on the business need for a specific restore point.  Once a hot backup is run, a restore point is created and subsequent archive logs maintain the changes performed in the database from that point until the next host backup is taken. We recommend keeping an eye on the archive log directory as this will continue to grow so long as the hot backup is active. You may want to consider running a fresh hot backup weekly so that all previous archive logs from that point and before may be discarded to retrieve filesystem space.

________________________________________________________________

 

Q: We use mirroring for our Control-M server and have a script that executes the following to back up the EM backup once a night shortly after new day. Is there a benefit to using DBUHotBackup over the "em util -export -type all -type history -file $_[0]"?

A: The EM util export essentially exports the data from the EM database at a particular point in time whereas the hot backup will contain al data up until the current time.

________________________________________________________________

 

Q: Is there a way to apply a cold restore and roll forward using the logs if they were kept?

A: Unfortunately, this is not possible.

________________________________________________________________

 

Q: On Linux, if you are running the hot b/u via a script at the same timing daily, what general type of issues would cause the backup to fail? Sample error .... AP-10 - Execute Script Module: 9 - Failed to invoke command= ....

A: We would have to examine the log files to determine the cause of this particular error, however, some possibilities are that it may be due to the backup directory not being empty, or the Postgres database is not running.

________________________________________________________________

 

Q: Can you paste the backup command via a job in this panel?

A: DBUHotBackup -TRACE_LEVEL info -BACKUP_DIRECTORY /controlm/ctmsrv9/hot_bkp/full -ADMINISTRATOR_PASSWORD manager -REMOVE_UNNECESSARY_LOGS Y

________________________________________________________________

 

Q: How CPU intensive is Hot Backup?

A: This would depend on the amount of data being processed for the hot backup and archive logs, as well as the physical resources on the machine itself hosting the Control-M database.

________________________________________________________________

 

Q: I like the command em psql -c "select.....", is there a similar command for oracle and sqlplus?

A: Here is an example for Oracle:

sqlplus -s /nolog <<EOF

connect user/pass

select * from my table;

quit

EOF

________________________________________________________________

 

Q: What are the advantages of hot/cold backup compared to a bcp backup?

A: A BCP backup on Control-M Server backs up the data contained within the database. The BCP restore assumes a functioning database in order to import the data back in.  A hot or cold backup will perform a backup of the database contents and configuration files, allowing the database to be restored in the event of corruption.

________________________________________________________________

 

Q: Is there a difference in the DBUBackup commands and just using the pg_dump command with Postgres?

A: The utility pg_dump is not a database backup but rather a database export. Conversely, the DBUBackup is a backup of the database configuration and contents to allow a restore in the event of corruption.

________________________________________________________________

 

Q: What about archive log files?  The hot backup apparently doesn't delete them.

A: Currently no automated utility exists to manage the removal of old archive log files once a new hot backup is performed. However, a simple delete or move command may be used or create a new directory for these files.

________________________________________________________________

 

Q: Is the process similar for MSSQL and Oracle, or are those backups done via the MSSQL or Oracle utilities?

A: Currently the hot backup functionality within Control-M is available only for a dedicated Postgres database.  Oracle and MSSQL databases require their own native utilities for such functionality. 

________________________________________________________________

 

Q: Does the contents of these folders need to be deleted each time you perform hot backup or will it overwrite the contents?

A: As mentioned in the presentation, please ensure that the directories used for the backup and archive files cleaned before running the hot backup. 

________________________________________________________________

 

Q: Would there be any purpose in enabling archive mode if we are not using hot backups?

A: No, the archive mode is intended for hot backups.

________________________________________________________________

 

Q: Do I execute the same command for Control-M Server Hot backup?

A: The hot backup commands for Control-M Server and Enterprise Manager are very similar. 

________________________________________________________________

 

Q: Are hot backups up to the minute, or, if there is a failure, could there be recent transactions that are not in the hot backup?

A: The archive logs will retain the most current information that was dumped in the hot backup.  There is the possibility that some transactions may not be included, depending on the point of failure.

________________________________________________________________

 

Q: Can a remote directory be defined as the default location for the hot backup files?

A: So long as the directory can be accessed via a local mount point, it may be used for the hot backup files.

________________________________________________________________

 

Q: Do I execute the same command for Control-M Server Hot backup in windows environment

A: The syntax for the hot backup commands are the same in a Windows environment

________________________________________________________________

 

Q: What is the difference between a cold backup and performing exportdefjob, exportdeffolder, exportdeftable, exportdefcal, copydefcal, copydefjob, etc..?

A: A cold backup is a backup of the Control-M database and the data contained it. The export utilities contain only the data exported at that given time.

________________________________________________________________

 

Q: What is the difference between a cold backup and performing em util -S T7LDM05 -D EM7 -U em800 -export?

A: A cold backup backs up the entire EM database contents and configuration files, whereas a UTIL export merely exports the data contained within the EM database.  The util restore assumes a functioning database in order to import the data back in.

________________________________________________________________

 

Q: Does DBUHotBackup copy all the EM data? Including calendar/shout destinations/user permissions/services etc?

A: The hot backup does backup all data contained in the Control-M EM database, including folders, calendars, users, services, etc.  Please note that shout destinations are actually maintained in the Control-M Server database and would require a backup of Control-M Server.

________________________________________________________________

 

Q: Also, which logs are removed by REMOVE_UNNECESSARY_LOGS?

A: The "REMOVE_UNNECESSARY_LOGS" when set to a value of "Y" keeps the last 7 days of files in the archive directory after a successful hot backup.

________________________________________________________________

 

Q: Which back/restore utilities to use when switching from windows to Linux?

A: The answer would depend on your business needs what data you are looking to backup for a potential restore in the event of a failure.  Generally speaking the cold and hot backup commands as well as the XML utilities mentioned in the presentation may be used on either Windows or Linux installations of Control-M.

________________________________________________________________

 

Q: What are the advantages of hot/cold backup compared to a bcp backup?

A: A BCP backup on Control-M Server backs up the data contained within the database. The BCP restore assumes a functioning database in order to import the data back in.  A hot or cold backup will perform a backup of the database contents and configuration files, allowing the database to be restored in the event of corruption.   

________________________________________________________________

 

Q: Other than time constraints are there any advantages to a cold backup versus a hot backup?

A: Time and space utilization are the primary advantages of a cold versus hot backup.

________________________________________________________________

 

Q: We are using the Control-M high availability function, does BMC still recommend a backup is performed?

A: While the High Availability function in Control-M allows switching between a primary and secondary platform, a backup is still recommended for disaster recovery purposes.

________________________________________________________________

 

Q: I had to create a python script clean up archive files.  I would clean up files from date stamp of .backup file up to the new .backup file.  I am hoping your utilities mentioned do this process.  How do we get information on those? Can you demo those?

A: The "REMOVE_UNNECESSARY_LOGS" parameter when set to a value of "Y" keeps the last 7 days of files in the archive directory after a successful hot backup. For further assistance, please open a support issue and we will gladly address your concerns. 

________________________________________________________________

 

Q: How do you use these backups for DR?  Do you sync them somewhere?  Are you setting somehow the HOSTNAME related things on DR server as needed?  Any tie in with IP address with restore?

A: With the database backups and restores, system specific information is maintained.  For the purposes of disaster recovery, as of the latest fix packs, the "restore_host_config" utility was introduced to allow for changing various parameters when different hosts are involved.