We just migrated to v11a and it seems that handling of time periods for capacity tier is different.
In v10:
- we had to deny offload jobs to run during backup window (22:00-05:00) as we had some locking issues, we also had to change regkey SOBRArchivingScanPeriod to 12h due to another case
- the immediate offload jobs then started at 05:00, so they were queued - clearly they were not that "immediately" anymore, but that was fine for us
in v11a:
- the immediate offload jobs seem to not be queued and do not run at the end of the blackout window, the offloads based on SOBR starts when blackout windows ends at 05:00. So they seem to be queued.
I'm not sure what the right behavior is, but is seems to have changed.
-
- Veteran
- Posts: 599
- Liked: 87 times
- Joined: Dec 20, 2015 6:24 pm
- Contact:
-
- Chief Product Officer
- Posts: 31816
- Liked: 7302 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: capacity tier time period handled different in v11(a)?
Sure, it's quite possible there were changes/improvements based on support cases from V11 users, as it's a never-ending polishing process. I have no visibility into the low-level details of those continuous small enhancements though. If the new behavior is causing you any issues, please open a support case and we will have developers review your situation.
-
- Veteran
- Posts: 599
- Liked: 87 times
- Joined: Dec 20, 2015 6:24 pm
- Contact:
Re: capacity tier time period handled different in v11(a)?
created case ##05079385
Who is online
Users browsing this forum: No registered users and 7 guests