Disaster Recovery Flashcards
What is Disaster Recovery?
The Disaster Recovery feature is a way to quickly recover and reinstall your ePO software back to its pre disaster state
What two pieces of data make your ePO environment unique?
the McAfee ePO database, and sections of the ePO server file system(like the extensions that you checked in, and the configuration files that control ePO)
Having an ePO database backup containing a valid Disaster Recovery Snapshot allows you to do perform which 3 scenarios?
- Restore McAfee ePO to your current ePO server, which allows you to recover from (example) a failed ePO software upgrade
- ePO to new server hardware with the original server name and IP address. For example, in the case of catastrophic hardware failure
- McAfee ePO server hardware with a new server name, which allows you to move your ePO server from one domain to another
Of what relevance is the Keystore Encryption Passphrase that’s configured during install to the Disaster Recovery Process?
The files that are stored in the Disaster Recovery Snapshot are encrypted using the Keystore Encryption Passphrase.
T/F McAfee can recover the Keystore Encryption Passphrase if you forget it
False, if you forget it then its gone
What are the two pieces that you need in order to perform a successful Disaster Recovery? Also, how do these two pieces work with one another?
You need a backup of the ePO SQL Database, and a Disaster Recovery Snapshot. The Disaster Recovery Snapshot is stored inside of the ePO SQL Database backup
What does it mean for the Disaster Recovery Snapshot to be out of sync?
This means that there has been a change to the ePO server configuration (such as checking in a new extension) since the most recent snapshot was taken.
What happens if you take a backup of the ePO database with an out of sync Disaster Recovery Snapshot?
If the database and the snapshot are out of sync as in the scenario described, then it is unlikely that you will be able to successfully restore from that database.
How can you quickly see whether or not the disaster recovery snapshot is up to date?
Through the Disaster Recovery Snapshot Dashboard
What is an important consideration to be made in regards to the scheduling of both the ePO database backup and the Disaster Recovery snapshot?
Since the Disaster Recovery Snapshot is stored within the ePO database, the database backup should be scheduled after the Disaster Recovery Snapshot server task completes. Since the time that it takes the snapshot to complete can vary, it is a good idea to implement a buffer period between the expected end of the snapshot and the beginning of the database backup
Are Registered Executables stored within your disaster recovery snapshot?
The snapshot stores the file paths for your registered executables, but doesn’t restore the files themselves, so they will have to be replaced when you restore your ePO environment. (post-restoration, any registered executables with broken paths appear in red on the Registered Executables page)
What is the default time that they Disaster Recovery Snapshot Server task is configured to run?
Daily at 2 am
T/F The Disaster Recovery Snapshot Server task is always enabled by default once ePO is installed?
False, It’s only enabled if the database i hosted on a full version of SQL Server. It’s disabled by default if the database is hosted on a SQL Express instance due to the hard-coded database size limit enforced by SQL express
T/F There can be multiple snapshots saved at any given time?
False, each time the Disaster Recovery Snapshot Server task is run, the current snapshot information is removed and the new snapshot information takes its place
On the Server Snapshot dashboard monitor, what does the “See details of last run” option do?
Displays the Server Task Log entry for the last snapshot task, showing information and log messages about the most recent snapshot saved.
