The system backs up index action logs and index databases so that the active index can be recreated if it becomes corrupted or is unintentionally deleted. (The active index is recreated by playing backed up action logs to a backed up index.)
Note
User-created schedules or schedule policies (if any) will not launch backups for index servers. Only the "System Created for Index Backups" schedule policy is able to launch backups for index servers.
Action Log Backup
The system backs up action logs to the same storage library used for the data backup. A series of cleanup rules determines how these action log backups are retained and deleted.
Index Database Backup
The system backs up the index database based on backupset level indexing or subclient level indexing. A series of cleanup rules determines how these index backups are retained and deleted.
Within 24 hours after running the first backup using a storage policy, the system creates an index backup pseudoclient for the storage policy, and then backs up the associated index database to the pseudoclient.
Note
-
The system names the pseudoclient based on the storage policy name, with an appended suffix of _IndexServer. For example, if a storage policy is named SP1, the pseudoclient's name will be SP1_IndexServer.
-
You can find the pseudoclient in the CommCell Console in Client Computer Groups > Index Servers.
-
The pseudoclient backs up the index database according to its associated storage policy's backup schedule and backup criteria. To modify an index backup schedule, see Modifying an index backup schedule.
-
In extreme scenarios in which numerous storage policies exist for a backupset, the system could become overloaded with an excessive number of index backups.