Hi All,
I was wondering if having clients using index V1 and others using V2 can coexist on the same commvault environment ? I mean, does have any impact on the Index cache ? On the MA performance ? ...etc
Any information or tip would be welcome.
Regards.
Best answer by Orazan
Good morning. Yes they coexist with no issues. Both v1 and v2 indexing will use the same “Index Cache” directory that is configured in the Catalog tab of the MediaAgent properties.
The retention setting in the “Catalog” tab of the MediaAgent properties is for v1 index only. v2 index retention works differently depending on if it is v2 subclient based indexing or v2 backupset indexing.
It is important to ensure that your index backups which run as “Big Data Apps” jobs are running successfully. If they are not, compaction can not happen and the index can not be physically pruned.
For performance, it is recommended to have the Index on a locally attached SSD. Be sure to follow the sizing recommendations shown here:
+8They can coexist...there’s no problem there
Good morning. Yes they coexist with no issues. Both v1 and v2 indexing will use the same “Index Cache” directory that is configured in the Catalog tab of the MediaAgent properties.
The retention setting in the “Catalog” tab of the MediaAgent properties is for v1 index only. v2 index retention works differently depending on if it is v2 subclient based indexing or v2 backupset indexing.
It is important to ensure that your index backups which run as “Big Data Apps” jobs are running successfully. If they are not, compaction can not happen and the index can not be physically pruned.
For performance, it is recommended to have the Index on a locally attached SSD. Be sure to follow the sizing recommendations shown here:
Good morning. Yes they coexist with no issues. Both v1 and v2 indexing will use the same “Index Cache” directory that is configured in the Catalog tab of the MediaAgent properties.
The retention setting in the “Catalog” tab of the MediaAgent properties is for v1 index only. v2 index retention works differently depending on if it is v2 subclient based indexing or v2 backupset indexing.
It is important to ensure that your index backups which run as “Big Data Apps” jobs are running successfully. If they are not, compaction can not happen and the index can not be physically pruned.
For performance, it is recommended to have the Index on a locally attached SSD. Be sure to follow the sizing recommendations shown here:
Thanks a lot for all the clarifications.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
