Database Backups Sample Clauses
Database Backups. CUSTOMER is solely responsible for database backups. eGenuity is not responsible for any loss of data that may occur as a result of natural disaster, fire, acts of God, hardware failure or any other reason. Any restoration work needed by CUSTOMER shall be billed at an hourly rate.
Database Backups. An incremental backup of the database to a local drive will occur hourly. And a full backup will occur nightly. Both the hourly and nightly full backups will be stored offsite.
Database Backups. Web Ascender will configure automated database backups using AWS RDS backup/snapshot service, configured for “point-in-time restores” with a data retention of at least 5 days. Any major Hosting Provider has redundant pieces of hardware, software, and network equipment to prevent a catastrophic failure. However, if for some reason there is a complete or catastrophic server failure, the following steps will be taken by Web Ascender:
Database Backups. Even though the AlarmTraq database is stable, it is advised to make regular backups of your database. The database is located at: Note that the database should not be in use by AlarmTraq when you create a backup. It is recommended to make a backup of the database immediately after installation, so that you have a copy of the original database for future reference.
Database Backups. The system should have the capability to perform routine database backups to cartridge tapes or optical media using highly automated routines for incremental backups and logging of the backup files. The Contractor will be responsible for setting up efficient daily backup procedures and for training County system administration staff in its use.