@olivierlambert hi there, I'm in a non-IT related department, very quiet.
long story, stress, poor payment, low resources... I think I will be happier here.

by the way I will keep on the email subscription so I keep informing on how is your way going.

good luck with your projects !!

@txsastre hi everyone.

this is a sort of goodbye because I'm no longer in the IT department.

it's been a pleasure being a part of this community this years.
thanks very much for your help and for your product.

I've been very pleased of using it.

hope I've been helpful for de developers and community.

Thank you again !!

@olivierlambert the new wiki is Oh là là

ok, I will do the backup again, will see in a few days.

thanks.

I'm doing a continuous replication of the vms. But sometimes I get the error of "Could't find the base disk" then I force to do the copy again and it works but this error is recursive.

I upgraded doce 2 days ago but it happened before.

5.58.2 server and web

@olivierlambert ok I will tell you how it goes
wish me luck

hi there.

a few days ago I asked this https://xcp-ng.org/forum/topic/2301/upgrade-move-vms-reboot?_=1577476241033

and as as by now there is no such assistant that I was used to use with xencenter and xenserver when upgrading the hosts I have developed an script that does the same, because I need a lot of time for moving, checking, rebooting just for upgrading the servere. So !

The script does the following

1. once the xcp-ng is updated
2. checks if all the running VM can be live moved
3. Disable HA
4. eject CD rom from all VMs
5. makes a inventory of the hosts
6. for each host, starting at master
		6.1 disable, evacuate and reboots
		6.2 check if its alive again from reboot
		6.3 recover the vm that were running on that host
7. Enables HA

by now I'm still learning git so I posted the script in my blog.

I tried it on my development pool and it worked fine every time, still haven't tested on production because... it's Christmas =P

obviously it can be done better, but by now it does what is wast meant to, so I'm really happy about what I have achieved in a few days.

hope it could help to someone else

https://illabit.wordpress.com/2019/12/27/xcp-ng-umar-unattended-migration-and-reboot/

Merry Christmas !

Congratulations ! Very glad to hear that !

@Danp thanks ! but I have rolled back to a previous version ( 5.50.1) and now I'm testing the backup again.

@rizaemet-0 thanks you've got the right. I already doing this, but I didn't know if you uninstalled it and installed a previous version.

it was just curiosity. So I'm gonna rollback to a previous snapshot too.

Thank you

@rizaemet-0 could you tell me how have you reverted to 5.50.1 ? thanks

hi there, yes we're using XOCE and I said that we have this problem because may be something wrong in the latests releases.

just trying to help the developers to show that there is a problem in the new versions, as I can see XOA is more tested may be because the XOCE users help to test it.

so my posts are intended to help not to complain about this wonderful product.

I have to say that I'm having the same problems.

everything is updated to the last version.

xcp-ng 8.0.0

xo-server 5.51.1
xo-web 5.51.0

ok, I changed the ETHs order to make them be the same as the production server, so both pool have their ETHs numbers in the same order.

eth0,1 - management
eth2,3 - vm
eth4,5 - SAN

and now the Disaster Recovery backup set the correct NIC in the VM.

problem solved.

hi, may be this gonna be a problem for another users, and may be could be an improvement for XO.

meanwhile I found this
http://www.ultimaforsan.com/logs/2011/8/10/xenserver-addremove-network-interface.html

that is useful for changing VM NIC, also tried and works fine.

and another solution is changing the order of NICs in XCP-ng
https://support.citrix.com/article/CTX135809#Identifying Existing NIC Characteristics

There will be an easy way to do a massive change of network, isn't it? With a bash script or something like that.

I copied a huge amount of VM from a one pool to another via Disaster Recovery

everything went fine, but when I checked the network of the VM i realized that it has assigned it a management NIC

has you can see the first pool it has a bond core with 2+3 NIC,

in the backup VM it has a NIC that is Network 3, that it belongs to the management bond 2+3

the order and NIC bonds have different order in one pool and the other.

pool 1.
bond 0+1 = management (1Gb)
bond 2+3 = VM (10Gb)
bond 4+5 = SAN (10Gb)

pool2
bond 0+1 = VM (10Gb)
bond 2+3 = management (1Gb)
bond 4+5 = SAN (10Gb)

is there a way I can tell with network has the backup VM use in the new pool ?

thanks

same problem, same solution. works fine

@olivierlambert haven't found it We'll nevermind I will keep an eye on the news