@Forza Actually not all is lost. I have off site backups, so I could restore the backup target remote from it's off site backup.

I'm wondering if I power off XO, then restore the contents of the directory where my backup target remote points to, will XO then be able to see the old backups, before they were wiped? Or, will it be very confused because it's metadata is not stored on the remote but rather on the XO VM.

Hello, so I screwed up. I was playing with backups and I wanted to see if I can do a manual backup (triggered by me, no schedule). Well apparently this is not sported. I realized this after I deleted the schedule and the backup job would not save, saying I need a schedule. So I created a (default) schedule and then disabled it. I then manually triggered the backup to test this approach. Of course the backup went through just fine. Soon after I realized that I messed things up good. The default backup schedule defaults to only retaining one copy. My half a dozen previous backups have now been automatically removed. The problem is I need my first backup in case I want to start over working on my VM. Well, that gone now

I get that I caused this myself. I'm wondering if a function for manually triggered backups without deleting any previous backups can be added.

My use case is as follows. You start working on a new VM, you get the basic setup done. Now I want to be able to get back to this point at any time should the changes I make next not work out so I'd like to trigger a manual backup. Next few weeks are keeping me busy with other work. I finally come back to what I started earlier and continue my configuration. In the next few days I realize that what I have done is not going to work. At this point I would like to simply restore my first backup that already has the basic configuration done and I can go for attempt two.

I guess another way of saying this is I would like to tag certain backups as protected so that they will never be erased automatically to reclaim storage space. Does anyone agree that this would be useful?

Cheers.

@thenorthernlight Thanks! It appears I had two problems with the configuration I posted earlier that were causing the Test plugin to fail:

Use StartTLS should be off
User filter should be (userPrincipalName={{name}})

Now onto testing if actual AD logons are working.

Cheers.

@olivierlambert OK, thank you for the clarification.

@Forza Actually not all is lost. I have off site backups, so I could restore the backup target remote from it's off site backup.

I'm wondering if I power off XO, then restore the contents of the directory where my backup target remote points to, will XO then be able to see the old backups, before they were wiped? Or, will it be very confused because it's metadata is not stored on the remote but rather on the XO VM.

@ronivay @olivierlambert So ISO stores are across pool. OK, that makes sense (somehow I figured they would need to be configured on each host in a pool). In my test setup I have only one host per pool right now.

Ultimately it would be great (in my opinion) to have an across pool ISO store, like @gsrfan01 is saying.

@gsrfan01 Yes please

Hello, so I screwed up. I was playing with backups and I wanted to see if I can do a manual backup (triggered by me, no schedule). Well apparently this is not sported. I realized this after I deleted the schedule and the backup job would not save, saying I need a schedule. So I created a (default) schedule and then disabled it. I then manually triggered the backup to test this approach. Of course the backup went through just fine. Soon after I realized that I messed things up good. The default backup schedule defaults to only retaining one copy. My half a dozen previous backups have now been automatically removed. The problem is I need my first backup in case I want to start over working on my VM. Well, that gone now

I get that I caused this myself. I'm wondering if a function for manually triggered backups without deleting any previous backups can be added.

My use case is as follows. You start working on a new VM, you get the basic setup done. Now I want to be able to get back to this point at any time should the changes I make next not work out so I'd like to trigger a manual backup. Next few weeks are keeping me busy with other work. I finally come back to what I started earlier and continue my configuration. In the next few days I realize that what I have done is not going to work. At this point I would like to simply restore my first backup that already has the basic configuration done and I can go for attempt two.

I guess another way of saying this is I would like to tag certain backups as protected so that they will never be erased automatically to reclaim storage space. Does anyone agree that this would be useful?

Cheers.

Thank you guys for replying, I do appreciate it. I don't think I explained what I'm after very well. I know that you can create a local to the host ISO SR that resides on a NFS share somewhere. This is not a problem. I understand I can then repeat this on the next host.

For a moment, let's pretend you have 200 hosts. You will need to do this 200 times at first (once on each host). You will also need to do this 200 time anytime you want to change where that share resides.

What I suggesting is a new capability (because it looks like this is not possible right now) where you can create a global ISO SR repository (like a remote) that then all hosts will be able to see as such without editing each host. This already works for NFS remotes, where you setup the NFS parameters once and then all hosts can see the repository (from drop down lists).

Another way of putting it, please add the capability of designating a remote as an ISO SR. Maybe that is how I should have stated it from the beginning.

Cheers.

@AtaxyaNetwork So on the link you provided there is a warning on a yellow background that reads:

WARNING

The ISO SR will be only available on the host where you have created the directory.

That is pretty much the opposite of what I'm trying to achieve.

If I understand your command lines, this is for setting up a NFS server on a Linux box. I already have the NFS server setup and working on a Synology NAS.

I think we misunderstood each other

Hello,

In VMware vCenter one can mount a NFS share as a data store available to ALL hosts. I have done this and put all my ISOs I use to create new VMs with.

Is there no way to do this in XO short of creating a "local" ISO NFS storage repository on each host? I only have 3 hosts now but I'd like to have a dozen at some point.

It sure would be nice to have a global NFS ISO repository in XO.

Comments anyone?

Regards.

Well, that deteriorated quickly. After disabling the LDAP plugin I was finally able to migrate the VM, but only when it was powered off.

The problem is now the VM will not start on this new host and it will not migrate back to the host it was on before.

I used the my backups to restore the VM in question on to it's original host. When I powered it up, unfortunately VM did not complete booting, something about the clock has gone backwards. After restarting the VM however, everything is working as it should.

I suspect this system is too old, it's an Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz, I just set it up for experimenting. It also only has 8GB of RAM.

@tjkreidl Thanks, reading it now.