FAQ (Indexing Version 2)
Is Secondary Index Server supported by Indexing Version 2?
No, Secondary Index Server is only available on Indexing Version 1 MediaAgents.
What support does Indexing Version 2 give for viewing deleted items?
During browse operations, agents that are configured to use Indexing Version 2 show deleted items across backup cycles. This is a change from Indexing Version 1 agents, which only showed deleted items in the current cycle.
Why are index backup jobs not being aged from my backup media?
With Indexing Version 2, 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 do I see an IndexBackup pseudoclient created even though no Indexing Version 2 job was run on a subclient?
In a special case, an IndexBackup pseudoclient may be created for a subclient, even though no backup jobs are associated with the subclient storage policy. This may cause a variety of errors, specific to your environment.
The following describes the special case:
- Previously, an Indexing Version 2 backup on was run on Subclient 1, which was associated with Storage Policy 1.
- You associate Subclient 1 with Storage Policy 2, which has no Indexing Version 2 backups run on it yet.
- The system creates an IndexBackup pseudoclient for Storage Policy 2, because it expects a backup to occur on Subclient 1 using Storage Policy 2.
Why don't I see the IndexBackup pseudoclient after I run an Indexing Version 2 job?
For Indexing Version 2, an IndexBackup pseudoclient is created within 24 hours after a successful data protection job using Indexing Version 2 completes on the MediaAgent. For more information, see Indexing Version 2: Index Backup.
After installing SP11, why are IndexBackup psuedoclients created, and why are indexing subclients disabled for backups?
The index backup process was changed in SP11 to better protect a CommCell during disaster recovery events. The change ensures that an index backup is stored along with its associated data backup, thus providing optimal recoverability of data in disaster recovery situations. The system now auto-creates one IndexBackup pseudoclient for each storage policy associated with an Indexing Version 2 client, and backs up the full index per storage policy.
Since the new IndexBackup pseudoclients take care of backing up indexes, the previous indexing subclients are no longer required and have been disabled for backups.
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 Indexing Version 2 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 Indexing Version 2 index servers in a CommCell environment. For more information, see Index Server Load Report.
Last modified: 5/7/2018 8:59:52 PM