SQL Log Backup - Log shipping server

[btanguay]

Hi

I've start to backup our sql log with veeam and i realize the systems is using an log shipping server instead of goind directly to the repository.
The Veeam Sql log server start to fill the c:\ drive and it's now almost full. i've also realize the backup from the previous day are still on the log shipping server.

How can i force veeam to do not use a log shipping server and use the repository?
If i cant, can veeam remove the backup from the log shipping server when it's move to the repository?

i'm using version 8, latest build.
Thanks

[Dima P.]

Hi,

In backup job settings (Guest Processing step of the wizard) under Log shipping opting choose Use the specified servers only and define the server you need. I assume right now it is set to automatic selection.

[foggy]

If i cant, can veeam remove the backup from the log shipping server when it's move to the repository?

Files should be cleared up automatically, so I'd check temporary folder permissions.

[btanguay]

Hi,

In backup job settings (Guest Processing step of the wizard) under Log shipping opting choose Use the specified servers only and define the server you need. I assume right now it is set to automatic selection.

Hi Dina

I was using the automatic settings at the beginning, but all my server were filling out space.. so I pick one server only.

[btanguay]

Files should be cleared up automatically, so I'd check temporary folder permissions.

Hi Foggy,

That was my impression, but I already find out that post and the SYSTEM account already has the full control over the Windows\temp folder.
I also have the same issue if I chose another server for the log shipping...
Benoit.

[foggy]

Then please reach out to our technical support for further investigation. Thanks.

[btanguay]

Could it be related to the user account control settings?

[btanguay]

Then please reach out to our technical support for further investigation. Thanks.

Hi Foggy, I've already open a support case : 01683286
I will let you know if we found anything.
thanks

[foggy]

Just a guess, might be related to server OS localization.

[btanguay]

We finally close the support case after escalation.
The issue is still not clear, but it wen't away suddently after i change the log shipping server to another value for only one vm
I've wait for a backup and change it back to original value.
All the vm start to work correctly.
Strange but fixed.. it's has been 1 week since and the issue didn't re-appear.
Thanks

[foggy]

Thanks for the update. Feel free to re-open the case once/if you see the behavior again.