-
- Novice
- Posts: 6
- Liked: never
- Joined: Oct 05, 2009 11:20 am
- Full Name: ole a
- Contact:
SOBR Tiering - Error. Manual run?
CaseID: 03438988
In my system logs, I get the error message:
"Preparing index
Local index is not synchronized with object storage, please rescan the object storage repository"
I've done that - and I would like to see if it works better now. However, I see that the SOBR Tiering jobs runs at 00-04-08-12-16-20
How can I run a SOBR Tiering job manually - to make sure it works now?
Ole
In my system logs, I get the error message:
"Preparing index
Local index is not synchronized with object storage, please rescan the object storage repository"
I've done that - and I would like to see if it works better now. However, I see that the SOBR Tiering jobs runs at 00-04-08-12-16-20
How can I run a SOBR Tiering job manually - to make sure it works now?
Ole
-
- Product Manager
- Posts: 20382
- Liked: 2292 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: SOBR Tiering - Error. Manual run?
Ctrl+right click the Scale-out backup repository and select "Run Tiering Job Now". Thanks!
-
- Novice
- Posts: 6
- Liked: never
- Joined: Oct 05, 2009 11:20 am
- Full Name: ole a
- Contact:
Re: SOBR Tiering - Error. Manual run?
Worked. thanks.
All good now!
Ole
All good now!
Ole
-
- Product Manager
- Posts: 20382
- Liked: 2292 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: SOBR Tiering - Error. Manual run?
You're welcome. Let us know, if additional help is needed. Thanks!
-
- Enthusiast
- Posts: 57
- Liked: 11 times
- Joined: Nov 21, 2011 5:41 am
- Location: Hong Kong
- Contact:
Re: SOBR Tiering - Error. Manual run?
Thanks for this. Very helpful.
We are just getting Scale out backup repository working and had to stop the job because it was taking too long and conflicting with the normal backups and replications jobs.
While we were working out the kinks, we stopped the job and adjusting the configuration, but couldn't find any way to restart the job.
What's the logic behind hiding this option?
We are just getting Scale out backup repository working and had to stop the job because it was taking too long and conflicting with the normal backups and replications jobs.
While we were working out the kinks, we stopped the job and adjusting the configuration, but couldn't find any way to restart the job.
What's the logic behind hiding this option?
-
- Veeam Software
- Posts: 492
- Liked: 175 times
- Joined: Jul 21, 2015 12:38 pm
- Full Name: Dustin Albertson
- Contact:
Re: SOBR Tiering - Error. Manual run?
It is an automatic process that happens every 4 hours. Having the button there may cause confusion and have people using all the time.
Dustin Albertson | Director of Product Management - Cloud & Applications | Veeam Product Management, Alliances
-
- Chief Product Officer
- Posts: 31768
- Liked: 7271 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: SOBR Tiering - Error. Manual run?
Right. Since we're talking about offloading your oldest backups, this is not really the process that is required to start the split second after certain backup became old enough, so we can save some server resources by doing scans for oldest backups once every few hours only.
The button is actually does exist for troubleshooting purposes, just hidden behind Ctrl + right-click on the scale-out backup repository node in the management tree.
The button is actually does exist for troubleshooting purposes, just hidden behind Ctrl + right-click on the scale-out backup repository node in the management tree.
Who is online
Users browsing this forum: smexiko and 13 guests