Duple fails on brand new F8 NVME

[Gremlin]

As you can guess, it is for desaster recovery.

Actually I wouldn't have guessed that. Disaster Recovery implies a catastrophic failure of the device in question often due to external forces - a copy on the device is then meaningless. I would not even consider a cross-volume copy a "backup".

Was Duple ever intended as a mechanism for internal coying between volumes

[GevinKe]

I think you're being too sensitive. Asking you to check if the SSD is healthy is a routine troubleshooting suggestion. You can search through the forum's history and find many issues related to disk abnormalities. Although the device seems to be working normally after you restarted it, there's no guarantee that the problem won't occur again after some time. Hopefully, as you said, the SSD is in good condition.

Hello

no I don't think I am.

You just can't answer seasonned IT people like me (over 35 years in big infrastructures) with such answers.
As I said all SSD are brand new and high end, they perform perfectly, it is just DUPLE that fails systematically, not the NAS or the SSD.
I sent the debug log, RIDDEN WITH PANIC LOGS, to your support for enquiry, hope they'll help me.
If not I'll put the NAS back into its box, since I bought it SPECIFICALLY for the NVME architecture and the Duple software (needed to keep unmutable copies of Veeam repository).

Hello! Thank you for your assistance. We have received the Debug logs you sent and immediately arranged for engineers to analyze them. We will reply to you as soon as possible.

I'd like to ask you, what backup mode did you use when using Duple Backup? Hybrid?

Meanwhile, during the backup operation, you can pay attention to the usage of resources such as CPU and memory. If you can tell us the number and format of the Veeam files you backed up, and it would be even better if you could attach relevant screenshots, it will be of great help for us to solve the problem.

Thank you again for your understanding and support!

[Thierry13]

The NAS crashes as well while duplicating the snapshots to volume2.
I give up, this hardware is a piece of junk, I lost my money.

[GevinKe]

The NAS crashes as well while duplicating the snapshots to volume2.
I give up, this hardware is a piece of junk, I lost my money.

Hello. Do you have an SSD that is on the compatibility list? You can try replacing it and see if it works.

Based on the analysis of the Debug logs you provided for the Duple Backup, we found that the application itself did not crash. Instead, the issue appears to be at the TOS system. To diagnose and resolve the problem more accurately, we recommend the following steps:

1. Go to TOS > Technical Support > Problem Report to generate and download a detailed log report.
2. Send the generated log report to our technical support email address for further analysis.

This will help us perform a more in-depth investigation and provide an appropriate solution.

If you need more direct assistance, we'd be happy to provide remote assistance services. Our engineers will offer support during the following time periods:
9:30-11:30, 14:00-17:00, Monday to Friday, UTC+8.
Please choose the appropriate service method according to your actual needs and arrange your time in advance so that we can provide you with timely and effective support.
Thank you for your understanding and cooperation!

[Thierry13]

Hello
The TOS crashes systematically whenever big transfers are done from Volume1 to Volume2.
I do not think that the SSD, all brand new, are involved since the 2 sites copy everyday hundreds of gigs on Volume1 through IPSEC and the NAS never failed in a month.
It is ONLY when datas are transfered from Volume1 to Volume2.
Surprisingly enough, it works sometimes and fails the day right after.

OK I'll send the detailed log report.

[GevinKe]

Hello
The TOS crashes systematically whenever big transfers are done from Volume1 to Volume2.
I do not think that the SSD, all brand new, are involved since the 2 sites copy everyday hundreds of gigs on Volume1 through IPSEC and the NAS never failed in a month.
It is ONLY when datas are transfered from Volume1 to Volume2.
Surprisingly enough, it works sometimes and fails the day right after.

OK I'll send the detailed log report.

Hello! Once we receive the logs, we will immediately assign an engineer to analyze them and get back to you as soon as possible. Thank you for your understanding and support!