Skip to main content

Database Recovery Strategies


Be it a natural disaster striking your primary data center and obliterating all your databases or some technical error that brings it down, forcing you to consider moving your database to your backup DR (disaster recovery) location, the right disaster recovery strategy would definitely save the day.

Tejas Jain - Database

How do we accomplish this?

Well, there are primarily three strategies, you can considering, depending upon your downtime tolerance level:

  • Electronic Vaulting
  • Remote Journaling
  • Remote Mirroring

Let us see what each one of them has in store for us:

Electronic Vaulting

  • These are essentially bulk transfers wherein the database backups are moved from the primary site to the remote (backup / DR) site via network
  • There is a significant delay between the time you declare a disaster and the time to recover your database backups
  • Entire Backup files are transferred
  • Not suited for hot sites where the recovery should be instantaneous

Remote Journaling

  • These are much more frequent and faster than Electronic Vaulting
  • Though these are bulk transfers as well, they are usually carried out every hour or sometimes more frequently
  • Entire backup files are not transferred every single time.. Rather, only the differential backup (i.e. the transaction logs which were generated due to live transactions post previous full backup) are transferred, making this mechanism quite fast.
  • Since the live transaction logs are not synced, there is still human intervention required to bring up the database at the backup location
  • Usually more expensive than Electronic Vaulting due to higher frequency

Remote Mirroring

  • The word "mirroring" should explain that this is the "real-time" replication
  • There is a live database server at the backup / DR location which continuously syncs up with the primary database such that should your original database goes down the backup database is fully ready to immediately take over
  • Most expensive as the underlying infrastructure, processing overhead and the personnel costs are significant





Comments

Popular posts from this blog

Checkpoint - Exporting Objects in CSV format

Be it a Network Operations Manager, Security Architect or a Security Auditor, the people up the hierarchy always harangue the Security Engineers to compile the list of firewall objects or rules or policies or the traffic statistics and so on.. This can turn out to be quite hectic especially if there are no built in features to systematically provide the output in a "layman-readable" format. Come, Checkpoint's "Object Explorer..."  which not only provides the output in the "layman-readable" format, but also provides in-built filtering mechanisms, thereby ensuring that the Security Engineer doesn't have to rely on Google for building his scarce Microsoft Excel data filtering skills. The following screenshots will show how easy it is, with Checkpoint R80.10 to generate the firewall configuration inventory. On the SmartConsole Unified Portal, navigate to Menu >> Open Object Explorer... Select the Categories you wish to see in your output: Click o

MITRE ATT&CK - Kerberos Vulnerabilities and Security

From the previous post, the summary of Kerberos authentication process is as below: For the initial authentication, the user’s client machine sends a request to the KDC  Authentication Service (AS) . The request includes details like the user’s username, and the date and time. All information except the username is encrypted using the hash of the user’s password. The KDC AS uses the username to look up its copy of the user’s password hash and uses it to decrypt the rest of the request. If the decryption is successful, that means the client used the correct password hash and the user has successfully authenticated. Once the user is authenticated, the KDC AS sends the user’s client a  ticket granting ticket   (TGT) . The TGT includes a unique session key and a timestamp that specifies how long that session is valid (normally 8 or 10 hours). Importantly, before sending the TGT, the KDC encrypts it using the password hash for a special account, the  KRBTGT account.  That password hash is s

AWS Workspaces - Unhide C drive

AWS Workspaces Windows 10 has C:\ drive hidden by default.. To unhide it, locate the following directory in Windows Registry (regedit), HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\ Explorer Dword Value - NoDrives. By default it is set to Hexidecimal value of 4.. Change it to Hexidecimal value of 0 Restart the Workspace and C:\ drive should be visible.