Change default log directory

[Dagr]

Is there any registry key or other method for changeing the log directory for the VBO/proxies?
Had a look both at the forums and the guide, but have not been able to find any information on this.
As it stands we are using a script to manually move files.

[chris.childerhose]

I don't believe there is a way to move them but I would be interested if so. Hopefully a future enhancement.

[Polina]

Hi All,

Logs location cannot be changed. May I ask why would you need it?

[b.vanhaastrecht]

I wish to relocate the logs files to. The folder is getting very big and its a policy to not allow growing folders/data on the operating disk. So please, just like VBR add a DWORD registry option 'LogDirectory' to place the VBO logs somewhere else.

[Polina]

Hi Bastiaan,

Thanks for your feedback, the request is noted.

[mjr.epicfail]

Hi all,

Just want to kick this post back to top to check of the status of this request

[Polina]

Hi Danny,

No updates here; the default logs location cannot be changed

[mjr.epicfail]

Hi Polina,

Thats disapointed to hear.
Logs on the C: drive where the OS resides is a bad idea in general, what if logs will cause the OS drive to fill up.
I got proxies that are around 40GB of logging alone.

[Dagr]

Hi Danny,

No updates here; the default logs location cannot be changed

Any plans for at change to this?

[Mildur]

There was no new release (with new features) since Nov 29th. So no update.

Best,
Fabian

[Dagr]

...But are a there plans for changing this?

[Polina]

Hi Daniel,

In the near future, this is not foreseen.

Thanks!

[coolsport00]

Hi @Gostev / @Polina -
Is there the ability in M365 to change Job log location, like other products/components can be done as shown in KB1825?
https://www.veeam.com/kb1825

Thanks!

[Mildur]

Hi Shane

I merged your comment with an existing topic.
Unfortunately, it is not possible today to change the log folder in VB365.
The request is noted.

Best,
Fabian

[coolsport00]

Thanks Fabian!

[Stabz]

Thanks Coolsport00 to found the good topic.

Mildur thanks for your feedback

[ratkinsonuk]

+1 for this. Veeam is using 10GB of space on the O/S disk causing Windows Updates to fail.

[Mildur]

Hi Robert

Thanks for your vote. Changing the log location is not a feature included in V8.
I suggest increasing the disk space, assuming it is a virtual machine.

Best,
Fabian

[b.vanhaastrecht]

More then 2 years down the road for this FR. OS disks filling up by logging is bad IT practice!

Whats the ETA?

[edh]

We got a workarround and works good at least for us.

We moved VBO Logs to another drive with Microsoft Hard Links , check in cmd mklinks and redirect Logs from VBO installation to other folders.

You need to stop VBO services, point to new Drive and restart service.

[chris.childerhose]

That is a neat workaround, but I am sure not supported by Veeam. LOL

Nice find, though.

[b.vanhaastrecht]

Can you elaborate, as to my knowledge hardlinks cant be linked to other volumes.

[b.vanhaastrecht]

So what I mean is, with a hardlink you can redirect a folder to another one but only within the same volume. An so the risk of filling the disk remains.

/Edit, I see that Junctions can span volumes, and so this is a possible workaround.

https://learn.microsoft.com/en-us/windo ... #junctions

[edh]

"mklink /d D:\SomeData Z:\SomeData"

Anyway i think too , this setting should be easyly change in a XML inside VBO Settings as Feature Request

[mjr.epicfail]

Just kicking this topic back on top.
Also, I'm testing upgrading from v7 to v8 for our larger environments.
Where logging for tenants is saved on the proxies, this is not the case for proxies in a proxypool.
So all logs are saved on the C:\ drive of the "archiver" server. This is kind of an issue as this doesn't scale. I calculate that my C drive would alone need 1TB for logs for just the tenant logging.

Is there any ETA yet on the custom log location feature?