We often has the Problem that the AHV Backup Service stuck because the root partition is full. We resized the Partition to 160GB and it still filled up after time with over 150GB of nxbackupagent logs.
So, two thing:
* Let the service cleanup the logs if no more space is available
* Create a seperate partition for /var to prevent that the root partition ran out of space
-
- Service Provider
- Posts: 82
- Liked: 18 times
- Joined: Sep 25, 2017 7:15 am
- Location: Frankfurt/M., Germany
- Contact:
Log Rotation and Cleanup
Socials: https://arogarth.net
-
- Product Manager
- Posts: 9848
- Liked: 2607 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Log Rotation and Cleanup
Hi arogarth
Our support team can help you configure log rotation with the correct parameters in the config file.
Also they can check if the current log configuration has issues on your system.
Could you please open a support case and let us know the case number? Thank you very much.
Thanks
Fabian
Our support team can help you configure log rotation with the correct parameters in the config file.
Also they can check if the current log configuration has issues on your system.
Could you please open a support case and let us know the case number? Thank you very much.
Thanks
Fabian
Product Management Analyst @ Veeam Software
-
- Service Provider
- Posts: 82
- Liked: 18 times
- Joined: Sep 25, 2017 7:15 am
- Location: Frankfurt/M., Germany
- Contact:
Re: Log Rotation and Cleanup
Is there no KB Article to this?
And create a safe vm image - put all to the root partition is a bad idea There should be a seperate /var partition.
And create a safe vm image - put all to the root partition is a bad idea There should be a seperate /var partition.
Socials: https://arogarth.net
-
- Product Manager
- Posts: 9848
- Liked: 2607 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Log Rotation and Cleanup
Using another partition is a good request. Than you very much.
Could it be, that you have changed log level to debugging once in the last few months and forgot to reverse this setting? Normally, the disk shouldn't be filled by logs.
Our support team will be able to confirm the correct log level and if the logs are normal for your system.
I can't find a public kb article for the parameters. Just some internal documents.
Thanks
Fabian
Could it be, that you have changed log level to debugging once in the last few months and forgot to reverse this setting? Normally, the disk shouldn't be filled by logs.
Our support team will be able to confirm the correct log level and if the logs are normal for your system.
I can't find a public kb article for the parameters. Just some internal documents.
Thanks
Fabian
Product Management Analyst @ Veeam Software
Who is online
Users browsing this forum: No registered users and 2 guests