search

JoelAzaria / throwaway

throwaway repo
0 stars 0 forks source link

Why did you choose to go with your own retention routine? #1

Open JoelAzaria opened 6 years ago

JoelAzaria commented 6 years ago

Hey now @jbfriedrich

Looking at your gist here: https://gist.github.com/jbfriedrich/c7ccd123f23d8d0d5b309dd6b3983a81

I recently put something similar together for myself but for hyper-v (with some other tweaks for my usage) and I'm trying to understand the -autodelete parameter in start-vbrzip. Searching Google led me to your gist.
I notice you are not using -autodelete and instead have your own retention routine. So I'm wondering why you chose that path.
Is there some issue with -autodelete or some negative to using it? Or was there something particular to gain by coding it the way you did? Sorry, new to powershell and new to Veeam. Hoping you can point a newbie in the right direction.

Thx

jbfriedrich commented 6 years ago

Hey @JoelAzaria,

it was quit some time ago, so I do not remember all the details. I think there were issues with the retention settings in the latest version of Start-VBRZip, that was available at the time. Also you could not specify a username/password when accessing a SMB share, which was essential for me with my setup. This here was my original post to the forums at the time. The post, and the next 2, should explain the issues I had at the time.

By now, they might have resolved the retention issue and added an option for the network share credentials. I am not using that solution anymore, so I am unfortunately not up to date with my knowledge on that front.

Hope that helps!

JoelAzaria commented 6 years ago

Thank you Jason, extremely helpful.

In case it ever matters, the SMB target and credentials thing is in fact fixed, using the creds stored in the server. The retention thing I'm still (obviously..) working out.

Thanks again.