Retention of VBO proxy logs

[OzFenric]

This has probably been asked before, but where do we configure retention for VBO proxy logs? The logs on our VBO server are being kept according to our policy to keep all sessions, but the logs on the proxy servers are being cleared after about a fortnight. Is there a setting to enable proxy logs to be held for longer? Or are the older logs being shipped off somewhere?

[Polina]

Hi,

The session history setting doesn't apply to logs, it allows to control the number of backup, restore, and other sessions displayed in the console under the History node.
All VBO logs, including proxy logs, are truncated automatically with the default of 16 txt files plus 16 archives, and there's no customization.

[Switchie_Urs]

@Polina

Is there a plan to change that behaviour? We're a service provider and run into the problem that in some cases our proxy logs not even span the last 24 hours - making troubleshooting ourself or with Veeam Support extremely difficult.
If not, could you please log that as a feature request?

thank you!
best regards,
Urs

[Polina]

Hi Urs,

In v6, we increased the number of logs stored - with extended logging, VB365 now saves up to 16 txt files plus up to 128 archives.

[Switchie_Urs]

Hi Polina,

that's good news - thanks for the update. We were holding off rushing to deploy v6 as one of the main benefits for us would be to be able to ditch Cloud Connect and use the new portal - if it were supporting Teams restores which is rumored to be supported from v7 only.
Recent talks to Veeam SEs however convinced us to update to v6 nevertheless to get latest bug fixes. And with v6a/Teams API charges the picture changes again of course.

Regards,
Urs

[Polina]

Hi Urs,

I cannot comment on v7 yet, but supporting Teams restores via the portal is definitely on the roadmap.

Btw, speaking of Teams, from what you see, what are the most popular restore scenarios? Any must-haves that you would want to see in the portal?