Hello,
please I need a clarification about the "Copy backups to object storage as soon as they are created" option when configuring scale-out with Object Storage as capacity tier.
When we created the scale-out for the first time, we enabled it and for a long time we have seen starting many offload jobs both for single jobs ("job name"+offload) and for scale-out (scale-out+"scale-out name"+offload)
Now we have disabled the option in order to have less concurrent offload jobs and in fact what I see is only the scale-out offload jobs, but they say always "0 backups will be copied to the capacity tier" even if the backup jobs with the scale-out as target are ending fine
The question is: when disabling the copy option, should I expect that no more backups will be copied to the capacity tier?
Thank you
db
-
- Influencer
- Posts: 22
- Liked: 3 times
- Joined: May 18, 2022 1:58 pm
- Contact:
-
- Veeam Software
- Posts: 12844
- Liked: 2487 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Copy backups to object storage as soon as they are created
Hello,
when you disable offloads / copy, then nothing gets offloaded / copied, correct.
Best regards,
Hannes
when you disable offloads / copy, then nothing gets offloaded / copied, correct.
can you maybe elaborate on this? because offload jobs have lowest priority and should not affect backup performance. And there is also a setting on tasks concurrency per object storage to reduce load.in order to have less concurrent offload jobs
Best regards,
Hannes
-
- Influencer
- Posts: 22
- Liked: 3 times
- Joined: May 18, 2022 1:58 pm
- Contact:
Re: Copy backups to object storage as soon as they are created
Thank you Hannes
I thought this option only affected the way the offload is done ("as soon as they created" vs something like "NOT as soon they created")
I thought that limiting the number of concurrent jobs, I could avoid them
db
So, unchecking "Copy backups to object storage as soon as they are created" = Any copy disabled, right?when you disable offloads / copy, then nothing gets offloaded / copied, correct.
I thought this option only affected the way the offload is done ("as soon as they created" vs something like "NOT as soon they created")
It's not about backup performance, but timeout errors.can you maybe elaborate on this? because offload jobs have lowest priority and should not affect backup performance
I thought that limiting the number of concurrent jobs, I could avoid them
db
-
- Veeam Software
- Posts: 12844
- Liked: 2487 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Copy backups to object storage as soon as they are created
yes, unchecking the "copy" box means that there is no copy.
I recommend to check with support. please post the case number for references.It's not about backup performance, but timeout errors.
Who is online
Users browsing this forum: No registered users and 11 guests