danekerman (Customer) asked a question.
Was wondering if anyone has done an upgrade to v8 from 7.5 and how long did the schema migration take? I just tested one with a copy of production data and it took about 15 mins with almost 4 terabytes of data. It took about 15 mins to complete
I honestly thought it would take a lot longer. I was able to login to the new version 8 and everything looked normal and didnt see any errors in the migration logs. Almost seems too good to be true. :)
Comparing the schema/tables information (record count etc) in an ASR generated after the upgrade with an ASR generated on the older version might give you a better sense of whether the upgraded G&L instance indeed contains all that data.
Same upgrade path here and it took around 12-15 min for our 80GB of data to migrate.
And yes, also thought it was "to good to be true". Would be VERY good to know that to look for in those ASR-reports -> haven't found anything strange (yet).
Instead the challenge seem to be to get all the AFX-integrations to work.
I strongly recommend all on 8.0.0 to test AFX thoroughly, and report all the errors you find. We found some really sneaky (hidden) errors.
It will help the customer behind you doing any migration journey.
Same upgrade path in my test environment and it took around 10 minutes for ~200GB of data.
I second what @OverthinkerDave (Customer) says here about testing AFX. I have encountered a ton of little high impact AFX issues preventing me from upgrading my production environment. Crazy to me that 7.5 is going EOPS in December when 8.0.0 has so many AFX issues.
curious, what kind of AFX issues did you guys encounter?
In short the issues around AFX are (so far, and not all fixed upon P04):
1) Settings in AFX (if external dedicated server) is using settings that lock the AFX to use 5GB of 32GB (that is minimum req. now)
2) Standard LDAP-connector template can't set group memberships, if using other attribute than AD "member"
3) Standard REST-connector template can only handle data if american a-z
4) If AFX-logs get to big -> crash
5) New functionality for "test connection" (it re-compiles a dedicated test-service) is broken until P03 -> but still slow in certain situations
6) Deployment loops: IF your external AFX can't recompile a collector within 10secs, then the scheduler will give up, and send a new for compilation -> which could cause the compilation go even slower, and hence causing more deployment loops (say you have 50 connectors, and you restart AFX, then it could get messy for a while, almost deadlock) -> (there are fixes that slow this down, so not a BIG issues, but still: new behaviour in 8.0)
7) An AFXMigrationServiceProvider starts EACH time you start ACM, making the start stop for 2minutes (even if you do not have anything to migrate)
8) If you haven't used the general-db-template before, then you will get problems migrating to it IF (and only if) you do not use the reserved words for the "operation" expected in the generalt-db-template (for example create account demands the use of INSERT, otherwise the SQL-query gets stopped) -> this is hopefully going to be less aggressive in coming patches, maybe P04
Then there are other non-AFX errors... but the question was about AFX, right? 😁
Hi @OverthinkerDave (Customer) ,
Any new insights on item 2 here? known fix or workaround?
(Standard LDAP-connector template can't set group memberships, if using other attribute than AD "member")
Thanks!
Item 2 is fixed in P05
Although new LDAP-connector bugs have been introduced in P05:
9) LDAP-connectors can't do an update an account if using full DN as AccounId, and not using "capital CN".
(there are other workarounds though, but all need you to send differently formatted strings than were accepted earlier)
So in short AFX is still full with bugs in 8.0, and personally I am not expecting AFX in 8.0 be fully operational until earliest P07.
It is some HUGE changes that AFX has gone through in 8.0, and especially P04.
But understand me right: The modernization is needed, so good this is happening to AFX now
A lot of more things need to happen "soon".
Like modernize the java classes used to be able to leave the over 10year old jdk8 (which is end of life in nov-2026)
Which in practice means start supporting more modern operating systems.
AND if getting into the future, maybe look at "more ways" of integrating to other systems, like:
But ok, now I am getting a bit "off topic" 😁