Topics created by stevewest15

@Darkbeldin Thank you, I looked at the SMlog and searched for this snapshot where I only saw activity back in March 27 and yesterday (April 26). See attachment.
smlog.txt

@olivierlambert Thank you! How do I add a new disk and ensure it doesn't use the same device id (/dev/xvdc) as that is currently used by the VM? The VM currently sees this:

/dev/xvda1 94G 18G 76G 19% /
/dev/xvdb1 12G 4.4G 7.7G 37% /var/lib
/dev/xvdc1 80G 23G 58G 28% /var/www
/dev/xvdd1 200G 54G 147G 27% /Emails

cb0df2c2-2fd5-4da2-be25-bfc48da21f3e-image.png

What does "Import VDI content" and "Export VDI content" do? Just trying to see if I can copy this snapshot and then attach it to the VM:
b2e6377d-3cd0-430a-941d-9840599f9566-image.png

Thank You,

SW

+1 to @Andrew setup

@stevewest15 I would also increase your dom0 memory, 16 GB is already pretty much all being used and for migrating VMs, you need memory. Some of the resources are used for dealing with storage, whoch requires such resources. If the migration is slow, run iostat and see what resources are being used; there may be a storage bottleneck, as well.

Very likely. With an UX designer, we'll be sure to avoid those problems 😄

Thank you greatly appreciate your assistance as always!

@olivierlambert Thank you, I didn't know this. Just reading the docs about it.

Dunno it's @florent you should ask 😉

@stevewest15 I don't have any advice of the fiability of b2
Their design require us to make a minor modification to our upload service .

During a full xva backup to a S3 like service, each part uploaded is uploaded along its hash and that is used to control the integrity

Thank you! So I must be doing something wrong as I'm getting the following error when I add in the old NFS mount which has the backups:

dc65c765-1542-4c58-8082-fbb54e33f3c9-image.png

The /mnt/Tank/VMs mount contains the previous XO backups as well as some active VM storage:
680455d2-9559-4fe9-a8a2-127762d5b61b-image.png

FreeNAS has two 10Gbe nics which are isolated based on the type of traffic:

10.10.1.5 is for VM traffic

10.10.2.3 is for Backups/Migration traffic

I can confirm it's now working. Thank You! Health page loads fine w/ the latest commit.

@olivierlambert Thanks, I tried running fstrim but it returned "the discard operation is not supported" on this NFS SR mount. I also tried running on SSD mounts which do support TRIM and they all returned the same message about "discard...not supported."

The VM OS (CentOS 7.8) does support TRIM in kernel so not sure if xcp-ng or xenserver is the reason why the VM can't issue fstrim on the NFS SR mount or the SSD SR mounts.

85b94dd0-b129-45ec-9ee2-bc4b7dd92b5e-image.png

If migration failed, there's a reason. It's usually stable.

Obviously, because your hosts weren't in the pool, a different CPU model can be the problem (they are automatically adapted if they are in the same pool).

Hi,

Have you checked that before? https://xen-orchestra.com/docs/community.html

They are two very different backup modes. Why not using delta + CR?

Hi,

Thanks for picture update, I will fix it 🙂

Good, keep us posted.

Hi,

It's possible to do it using the UI, simply create a schedule with 7 as Backup retention and 2 as Replication retention.

fd938a54-8730-4bcf-85c3-7caf2018ac52-image.png

Hi,

So I tried using the NFS target remotes but the speed of transfer was very poor even though the connection from XO to the NFS server is over 10Gbe. XO is on the same XCP-ng host as the VMs being backed up. This XCP-ng server is connected to the NFS mount over 10Gbe network:
56cc5a0a-e633-443b-9a50-6575ef5cddaf-image.png

Here is the NFS Remotes setting in XO to the backup server (FreeNAS) at IP 10.10.2.3:046fcdaa-8788-4d69-aa00-c1620a0afb46-image.png

The backup logs show extremely low transfer speed:
b51d304d-2fb6-472f-8eb9-0dbec967d49c-image.png

See my answer in the other thread.