Categories

  • All news regarding Xen and XCP-ng ecosystem

    145 Topics
    5k Posts
    marcoiM
    went well with test systems. going to do prod soon.
  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    V
    Greetings! I performed a V2V migration from a standalone ESXI 7.0U2 server with a VMFS6 datastore and it seems to have worked with no hiccups I'm confused about where I am in the process probably due to mixing instructions: https://docs.xcp-ng.org/installation/migrate-to-xcp-ng/ https://docs.xen-orchestra.com/xo5/v2v-migration-guide#-initial-test-migration The steps I performed were on ESXI were: Shutdown VM Snapshot VM named with vmware tools. Turn on VM to uninstall vmware tools. Shutdown VM Snapshot VM named without vmware tools. On XenOrchestra: Performed V2V Migration Once completed I started VM booted successfully Installed Vates Tools Assigned static network configuration to the proper nics based on matching MAC addresses. and that's where I've left off. XenOrchestra reports it has a disk attached to the VM in VHD format and a snapshot named after complete import from V2V.[image: 1785868752396-disk.png] [image: 1785868779054-snapshot.png] Do I need to "Remove the test copy" or perform steps in the "Final Migration"? As far as I can tell the XCP-NG VM is in production ready state. Any support appreciated and thank you!
  • 3k Topics
    29k Posts
    acebmxerA
    @msupport said: @acebmxer You need two Disk with 300GB If this is a reply to my initial post. I have already got it installed. Where do you see this 300GB requirement? https://helpcenter.veeam.com/docs/vbr/em/system_requirements.html?ver=13 Disk Selection Logic: When selecting a disk for system and adjacent functions, Veeam Software Appliance automatically chooses an SSD over an HDD, and selects the smaller disk of the two available. The sizing recommendations for Disk 1 below remain valid for the system disk. Disk 1: 240 GB1 minimum. This disk hosts Veeam JeOS, Enterprise Manager Veeam Backup & Replication software, configuration database and instant recovery cache. Recommended sizing depends on the number of protected workloads. Sizing also accounts for configuration database growth as you add more workloads to protect: 480 GB1 SSD for small environments (up to a few hundred workloads). 960 GB1 SSD for medium-sized environments (up to a few thousand workloads). Multi-TB1 SSD for large environments. Larger capacity increases the disk space available to instant recovery cache, allowing for running more machines for longer time. Note: After Veeam Software Appliance deployment, adding new storage devices or resizing existing ones is not supported. Plan your disk capacity carefully before you start the deployment. Disk 2: 240 GB1 minimum. This disk hosts guest file system catalogs and backups, therefore recommended sizing depends on your backup storage needs. Any additional disks found in the system during Veeam Software Appliance deployment will be automatically joined with Disk 2 into the single Logical Volume Manager (LVM) spanned volume. This is only backing a few vms around 10 vms, and actual location is to nfs storage.
  • Our hyperconverged storage solution

    50 Topics
    796 Posts
    olivierlambertO
    Great, thanks for the feedback!
  • 37 Topics
    131 Posts
    AtaxyaNetworkA
    @jeremie1977 Ah, oui effectivement je n'ai pas testé avec plusieurs disques ! Et j'ai du typo dans la doc, je vais faire une PR pour modifier Je pense que c'est du a la façon d'insérer les disques et les DVD coté XCP-ng. Je vais investiguer !