Share via

2012 R2 Storage Migration Service failed files

Anonymous
2023-12-18T17:47:34+00:00

I have a 2012 R2 VM that I plan to transfer to a 2022 VM via a 2019 orchestrator. The inventory process isn't going well and the event log isn't helpful to me.

This is a very old, deep, filesystem that has previously been migrated from server to server via Robocopy. The volume uses Windows deduplication. There could be permissions or path length issues or both, but I don't know where to look. CHKDSK ran fine. Appreciate any help.

Windows for business | Windows Server | Storage high availability | Virtualization and Hyper-V

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

8 answers

Sort by: Most helpful
  1. Anonymous
    2023-12-25T02:25:17+00:00

    Hi Mike,

    Thanks for your reference.

    Due to the resource limitation of the Forum, we suggest you go to the Microsoft Customer Service Center to open a case so that with their permission level and resource, Microsoft could provide you with better help on your request.

    Best Regards

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2023-12-22T02:46:40+00:00

    I tried with using a different volume on the same server. No luck.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2023-12-22T01:43:42+00:00

    Hi Mike,

    Thanks for your update.

    I noticed that this issue is related to SMB, this involves the network, and you can check if there is a problem with the network.

    Best Regards

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-12-21T16:45:02+00:00

    To be clear, I'm not moving anything until I get the failed files resolved. Unfortunately, I don't know which ones are implicated. A list-only Robocopy run didn't find anything, but ICACLS did.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2023-12-19T02:58:00+00:00

    Hi Mike,

    Hope you're doing well.

    Please fer to the following:

    1. According to the errors you showed, there may be a compatibility issue. So, before transferring your VM from 2012 R2 to 2022 via a 2019 orchestrator, ensure that your VMs are compatible with the new environment.

    Here is document for you reference:

    Upgrade information for System Center Orchestrator | Microsoft Learn

    1. And there could be permissions or path length issues or both in filesystem. And the volume uses Windows deduplication, so it's necessary to open dedup on server 2022 during migrating. Or you can disable deduplication before migrating. and try the inventory process again.

    Note: To avoid data loss, it's important to backup all your data.

    How to extend file path characters maximum limit manually? - Microsoft Community

    Hope my answer can help you.

    Best Regards

    Was this answer helpful?

    0 comments No comments