Skip to main content
commvault.com commvault.com
Solved

Retire FileSystem agent

  • September 7, 2026
  • 3 replies
  • 15 views
Paul G
Explorer
Forum|alt.badge.img+2

Hi everyone,

At the moment, I am looking to clean-up our MSP environment. We have a lot of clients that are reported by our SLA as missed SLA and we have a lot of clients that show failed to run.

Most of the clients show up for the file system backup as FS agent was pushed when another agent was also installed. We don't need the FS backup as we also protect the clients as VM but we still need the other agent to stay active as they protect things like AD, databases or cloud applications.

Can I just retire the file system agent on these clients or will this uninstall the entire client? This is especially important when the clients are access nodes where backups are not tied directly to the client but to a pseudo client such as SQL AG or Office 365.

I can also do this by releasing the license on the FS agent via the java console but this feels like the old way of doing things.

Kind regards,

Paul

Best answer by Jace Ross

Hi ​@Paul G 

To mitigate the errors, don’t associate the “File System Agent” subclient with any schedule, Storage Policy or a Plan.

Then you can either disable “Backup Activity” on the FS subclient, or release the license on it.

 

The “File System Agent” is not required to use the machine as access node or other agent,

Thanks,

Abdu

To add to this.

You shouldn’t retire the FS agent as that uninstalls the software, which will remove integral Commvault infrastructure pieces.

Disabling backup activity on unused subclients should suffice. 

Alternatively you can exclude from monitoring for SLA reporting:
https://documentation.commvault.com/11.46/software/excluding_subclients_from_sla_in_sla_report.html

Regards,

    3 replies

    Vaulter

    Hi ​@Paul G 

    To mitigate the errors, don’t associate the “File System Agent” subclient with any schedule, Storage Policy or a Plan.

    Then you can either disable “Backup Activity” on the FS subclient, or release the license on it.

     

    The “File System Agent” is not required to use the machine as access node or other agent,

    Thanks,

    Abdu

      Vaulter
      Forum|alt.badge.img+10
      • Jace RossVaulter
      • Vaulter
      • Answer
      • September 7, 2026

      Hi ​@Paul G 

      To mitigate the errors, don’t associate the “File System Agent” subclient with any schedule, Storage Policy or a Plan.

      Then you can either disable “Backup Activity” on the FS subclient, or release the license on it.

       

      The “File System Agent” is not required to use the machine as access node or other agent,

      Thanks,

      Abdu

      To add to this.

      You shouldn’t retire the FS agent as that uninstalls the software, which will remove integral Commvault infrastructure pieces.

      Disabling backup activity on unused subclients should suffice. 

      Alternatively you can exclude from monitoring for SLA reporting:
      https://documentation.commvault.com/11.46/software/excluding_subclients_from_sla_in_sla_report.html

      Regards,

      Jace Ross, Senior Technical SME
      Paul G
      Explorer
      Forum|alt.badge.img+2
      • Paul GExplorer
      • Author
      • Explorer
      • September 8, 2026

      Hi ​@AbdulRahman AlSindiony, ​@Jace Ross,

      Thank you for both replies. I was not sure that the agent would be uninstalled when I would retire the file server registration in command center so I am glad I asked the question.

      I will probably release the license of the FS agents in de CommCell console as this will allow me to remove any alerts while still having the software. Removing a plan will still let the subclient show in up in the SLA reporting and disabled activity is the current situation which I want to clean-up.

      I don't like to exclude clients/subclients from the SLA if I can. These exclusions are often forgotten when situations change in the future.

      Kind regards,

      Paul

      Readiverse Academy Certifications

      description of image
      Terms & ConditionsAccessibility statement