Emergency Database Recovery
Restore and recovery are the first steps to getting back on your feet in an unplanned outage. But sometimes there is no place to restore backups because of hardware failure; sometimes backup integrity is questionable; sometimes the backups were performed improperly.
Blue Gecko can quickly assess the possibility of restore and recovery in almost any disaster. Our DBAs will quickly assess the situation, provide meaningful feedback about the state of your database and data, and will any perform any recommended restore and recovery steps if required. though it is not always possible to perform a complete restore or recovery, our goal in an emergency recovery situation is to get your database back up and running again with as little data loss as possible.
Oracle Database Restore and Recovery
Some common Oracle restore and recovery activities:
- Evaluate the integrity of RMAN backup pieces
- Repair corrupt data blocks
- Fail over to standby databases
- Restore databases from tablespace or RMAN backups
- Repair corrupt file system or disk partitions
- Extract data from corrupt database files and unusable databases
- Fix broken media interfaces (e.g. Vertitas, Commvault)
- Perform standard point-in-time, tablespace, or object recoveries
MySQL Restore and Recovery
Some common MySQL restore and recovery activities:
- Create new databases from MySQL dumps
- Restore databases from MySQL dumps
- Restore and recover hot InnoDB backups
- Fail over to standby databases
- Repair corrupt datafiles
- Repair corrupt file system or disk partitions
- Extract transactions from the MySQL binary log to reverse destructive SQL
