Why are index backup jobs not being aged from my backup media?
Previous index backup jobs are kept on the backup media until there are at least three versions present on the backup media. Also, the index backup job considers the index of separate backup sets as separate versions. Therefore, you might still see older index backups on your storage media even after several backup jobs for different backup sets. For more information, see Index Cleanup and Compaction Operations.
Why don't I see the Index Backup pseudo client after I run a backup job?
An Index Backup pseudoclient is created within 24 hours after a successful data protection job completes on the MediaAgent. For more information, see Index Backup.
Note
It is recommended that you do not change the storage policies of IndexBackup pseudoclients. If you do change the storage policies, disaster recovery restores may run slower than normal.
Do IndexBackup psuedoclients affect license usage?
No, IndexBackup psuedoclients do not affect license usage.
How do I evenly distribute indexes across available disk space in index servers?
You can perform index server load balancing by running the Load Balance Index Servers workflow. This redistributes loads across all index servers in a CommCell in order to achieve optimal distribution of indexes across available disk space. For more information, see Load Balance Index Servers Workflow.
You can also view the Index Server Load Report to display information about index load statuses, index load trends, and index size distributions across MediaAgents that are acting as index servers in a CommCell environment. For more information, see Index Server Load Report.