Do all "System Created" jobs actually have to run?

Hello @Ken_H 

1. DDB Space Reclamations only need to run if you have storage that doesn’t support Sparse Files. This is how we prune aged data from those types of storages.
2. DDB Verifications are not required but it is good to run them regularly. They check data consistency to ensure jobs can be restored. If an issue occurs after the data is written that would corrupt it, you wouldn’t know until you needed to read it for any reason. Since the data is deduplicated, later jobs would build off the corrupt files and you would have a gap of time where all the jobs were corrupted resulting in data loss and RPO.
3. DDB Subclients controls the DDB backups. Again not required but makes DDB reconstructions faster in the event you need to recover the DDB. Without the backup we have to read through all of the data on storage to rebuild the DDB.
4. *Failover, I am not sure about this to be honest as its a little outside of my Knowledge Base. Hopefully another Engineer could speak to this one.
5. Index Backups are required to commit indexing information to storage and prune out old index records. Index is very important and these backups should run.
6. Index Server backups are same as above, the only difference is the version of Indexing. V2 indexing runs in Index Server Pseudo-Clients rather than in a subclient of the MediaAgent.
7. Index Cache Load Balancing Is not required but is generally good to run periodically to keep one Index Cache on a MediaAgent from becoming full. This migrates indexes periodically to keep cache utilization more or less equal across MediaAgents.
8. The AutoCopy Schedule is only required if you use NDMP backups with SnapMirror replication.
   
   Thank you,
   Collin