Check to see if the MMC is consuming all of the CPU. If so, stop the MMC process and check the CPU again to see if there are any other processes now consuming a large amount of CPU. If the CPU drops but the usage is still high by other processes try opening the console again. The backups may begin to complete.
For a specific customer, once the MMC was stopped, a Mcafee process began using 60-90% of the CPU. Opening the console again we could see the backups starting to complete. It appears that Mcafee was causing the RMAD server to get pegged and it was unable to properly communicate with the backup agents. If there is Antivirus software running and using a large amount of CPU when the backup is running and the backup are stored locally on the RMAD server, the backups directory and RMAD logs directory should be excluded from the A/V software as it may be scanning the backups as they are getting created.