Migration options v3 to v5

[felipeschulz]

hi, i need migrate from v3.1 to the latest version, but i need to know what is the best pratice:

• Migrate to v4 and then migrate to v5?
• migrate from v3 to v5 is possible?
• or a new deploy is recommended? (if a new deploy is the best choice, i will lose my previous data or it is possible to do an import/restore ?)

[v-jaygupta]

Hello @felipeschulz ,

Thanks for reaching out to us! If you want to retain your data then we would suggest to go for step by step upgrade i.e. upgrade to v4 first by following v4 migration guide and then upgrade from v4 to v5 or the latest version by following v5 migration guide. But the quickest way will be to deploy a new instance of CC side by side within your tenant, test it out and then you can switch to the newly deployed CC instance. In this case you will not be able to restore previous data.

[felipeschulz]

ok, I tried to do a new installation while waiting for this response, but when I follow the deployment through powershell, I can't proceed because an AzureAD module was deprecated and the "Connect-AzureAD" command on line 1068 no longer works

any suggestion?

[tiwariShiv7]

Hey @felipeschulz , Can you please try with manual deployment in this case ?

[felipeschulz]

Hi @tiwariShiv7 thanks for help me. I did this in parallel to test the CC, but now I have another problem: queued messages: i tried re-sync webapp (because it failed on the first deployment), but it didn't work:

i guess someting (bot maybe?) doesn´t retrive messages in queue on Service bus

UPDATE: i tried sending a message to everyone: because when i try to send a specfifc team or group, this option doesn´t recover results to the search (problem with Graph API?)

[v-jaygupta]

Hello @felipeschulz, The 1st and the 2nd sending options will be enabled once we add the user app against the particular team, then it will start to display Team names in the dropdown. For the message queue issue, can you please check and share the app insights screenshots and logs to troubleshoot further.

[felipeschulz]

Hi @v-jaygupta Of course:

When i send a draft messagem:

HTTP 409: Time 11:40:32 Duration 8 ms Outgoing command PUT sgghi6kw4xve4 Result code 409 AspNetCoreEnvironment Production ClientRequestId 56cf922e-c460-4fce-8331-90bb9a0119f4 Container images ServerRequestId 7f393013-b01e-007a-36c4-d6377d000000 _MS.ProcessedByMetricExtractors (Name:'Dependencies', Ver:'1.1') https://sgghi6kw4xve4.blob.core.windows.net/images?restype=container Time 11:40:32 Duration 11 ms Outgoing command BlobContainerClient.Create AspNetCoreEnvironment Production Error Azure.RequestFailedException: The specified container already exists. RequestId:7f393013-b01e-007a-36c4-d6377d000000 Time:2024-07-15T14:40:32.0800550Z Status: 409 (The specified container already exists.) ErrorCode: ContainerAlreadyExists Content: <?xml version="1.0" encoding="utf-8"?>ContainerAlreadyExistsThe specified container already exists. RequestId:7f393013-b01e-007a-36c4-d6377d000000 Time:2024-07-15T14:40:32.0800550Z Headers: Server: Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0 x-ms-request-id: 7f393013-b01e-007a-36c4-d6377d000000 x-ms-client-request-id: 56cf922e-c460-4fce-8331-90bb9a0119f4 x-ms-version: 2021-08-06 x-ms-error-code: ContainerAlreadyExists Date: Mon, 15 Jul 2024 14:40:31 GMT Content-Length: 230 Content-Type: application/xml at Azure.Storage.Blobs.ContainerRestClient.CreateAsync(Nullable1 timeout, IDictionary2 metadata, Nullable1 access, String defaultEncryptionScope, Nullable1 preventEncryptionScopeOverride, CancellationToken cancellationToken) at Azure.Storage.Blobs.BlobContainerClient.CreateInternal(PublicAccessType publicAccessType, IDictionary`2 metadata, BlobContainerEncryptionScopeOptions encryptionScopeOptions, Boolean async, CancellationToken cancellationToken, String operationName) _MS.ProcessedByMetricExtractors (Name:'Dependencies', Ver:'1.1')

do you need any specific query for logs?

[v-jaygupta]

@felipeschulz , Could you please check the failure section and share the failure logs screenshot which are outlined. Before viewing the logs I would request you to please try to access and send a new message so that the latest errors can be captured in the app insinghts logs.

[microsoft-github-policy-service[bot]]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.