@planedrop why dont you just disconnect the VMDK at source VM ?

@tsukraw if it's working on VMWARE, and same OS/same app, there is some cpu flag that is not presented in xen/xcp to the app that provoke the crash I guess

above my level of competency to know for sure how to mask CPU flags in a VM params

does bcdedit /enum tells auto for hypervisorlaunchtype ?

if yes, try to

bcdedit /set hypervisorlaunchtype off
shutdown /r /t 0

summoning some pro support guru ... @danp ?

@JSylvia007

      "Fatal error: exception Unix.Unix_error(Unix.EIO, \"read\", \"\")\n"

mmmm SR is failing ?
can you restore the last known good state of this VM (in parallel of the one in production) and try to backup this restored version ?

@tsukraw disable VIRIDIAN in advanced tab of the VM ? and put network card in E1000 (I think this one is taken into account only if PV Tools are not present)

restart VM and relaunch app ?

you could also try to prevent debug registers to happen, in the VM :

bcdedit /enum

to check current config

bcdedit /debug off
shutdown /r /t 0

to disable debug

@JSylvia007 long stretch test but, if you have some space on the SR where resides the VM.
shut the VM down and full-clone it.

try a backup of this clone.

report back ?

@JSylvia007 did you test create a new job, with just this VM ?
is it still failing ?

a new job would have a separate UUID and create new folders with clean metadatas on your NAS.

@olivierlambert said:

no Asrock support yet

nor HPE servers (yet...)

@JSylvia007 said:

That's correct. It's the same host and same job and same remote.

in your backup job, you have NBD enabled AND a compliant NBD enabled network on the host (network tab of the pool) ?
your XO/XOA VM is connected to this NBD enabled network ?

in ADVANCED TAB of your pool, at the bottom, MIGRATION NETWORK and BACKUP NETWORK are configured as this NBD enabled network ?

just some basic checks, sorry if it seems dumb questions

@JSylvia007 is the VM failing on the same host as the VMs not failing, in this same job ?

hey,

Could be of some interest for french speakers and why not others in the forums :
https://go.veeam.com/webinar-technical-cloud-club-france

@nikade more beautiful than scary, it goes in an usual place where no one lives as you can see on satellite view
it's an effusive éruption, not explosive, i was barely 100m when taking photos and you can also poke lava with a stick if you want (but need appropriate masks because of harming gazes like sulfur)

not the first time it goes to the sea, the island expands slowly

no casualties except from some fishes

Re: [Racked today](entire hosting solution based on Vates stack)

ha, we have an active volcano on the island too 🔥

currently active, and lava got to the sea

for context : we are a Vates Partner on Reunion Island, french overseas territory in Indian Ocean off topic, but hell yeah
https://maps.app.goo.gl/curTb1rrkzyqE3hw9

@User-cxs si ici :

tu DISABLE le serveur. tu nous confirme que c'est "comme" le probleme que tu constates ? un XOA tout vide en page d'accueil ?

tu re ENABLE, et ça reviens ok ?

tu n'as pas de probleme réseau / micro coupures / host distant au XOA (ipsec/openvpn?) ?

la déco/reco que tu as me fait penser a un simple probleme réseau (si ça reviens tout seul et aucun autre impact...)

@User-cxs tu peux aller voir dans SETTINGS / SERVERS ?
on dirait que tous les hotes master sont disable/disconnect

ou alors tu as un toolstack restart inopiné...

@anthoineb wow great news ! still impacted by this issue

@kratos said:

This may not be best practice.

in a two hosts pool, if your replicated VMs live on the Master, and it's gone, you won't be able to start the replicated VMs

you will first need to transition slave to master

indeed CR is better to another pool

@kratos @florent shouldn't he have one VM with 4 snapshots ? and delta replicas between each snap ?

@Dezerd you just have to start-copy the Replica VM

it permits the original job to keep replicating on the VM.
there is no failover/failback mecanism AFAIK

if you work on replica started VM, you will have to put up in place a replica going to original hosts

@User-cxs it is possible as long as your OS accepts it.

must be planned in the advanced settings of your VM.
Can be hotplug

If your CPU limits are 2/8, you can hotplug 6 more vcpus

@florent ho nice
we had as many "VMs with a timestamp in the name" as number of REPLICAs, and multiple snapshot on source VM
now we have "one Replica VM with multiple snapshots" ? Veeam-replica-style...
do multiple snapshots persists on source VM too ?

if it's true, that's nice on the concept.

but when your replica is over lvmoiscsi not so nice

ps : i didnt upgrade to last XOA/XCP patchs yet