1- Schedules are configured to run every 8 hours... Does it really needs to run this often?
[Answer] Each run of Index backup merely checks if an index is qualified for backup. It does not mean that every index is backed up every 8 hours. Every subclient creates a unique index and every index is qualified for backup once a week only. Once a week backup of index is needed so that when index is not in cache or corrupted, rebuild of index is swift.
2- I have FULL copies every time it runs, does it really need FULLs or it can be set as incrementals? Which I believe would decrease the amount of time it normally runs for? Usually these copies takes a little longer to finish, any way to speed up the copies?
[Answer] Job runs as full, but it does not mean that entire index cache is backed up as full. As explained above, index qualification criteria for backup works differently. How long is index backup job running on your seutp? It is not expected to run that longer. Perhaps an escalation so we can check?
3- If the data follows the storage policy, in case of TAPE backups, wouldnt it be more efficient to run Synthetic Fulls for copy it to tape?
[Answer] We do not need Synthetic full for index as index backup is always full in nature.
4- Trying to determine the most effective way to set this up, since I have seeing my monthly copies (tapes) significantly increase. Best practices?
[Answer] Is your primary copy on tape? Perhaps it is better to understand your use case via a phone call? Either you can request for a Webex session via support or if you provide any other means to call you, I can explain.