7718-1960-$ - Gym.log (39.3 KB)
Hello.
We have a strange bug which sounds like quantum physics:
At our company, we have a number of designers using Unreal to create content. Due to the nature of their work, we need to host our Unreal projects at a file server. Our previous environment was becoming too slow so we invested in a new QNAP TS-h1283XU-RP NAS system filled with 12 times 2TB 870 EVO SSD at RAID 50. The performance is good enough, designers can work directly on this file server.
The thing is: after a nightly backup is executed, and the designer is opening an Unreal project, it crashes during opening. Now the strange part: if you make a copy of the whole Unreal project, you can open the copy, it will not crash. You can close the copy, and throw it away. Now you can open the original project again and it will not crash at all.
So this makes you believe the backup software is changing something on file level which causes the project to crash. But, when I make a copy of the project, and I then only backup the original, and I compare the to folders afterwards (and without opening it with Unreal) using Total Commander or whatever, there are no differences detected, even compared on binary content. I tried various methods of backing up, but no difference.
This behavior only occurs at the new QNAP: when we place the project at a different file server, there are no issues. We also have an older model of QNAP, a TS-873U-8G, and even here there is no problem. There is a difference between the two QNAP server at the way the volume is created. My last resort will be to completely start all over with the troubled QNAP and organize the volume the same way as the older model…
Currently we use Unreal 4.27. Our backup software is Veritas Backup Exec 16.
Does this makes any sense?