8e6 Technologies 3 - Manual (Page 43)

8 E 6 T ECHNOLOGIES , E NTERPRISE R EPORTER 3.0 U SER ’ S G UIDE
43
A
DMINISTRATOR
S
ECTION
: C
HAPTER
2 - C
ONFIGURING THE
ER 3.0 S
ERVER
Some scenarios and action plans to consider include the
following:
• The ER 3.0 database becomes corrupted - Correct the
root problem. Restore the database from the most recent
ER 3.0 backup, and reprocess raw logs up to the current
date and time.
• The data drive fails - Replace the data drive. Restore the
database from the ER 3.0 backup drive, and reprocess raw
logs up to the current date and time.
• The backup drive fails - Replace the backup drive, and
perform a manual backup.
• Both data and backup drives are damaged - Restore the
database from the most recent remote backup, and repro-
cess raw logs up to the current date and time.
As you can see, it is critical that raw logs are available to
bridge the gap between the last database backup and the
present time, and more frequent backups (local and remote)
result in less “catch-up” time required for reprocessing raw
logs.
Set up/Edit External Backup FTP Password
In order to back up the ER 3.0 Server’s database to a remote
server, an FTP account must be established for the remote
server.
NOTE: In the External Backup FTP Account frame, the login
name that will be used to access the remote server displays in the
Username field. This field cannot be edited.
1. In the Password field, enter up to eight characters for the
password. The entry in this field is alphanumeric and case
sensitive. For security purposes, an asterisk displays for
each character entered.