Replication shots down QNAP (worked for months before)

[peste]

Hello,

i have a big problem here. I use veeam B&R 6.1 for backup and replicate with an QNAP TS-879. Backup in a SMB Share and Replicate to an NFS activated share (as added Datastore in the ESXi 5). This constellation works since June like a charm - no problems. Until today. It replicates three Servers (SBS 2011 with 1.5TB, Server 2003 with about 50 GB and a 2008 Server with 80 GB). After the first server it failed with the message "Replica location '192.168.205.3:QNAP_NFS' is getting low on free disk space (0,0 KB left of 0,0 KB)." or "Preparing replica VM Error: The operation is not allowed in the current state.
Error: The operation is not allowed in the current state.". The QNAP has 9TB of space free. But the SMB Service after this is unreachable - i can also get no looks at the volumes (disks) until i reboot the QNAP (hard). Can i provide you with some logs or anything ? I will now test an normal Backup which runs also on this QNAP. Or should i open a case ?

Thanks in advance!
Stefan Petershofer

[foggy]

Can i provide you with some logs or anything ? I will now test an normal Backup which runs also on this QNAP. Or should i open a case ?

Yes, with all technical issues, opening a case should be the first step, as it is explained when you click New Topic. Please update this thread with your support case ID for reference, otherwise it will be removed.

[peste]

Support Case ID 5212823

[peste]

Where do i get now the support ? Only over the case, via E-Mail or over this thread ?

[foggy]

Stefan, I believe our support specialists will contact you shortly. Please note, that support is provided according to the Veeam Software Support Policy.

[Vitaliy S.]

Yes, you should continue troubleshooting your issue with your support engineer directly over the email, WeBex sessions or phone calls. These forums are not technical support forums.

[peste]

Ok, thank you. Sorry i didn´t know what the next steps are

[J1mbo]

Despite that, posting the outcome may well offer someone else some time-saving pointers in the future.

[Gostev]

Sounds great in theory, except that 99% of posters never come back to post the resolution...
But at least we can look it up, having the support case ID available.

[peste]

I would came back if we had found a solution yet. I´m not the 99% In the meanwhile i started a second replication job (which works flawlessly) had a bunch of TB on my QNAP free. I will try the old replication again today - i keep this testing minimized cause the full reset of my QNAP is always a big "stomach-thing" ?! for me. A 16TB RAID Synchronizing again is no fun. One of the old replicas whishes to be consolidated and i will try this today. But anyway, what can bring a QNAP to stop all services (SMB, NFS) when a replication fails.This job was created at the beginning of June and worked until now without any problems...

Is there a "best practise way" to remove one of the replica jobs and the machines ? First the machines and then the job ? The Machines through veeam or how ? Thanks!

I keep you updated.

[foggy]

Is there a "best practise way" to remove one of the replica jobs and the machines ? First the machines and then the job ? The Machines through veeam or how ? Thanks!

If you want to permanently remove the replica VMs from the target host, the best would be to right-click the job in the Replicas node and select Remove from Disk. Then you can delete the job itself.

[peste]

Thanks. So updating this thread: The Replication works again. All i have done is to restart the Management Agents AND consolidated one of the replica machines (what the vSphere Client wanted me to do). But i know when the replication failed for the first time(s) the machine wanted me not to consolidate it. Or i overseen it. One of this two things is the solution for this problem.