Hi still looking for info on this.

I deleted the snapshots that had been there, and new ones have been created.

@florent I just looked at the new documentation, and it's much better as far as details go.

For example, I don't recall seeing the requirement that the snapshots on the ESXi side had to have specific names.

I'll give it a try with these new docs.

Thanks.

@florent I only have 2 jobs. One called VM Backup (yeah, I know very imaginative) which backs up 2 VMs and one call XO backup which backs up the pool metadata and XO config.

The one called VM Backup is a Delta Backup, running daily at 8pm, with a full backup every 7 days.

The snapshots have the name of the backup job (for example: [XO Backup VM Backup] Windows10)

@Pilow Double checked. There's no filter in place and no new VM.

@olivierlambert Ah, OK. Looked there, everything appears to be OK.

@Danp Nothing there. The most recent entry was from yesterday (24-Sep) at 00:23 about invalid credentials. Would the cli show anything further?

Thanks.

@olivierlambert Do you mean the Health view under the Backups? That doesn't show any issues.

@Danp I didn't do anything but the restore, so it's not clear what happened and I'm looking for guidance on how to best proceed.

I have a backup jobs that runs every night. It's an incremental with a full every 7 days.

I was checking the storage today and I see that there are two snapshots from last night's backup that are still there.

Looking at the logs, last nights backup was an incremental.

How do I determine why the snapshots weren't removed, and can I safely remove them now?

Thanks.

I've been looking around, and I can't find any docs about actually restoring from a backup.

When I attempted a restore, it said it completed, but I have no idea what was actually done.

When I look at the backup screen in XO, under the logs, it shows a single item, but under the VM column, it states "VM not found!".

When I look at the local storage, and list the disks, I see a number of disks, but I'm not sure which one is the one I just restored.

Is there any documentation on restoring? I looked at https://docs.xen-orchestra.com/ but the only thing there concerns backups.

Thanks.

@DustinB When I tried to do that the first thing the migration process did was to power off the VM.

@DustinB Because I was led to believe that I could leave my VM running while the initial transfer is occurring and only have it shutdown for the final bit to be copied. I have VMs that I'd rather not shut down for some number of hours if I can avoid doing that.

@DustinB It forcibly powers off the VM.

@DustinB That's my point. The "Warm Migration" powers off the running machine.

@florent I guess I'm confused. What then does "Warm migration for all ESXi versions" mean exactly?

Powering off a running machine is really a problem since that can lead to all kinds of corruption/data loss issues.

@florent Next time I attempt one, I can do that, but again, my question is why is the VM being powered down?

Thanks.

@florent Yes, I had a snapshot, that isn't the issue. The issue is that the VM is powered off and then the transfer begins.

Thanks.

@olivierlambert OK, I guess I'm still waiting to hear why the VM that is being migrated is being shut down on the ESXi host...

Thanks.

So just checking in to see if there's been any progress on being able to do a warm migration (e.g. with the VM running)?

Thanks.

@florent The VM I ws referring to was the one on the ESXi host.

If you're providing a warm migration, then that VM should be running during the transfer.

If for whatever reason a warm migration can't be done, then the user should be made aware of that.

At this point, just to be safe, I'm going to make the assumption that the VM to be migrated has to be powered off.