file backup with hardened repo as cache didn't work properly

[mcz]

Hi everyone,

just created a simple file-backupjob for a folder with some files and used a hardened linux repo as backup cache - my backup target is an object storage. However, it never run pretty: It took hours to assign resources(!!), it took hours to backup, it took hours to update metadata. All in all I had 8 hours of backup job for some hundret MB's - so something was clearly wrong here.

Long story short: Removing the hardened repo as cache-server and use a different one just fixed the issue. According to the support-team there is no documentation that you can't or shouldn't use a hardened repo as cache server.

If my information is correct, could you please engage QA to have a look at it? I mean if it was not recommended or supported, it would be nice when veeam would at least bring a warning or (better) reject the operation to use a hardened repo as the cache server.

Thank you!

[david.domask]

Hi Michael,

Thank you for the report, and the behavior does seem a bit odd. I'm glad you have a workaround that works for you, but may I ask you to please share the case number for your case for us to review? I'm not aware of any specifics regarding the cache repository and hardened repositories, but would be great to see what was checked on the case. Will discuss the main question internally, but would be great if you could share the case number.

[mcz]

Hi David,

sure. The case # is: 07401934

[mcz]

Hi everyone,

just a short summary for everyone that might read this thread in the future: The issue had nothing to do with the hardened repository itself, it was caused by a routing/networking-topic.