@olivierlambert

The server had high memory usage so I expect lots of paging, which could explain the block writes. I've increased the mem and want to see what difference that makes.

@olivierlambert

Results are in...

Four VMs migrated. Three using warm migration and all worked. 4th used straight migration and BSOD but worked after a reboot.

@olivierlambert

Thanks Oliver. We have used GFS with Veeam previously and will be a great addition.

@olivierlambert

We have successfully installed using:

rpm -Uvh https://repo.zabbix.com/zabbix/7.0/rhel/7/x86_64/zabbix-release-latest.el7.noarch.rpm
yum install zabbix-agent2 zabbix-agent2-plugin-* --enablerepo=base,updates

@BenjiReis

Worked perfectly. Thanks guys.

@olivierlambert

Thanks Oliver, lots to learn.

p.s. Congrats on the 8.3 launch.

@thomas-dkmt

Our Hyper-V servers have no GUI and the process I use is:

1. RDP to the Hyper-V host
2. Open PowerShell
3. Get a list of the VMs on the host

    Get-VM

4. Stop the VM

    STOP-VM -Name <name of VM>

5. Identify the VM's disk(s) for conversion

    Get-VMHardDiskDrive -VMName <name of VM>

6. Convert the VHDX to VHD (destination file extension sets the type so use ".vhd")

    Convert-VHD -Path <source path> -DestinationPath <destination path> -VHDType Dynamic

To transfer the newly created .vhd files to xcp-ng we use Putty via the cli

@thomas-dkmt

Either way.

1. If you can have the server offline then shutdown and create the VHD from the VHDX. The process creates another disk file so the original remains unchanged and if it all goes wrong you can simply restart the VM in Hyper-V and try again another day. You will need enough disk space for the original VM & the new VHD file.

2. If the server cannot be offline then export the VM and then convert the VHDX to VHD. The issue being the original will VM still be updated whilst the migration to xcp-ng takes place. You will need enough disk space for the original VM, the exported VM and the new VHD file.

@olivierlambert

We have a simplified process now.

• Shutdown VM in Hyper-V
• Convert VHDX to VHD using PowerShell
• Move VHD to xcp-ng using SSH
• Generate new name using uuidgen
• Rename VHD
• Create VM in XO and attach VHD

After much trial and error this works every time.

Is there any way to paste from the console?

We have long passwords for Windows and these need to be typed manually to obtain console access which is a real pain.

@olivierlambert

Can you clarify please?

@ph7

Thank you but still not 100% clear.

As we want to reset the delta chain periodically with a full backup, does the monthly full backup achieve this goal?

My question is ultimately, what is the maximum length of the delta chain in this scenario?

@DustinB

Does this mean the daily delta chain will be reset on the 1st of each month when a full backup is performed?

I wish to perform a daily delta backup and a monthly full backup, as shown below:

Does this mean the daily chain will be reset after each monthly?

i.e. On 2nd the chain will be Monthly Full + Daily Delta

@olivierlambert

Not a criticism but just feedback. We have come from Veeam & Datto and both have a single backup that can be virtualised, if required, and allows individual files/folders to be restored.

@florent

So really backup and CR have similarities but are two different beasts with distinct purposes

Apologies if I am over complicating this.

I have an hourly CR of a Windows server and I need to restore a single file. Being CR the file restore feature is not an option.

I am thinking I need to:

1. Spin up the CR VM
2. Copy the file to the production VM

My question is I need the CR VM to be off the network so it does not conflict with the production VM however then how do I get the file off?? Catch 22.

Again, apologies if the solution is simple and I am over complicating things.

@olivierlambert

Still trying to identify the owner of a job so the I can determine which backup job failed. The email report does not identify the host/pool. Accordingly, I need to login to every individual XO/XOA and check the backup log manually to find the failed job.

@olivierlambert

Hyper-V has the concept of Dynamic memory as documented below. This allows a startup mem value to be specified and something similar could be used for health checks as this is only needed for the network to connect then them VM gets killed.

@DustinB

Other hypervisors I have used do not perform the healthcheck as an auto restore on a different host so I cannot say. It would be good if the healthcheck could start the VM with the minimum memory value configured.