Not your word, then from gpatel-fr … credits to him But also for you for your kind and wealth of ideas. “Should” sounds like a time-costly test…
I don’t expect that NTFS rights are restored, too - even I don’t want that because the new server has a complete new setup for access right’s which finally meets the goals the customers wanted to have. This is really the good side of the crash…
Your’e right.
Your’e right.
Hit the goal!
My plan is to restore the files to the “small” Debian Server VM, doing a folder- and filename cleanup and transfer them to the new Windows Server. We are just missing about 20’000 files, which weren’t copied from the crashed one to the new one - almost because of “forbidden” characters (worse than you think) where NTFS says “No”!
Because the only task of the Debian VM is to restore the Duplicati backups. After restore, cleanup, transfer, verify the restored folders on the Debian VM will be deleted and reboot will done to free RAM. This scenario, because the crashed Debian Server must be up as long as the new server setup will be switched to production. Thanks god, the old Debian contains the most important files.
Originally we had to recover 3TB of data in more than a million of files on a new Windows VM. This doesn’t work in an “short” timespan and got - you know it - some other “maybe-a-problem”. Next was to repair the Ext4-Filesystem of the old (crashed) Debian VM - which was good - and transfer the data to the Windows Server.
At this point, again the question or as a comment, why does Duplicati didn’t release the RAM it used? I think I would be great to investigate this.
I hope, the transfer from the Duplicati database will work well. This will be the decisive point of the plan.
Crossing fingers.