nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Migration C2C : Data preparation : We found some errors

JM Perrot

Hi guys,

Yesterday during a migration C2C for JSM I got a curious error I never had before.

After importing my backup from my B Cloud instance on my DC instance, I tried to run a migration from the DC to the Cloud A.

However Igot this error during health checks migration :

Screenshot 2023-11-23 at 17.22.36.png

With the troubleshooting tools, all looks ok :

Screenshot 2023-11-24 at 09.54.53.png

Do you already see that and do you have an idea of what I did wrong or how I can process to fix it ?

Thanks a lot

Accepted answers

Brant Schroeder

@JM Perrot Were there any manual errors?

All comments

Brant Schroeder

@JM Perrot Were there any manual errors?

JM Perrot

Yes, it turned out to be related to attachments and the recovery admin account. I'm not sure why, but when I tried to import my backup to my server instance, the attachments were reorganized.

The solution was to open my backup, copy and paste the attachments from the backup to the attachment server file (after deleting the incorrect attachments, of course).
After that, the recovery admin account didn't have an address and couldn't be modified (I never had this problem before). The tip was to log in with it and perform the migration in "recovery" mode.

Brant Schroeder

@JM Perrot thanks for the response that will help others having the same issue.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

cloud

migration

jira-service-management

migration-customer-care

jira-service-management-server