@BenjiReis The xapi is written in OCaml? That is pretty cool. I would love to learn OCaml one day.
Anyways, doesn't seem intuitive to design it this way:
Going to file an issue in that repo to see what happens. I suppose they would have to fix the OCaml code you linked as well.
@BenjiReis The xapi is written in OCaml? That is pretty cool. I would love to learn OCaml one day.
Anyways, doesn't seem intuitive to design it this way:
Going to file an issue in that repo to see what happens. I suppose they would have to fix the OCaml code you linked as well.
@BenjiReis just checked the repo: https://github.com/xcp-ng/xcp-ng-xapi-plugins/tree/master/SOURCES/etc/xapi.d/plugins
That doesn't even have the firewall-port script in it, so not sure what repository contains that to send a fix to.
@BenjiReis am I crazy or does the firewall-port script have a bug? If I use the firewall-port script to open the port then use firewall-port check 3493 tcp as a way to check, it reports that it is not open. The code needs to be fixed from
check)
if [[ -z `iptables -S $CHAIN | grep " $PORT "` ]]
then
echo "Port $PORT open: true"
else
echo "Port $PORT open: false"
fi
;;
to
check)
if [[ -n `iptables -S $CHAIN | grep " $PORT "` ]]
then
echo "Port $PORT open: true"
else
echo "Port $PORT open: false"
fi
;;
or
check)
if [[ -z `iptables -S $CHAIN | grep " $PORT "` ]]
then
echo "Port $PORT open: false"
else
echo "Port $PORT open: true"
fi
;;
If I knew how to do a git pull request and all that I'd do it, however I do not.
I have a UPS connected to XCP-ng via USB. I have a backup server I need to setup to monitor the UPS for shutdown as a secondary NUT host.
XCP-ng blocks NUT server communication. What would be the best way to edit iptables (or nftables, I forget which XCP-ng uses) to allow the NUT secondary server to communicate with the primary NUT service running on XCP-ng?
I am finding myself in this really unfortunate situation. We want to use Microsoft Connected Cache which requires Hyper-V. Microsoft Connected Cache is a way to cache inTune installation packages to reduce internet usage.
@Danp Oh for sure!
I have 3 delta backups that backup to an NFS share on a QNAP NAS.
1 of the backups is weekly and the other 2 are daily.
Is that sufficient information or did I forget a detail?
@Danp This is great, thank you. So as long as I migrate the VM, the VM with "[XO Backup weekly-vm-backup]" appended that XO creates will come with it?
I need to migrate VMs to new hardware. The new hardware doesn't have the same number of interfaces and has a bond whereas the current server does not have a bond, so I can't put them in the same pool.
Do I need to start backups fresh after the VMs have been migrated to the new hardware?
@olivierlambert The issue turned out to be a problem with the VHD files. The VM is a Windows VM converted from a physical server with disk2vhd. There were 3 disks in total that I had converted.
To resolve the issue, I created a bootable WinPE.vhd (with storage and DISM tools added) as well as another VHD as a temporary holder for .WIM files. I captured the contents of each VHD from the disk2vhd conversion into .WIM files on the temporary VHD. Then I created new .VHD files and applied the .WIM files to the new VHDs.
After this process, the backups are working.
EDIT (Important): I had to re-create the EFI boot partition and use bcdboot.exe to setup the Windows boot. I also made sure that the new .VHDs had the same drive letters assigned as the originals while in WinPE and have the new .VHDs assigned to the VM in the same order that the originals were.
