-
- Service Provider
- Posts: 42
- Liked: 4 times
- Joined: Jan 21, 2021 3:17 pm
- Full Name: Hin Tang
- Contact:
Linux Proxy log directory filling up
I am seeing an issue with the location of the VB365 logs on Linux proxies fill up and either the proxy goes offline or jobs which started on that proxy get stuck resolving objects. Can you help me understand how the location of the logs is set and if it can be moved to a different location. Also, is there a way to tweak the log clean up to free up more space. Thanks!
-
- Veeam Software
- Posts: 3747
- Liked: 912 times
- Joined: Oct 21, 2011 11:22 am
- Full Name: Polina Vasileva
- Contact:
Re: Linux Proxy log directory filling up
Hi,
Changing the defaults for logs storage is not possible, and niether you can defined how many logs to keep.
Please open a support case to bring this issue to the attention of our engineers and let them investigate if it's expected or a misbehavior. Post your case ID here for the followup.
Thanks!
Changing the defaults for logs storage is not possible, and niether you can defined how many logs to keep.
Please open a support case to bring this issue to the attention of our engineers and let them investigate if it's expected or a misbehavior. Post your case ID here for the followup.
Thanks!
-
- Service Provider
- Posts: 42
- Liked: 4 times
- Joined: Jan 21, 2021 3:17 pm
- Full Name: Hin Tang
- Contact:
Re: Linux Proxy log directory filling up
Thanks, Polina. That's good to know. I have expanded /var to accommodate the logs. Do you happen to know if this is in the documentation for configuring Linux servers to serve as proxies? I found that jobs were getting stuck getting started due to the lack of space but in the VB365 console, it did not show that the issue was that so the jobs stayed in a running state until the proxy actually went offline due to /var being full.
-
- Veeam Vanguard
- Posts: 678
- Liked: 175 times
- Joined: Aug 13, 2014 6:03 pm
- Full Name: Chris Childerhose
- Location: Toronto, ON
- Contact:
Re: Linux Proxy log directory filling up
This would definitely be a great thing to document. I work with Hin, and we have recently completed some fairly substantial deployments of VB365. I have personally led two substantial deployments for the government. I'm happy to contribute to this topic further and help in any way I can.
-----------------------
Chris Childerhose
Veeam Vanguard / Veeam Legend / Veeam Ceritified Architect / VMCE
vExpert / VCAP-DCA / VCP8 / MCITP
Personal blog: https://just-virtualization.tech
Twitter: @cchilderhose
Chris Childerhose
Veeam Vanguard / Veeam Legend / Veeam Ceritified Architect / VMCE
vExpert / VCAP-DCA / VCP8 / MCITP
Personal blog: https://just-virtualization.tech
Twitter: @cchilderhose
-
- Veeam Software
- Posts: 3747
- Liked: 912 times
- Joined: Oct 21, 2011 11:22 am
- Full Name: Polina Vasileva
- Contact:
Re: Linux Proxy log directory filling up
Hi Hin and Chris,
First, can you elaborate more on what you would like to see documented? Cause all existing best practices and requirements are already shared in the HelpCenter and KBs (if there're any on Linux, I don't rememeber it well now). There's no hidden knowledge that we're keeping for ourselves
First, can you elaborate more on what you would like to see documented? Cause all existing best practices and requirements are already shared in the HelpCenter and KBs (if there're any on Linux, I don't rememeber it well now). There's no hidden knowledge that we're keeping for ourselves

-
- Service Provider
- Posts: 42
- Liked: 4 times
- Joined: Jan 21, 2021 3:17 pm
- Full Name: Hin Tang
- Contact:
Re: Linux Proxy log directory filling up
Hi Polina,
If a note could be added to this section for Backup Proxy requirements to inform that /var is where the logs are placed and to ensure that has enough storage for the logs. Please forgive me if this is already in another part of the documentation.
Thanks,
Hin
The following hardware is required:
CPU: any modern multi-core x64 processor, 4 cores minimum.
Memory: 16 GB RAM minimum. Allocating additional RAM and CPU resources can enhance backup, restore and search performance.
If you plan to deploy Veeam Backup for Microsoft 365 backup proxy server on VM with dynamic memory allocation, such VM must have 32 GB RAM minimum.
Disk space: 3 GB for the backup proxy server installation and additional free space for product logs.
If a note could be added to this section for Backup Proxy requirements to inform that /var is where the logs are placed and to ensure that has enough storage for the logs. Please forgive me if this is already in another part of the documentation.
Thanks,
Hin
The following hardware is required:
CPU: any modern multi-core x64 processor, 4 cores minimum.
Memory: 16 GB RAM minimum. Allocating additional RAM and CPU resources can enhance backup, restore and search performance.
If you plan to deploy Veeam Backup for Microsoft 365 backup proxy server on VM with dynamic memory allocation, such VM must have 32 GB RAM minimum.
Disk space: 3 GB for the backup proxy server installation and additional free space for product logs.
-
- Veeam Software
- Posts: 3747
- Liked: 912 times
- Joined: Oct 21, 2011 11:22 am
- Full Name: Polina Vasileva
- Contact:
Re: Linux Proxy log directory filling up
@HangTen
It makes sense, thanks.
I'd like to ask you also to open a support case on the issue with logs filling up space and jobs getting stuck because of it. Please post your support case ID here - I'll bring it to the attention of our RND team.
Thanks!
It makes sense, thanks.
I'd like to ask you also to open a support case on the issue with logs filling up space and jobs getting stuck because of it. Please post your support case ID here - I'll bring it to the attention of our RND team.
Thanks!
-
- Service Provider
- Posts: 42
- Liked: 4 times
- Joined: Jan 21, 2021 3:17 pm
- Full Name: Hin Tang
- Contact:
Re: Linux Proxy log directory filling up
Case #07855955 was created. Thanks!
Who is online
Users browsing this forum: No registered users and 3 guests