The StorCycle solution requires daily database backups configured and scheduled before any migrate / store jobs can run.
IMPORTANT |
If something happens to the StorCycle database and you do not have a backup, you will lose information about what files are migrated and where they are located. |
IMPORTANT |
Database backups are specific to each operating system. Database backups and the Database Archive and Restore actions cannot be used to migrate the database across operating system server platforms. For example, you cannot restore a database to a Windows system if it was originally created by a Linux system, and vice versa. |
The Jobs pane of the main dashboard (see Figure 114) provides the date and time for the last successful Database Backup. The background color for the Database Backup status indicates the age of the last successful backup:
• | White — Less than one day old. |
• | Yellow — One to seven days old. |
• | Red — Greater than seven days old. |
Note: | The StorCycle solution displays a red banner message on the user interface to remind administrators if a daily database did not run in the last 24 hours. |
The StorCycle solution requires additional database protection for any migrate / store job that removes or replaces original source files. The StorCycle solution requires the completion of two successful database backups before the removal or replacement occurs.
Use the instructions below to configure a database backup.
Note: | It is recommended to check the backup directory after creating your first database backup to verify the backup completed as expected. |
1. | Click Settings ![]() |
|
2. | Click Schedule New Database Backup. |