Is it possible that excluding files of type .jar could potentially lead to unexpected issues?

[Kagenui-yozuru]

I've observed that the default value of the EXCLUDES environment variable is *.jar,cache,logs,*.tmp, which excludes all .jar files. Could this lead to unexpected situations? In my server, I have installed mods (which are all .jar files), and using the default EXCLUDES configuration would result in the mods within the mods/ folder not being backed up, causing issues when restoring the server and preventing it from starting properly. Additionally, there are other jar files outside the mods/ folder whose purposes I am unaware of, although they do consume a significant amount of space. Considering a better approach to exclude jar files other than those in the mods/ folder, would it be worth considering an upgrade to the exclusion strategy? For example, supporting the following format: EXCLUDES=*.jar,!mods/*.jar.

[itzg]

That is only the default. You can override it with the patterns you want or setting to an empty string to exclude nothing.

If using tar as the backup method, then anything supported by its --exclude option can be provided which will be any glob pattern.

[Kagenui-yozuru]

ok，Thank you for your response.