@olivierlambert

I thought so however booting the VM on the LAN will cause IP conflicts and alternatively, if the VM is off the LAN then it will be inaccessible.

What is the best way to restore a single folder from a CR backup?

I do not wish to restore the entire VM, just a folder that was accidentally deleted.

Thanks in advance...

Is there a maximum run time for a backup before it will timeout?

I have a backup of a large VM to the cloud that takes longer than 24 hours to complete. After 24 hours the backup Export task disappears form the task list however the backup appears to continue running.

Should I simply wait longer or has this backup reached a timeout limit?

Is there a better way to complete backups that will take a long time?

What happens to a backup if the VM restarts during the backup?

We restart client VMs on a Sat night and some backups to offsite can take longer than 24 hours

I have a backup job that has hung. What does this error mean?

{
  "data": {
    "type": "VM",
    "id": "af2b36be-d1cf-4e67-e1a7-37f0c94300d5",
    "name_label": "SERVER01"
  },
  "id": "1733738841196",
  "message": "backup VM",
  "start": 1733738841196,
  "status": "pending",
  "tasks": [
    {
      "id": "1733738841312",
      "message": "clean-vm",
      "start": 1733738841312,
      "status": "success",
      "warnings": [
        {
          "data": {
            "path": "/xo-vm-backups/af2b36be-d1cf-4e67-e1a7-37f0c94300d5/vdis/578e1ed8-4005-4010-8b46-2590a258120d/ca6904e4-2fa2-4cad-927b-5d20529cd26c/data/a76f8556-58ff-42a6-8836-639ce2ed5024.vhd"
          },
          "message": "no alias references VHD"
        }
      ],
      "end": 1733739422534,
      "result": {
        "merge": false
      }
    },
    {
      "id": "1733739422820",
      "message": "snapshot",
      "start": 1733739422820,
      "status": "success",
      "end": 1733739425172,
      "result": "a0aecb03-4178-5614-9b8d-90091fcf0cc4"
    },
    {
      "data": {
        "id": "2b68764f-1824-46ab-b280-2d83dcff0202",
        "isFull": true,
        "type": "remote"
      },
      "id": "1733739425172:0",
      "message": "export",
      "start": 1733739425172,
      "status": "pending",
      "tasks": [
        {
          "id": "1733739426063",
          "message": "transfer",
          "start": 1733739426063,
          "status": "pending"
        }
      ]
    }
  ]
}

Found this...

https://xcp-ng.org/forum/topic/3553/creating-schedules-to-run-on-specific-days

I have a backup job with three schedules that will occasionally conflict:

1. Daily @ 8pm
2. Monthly @ 8pm on 1st
3. Quarterly @ 8pm on 1st

Is the way to resolve this:

1. Daily @ 8:02pm
2. Monthly @ 8:01pm on 1st
3. Quarterly @ 8:00pm on 1st

My understanding is this 3 will trump 2 & 1 and 2 will trump 1

I do not think sequences can help here as the three conflicts are within the same backup job.

I wish to perform a full backup to WASABI monthly on a Sunday when the bandwidth impact will be least noticed.

I cannot see any way to schedule a backup for the 1st Sunday of the month in XOA/XO

The cron command is:

00 09 * * 7 [ $(date +\%d) -le 07 ] && /run/your/script

https://stackoverflow.com/questions/3241086/how-to-schedule-to-run-first-sunday-of-every-month

Can I edit the cron file directly in XOA/XO?

@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

@olivierlambert

As per the Zabbix install guide is it safe to issue this command on xcp-ng?

rpm -Uvh https://repo.zabbix.com/zabbix/7.0/rhel/7/x86_64/zabbix-release-latest.el7.noarch.rpm

When installing the Zabbix agent the correct distro & version needs to be selected.

Based upon the information below is appears xcp-ng is compatible with Centos/RHEL/Fedora however I am unsure of which OS version to select. I am running xcp-ng 8.3

@florent

What are your thoughts on my last three questions please.

@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

When installing patches what is the difference between updating the hosts in a pool individually or simply installing the pool patches?

I understand that the pool master needs to be updated before the slaves when updating hosts individually however would it not be a simpler process just to install the pool patches?

@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.

Our infrastructure is:

1. On premise xcp-ng production server (Windows VMs)
2. On premise xcp-ng DR server
3. DSL broadband connectivity (100/40)
4. Wasabi account for offsite storage

My goals are:

• Hourly backups (8am till 8pm)
• Offsite storage to Wasabi

I have an idea of how to implement but I would appreciate any input.

My thoughts are:

1. Hourly CR to DR server (@ 8am till 8pm) - Retention 84
2. Weekly full to DR server (@ Sunday 8pm) - Retention 1
3. Daily delta to Wasabi (@ 8pm) - Retention 90
4. Quarterly full to Wasabi (Jan, April, July Oct 1st day @ 8pm) - Retention 4

Should 1 & 2 be part of the same backup job and have 3 & 4 part of a separate backup job?

Does having 2 & 4 as full backups jobs reset the chain length to avoid potential chain corruption?

Due to bandwidth constraints can I restrict the upload to after hours?

@Andrew

Got it. As we only have a single production server there is no shared storage so I guess the idea of a pool is mute.

@Andrew said in Replication retention & max chain size:

It's a quick DR server that can start an VM (or a clone) immediately if the main pool fails

Does this mean you do not have your production server(s) and DR server in the same pool?

At each client site we have a single production server and a single DR server. Both have been added to the same client specific pool however I have no idea if this is good or bad.

@Andrew @olivierlambert

We are looking to migrate from Datto backups to xcp-ng/XO

The standard Datto DR device we use for clients is:
https://continuity.datto.com/help/Content/kb/siris-alto-nas/208645136.html#S4B3

4 cores with 8 threads so HT must be enabled already
https://www.intel.com/content/www/us/en/products/sku/136429/intel-xeon-d2123it-processor-8-25m-cache-2-20-ghz/specifications.html

The Datto system also does a type health check (screenshot verification). I am not sure how they do it as the VMs never fail to boot regardless of VM resources.
https://continuity.datto.com/help/Content/kb/siris-alto-nas/KB205330860.html

The lower spec'd DR machine is not perfect however it has served it's purposes to date, being:

1. Automatic backup verification (health check / screenshot verification)
2. DR hardware in the event of a production server failure

The second scenario is not very likely, from my experience, however if the VMs had to be virtualised on the DR host then they would work, all be it slower.

What I am still not understanding is this concept of "CPU Limits"... if a host has 32 CPUs and a VM is allocated 8 then why in the advanced tab can I then allocate the VM only a fraction of those 8? Such as "4/8". What is the difference between setting the VM vCPUs on the General tab vs the CPU Limits section on the Advanced tab?