BRRABill's Field Report With XenServer
-
@scottalanmiller said:
Just share a folder from your desktop that you are running XenCenter on. Same as sharing files anywhere in the Windows world. Super simple, all Windows standard tools.
Out of curiosity, how do you do this with the XenServer. Do you set up an account for it to connect to your share?
-
@scottalanmiller said:
Yes, that is the proper way to do it both from a XenServer and from a StorageCraft perspective.
Why is that, exactly?
-
@scottalanmiller said:
And of course standard "looks like Windows" tools like WinSCP and Filezilla work great too.
Yes, I have no desire to move to the text based world.
-
@BRRABill said:
@scottalanmiller said:
Just share a folder from your desktop that you are running XenCenter on. Same as sharing files anywhere in the Windows world. Super simple, all Windows standard tools.
Out of curiosity, how do you do this with the XenServer. Do you set up an account for it to connect to your share?
Haven't done this recently but I think you just share it, and put in the creds in XenCenter.
-
@scottalanmiller said:
Haven't done this recently but I think you just share it, and put in the creds in XenCenter.
What creds, though? Your user account? Do you create an account for the XenServer?
-
@BRRABill said:
@scottalanmiller said:
Yes, that is the proper way to do it both from a XenServer and from a StorageCraft perspective.
Why is that, exactly?
Because restoring to specific platform targets rather than generic isn't practical or purposeful. Why import from a overly specific process for one platform when you can have a uniform process for any? If you were purely on just one platform, then it would be six of one, half a dozen of another, but you are not and few people are.
-
@BRRABill said:
@scottalanmiller said:
Haven't done this recently but I think you just share it, and put in the creds in XenCenter.
What creds, though? Your user account? Do you create an account for the XenServer?
That would be up to you and is purely a Windows question.
-
@scottalanmiller said:
That would be up to you and is purely a Windows question.
I am looking for ML best practice!
-
Really pretty trivial, it's a read only ISO store from your desktop.
-
BTW: last night I found there IS a way in XenCenter to force it to check for updates and then force an install.
From the ISO on their webpage, there are probably 25-30 updates needed to my fresh install.
Strangely, most of them needed a reboot which I thought was weird.
-
@BRRABill said:
BTW: last night I found there IS a way in XenCenter to force it to check for updates and then force an install.
From the ISO on their webpage, there are probably 25-30 updates needed to my fresh install.
Strangely, most of them needed a reboot which I thought was weird.
sooooo.... how did you force it?
-
@Dashrender said:
sooooo.... how did you force it?
First, if you want it to check for new version of XenServer, you have to go into TOOLS and OPTIONS and UPDATES and select that box.
To check for and install updates, go to the Notifications tab. Then go to UPDATES. Then click on REFRESH. It will give you a list of the updates, and an option to DOWNLOAD AND INSTALL.
I've only been able to install them one at a time.
QUESTION:
It is generally recommended to install every update they offer? -
@BRRABill said:
@Dashrender said:
sooooo.... how did you force it?
First, if you want it to check for new version of XenServer, you have to go into TOOLS and OPTIONS and UPDATES and select that box.
To check for and install updates, go to the Notifications tab. Then go to UPDATES. Then click on REFRESH. It will give you a list of the updates, and an option to DOWNLOAD AND INSTALL.
I've only been able to install them one at a time.
QUESTION:
It is generally recommended to install every update they offer?Yes. As is the case in 95% of instances.
-
I thought the updates were cumulative?
OK I just looked, the answer is - sorta, but not exactly.
-
I was really surprised at
a--how many there were and
b--that most of them needed rebootingI thought that was one of the things non-Windows admins always railed about, how you always have to reboot with Windows updates and not so much with non-Windows systems.
-
@BRRABill said:
I was really surprised at
a--how many there were and
b--that most of them needed rebootingI thought that was one of the things non-Windows admins always railed about, how you always have to reboot with Windows updates and not so much with non-Windows systems.
Rebooting is generally a good idea regardless. That being said I haven't had to reboot XenServer because of an update in a long time. Although I am running a very out of date version.
-
@BRRABill said:
I was really surprised at
a--how many there were and
b--that most of them needed rebootingI thought that was one of the things non-Windows admins always railed about, how you always have to reboot with Windows updates and not so much with non-Windows systems.
Rebooting for security updates has never been a railing point for any sys admin.
A lot of updates don't require the host to be reboot, think of Debian and CentOS. You can patch on the fly.
-
In XenServer:
When you select a size for a virtual disk, is that the max size it can grow to, or the actual size it is taking up?
For example, with Hyper-V, with a dynamic disk, if you say the size is 40GB, it appears as 40GB to the OS on the VM, but only takes up as much space as there is data on the host hard drive.
And since I picked "thin provisioning" in setup, ALL virtual disks will be dynamic, correct?
-
@BRRABill said:
In XenServer:
When you select a size for a virtual disk, is that the max size it can grow to, or the actual size it is taking up?
For example, with Hyper-V, with a dynamic disk, if you say the size is 40GB, it appears as 40GB to the OS on the VM, but only takes up as much space as there is data on the host hard drive.
And since I picked "thin provisioning" in setup, ALL virtual disks will be dynamic, correct?
Correct, the size of the virtual disk in this instance is the max size the disk can grow.
-
@BRRABill said:
In XenServer:
When you select a size for a virtual disk, is that the max size it can grow to, or the actual size it is taking up?
For example, with Hyper-V, with a dynamic disk, if you say the size is 40GB, it appears as 40GB to the OS on the VM, but only takes up as much space as there is data on the host hard drive.
And since I picked "thin provisioning" in setup, ALL virtual disks will be dynamic, correct?
that depends on the option you picked earlier.
Remember you started your datastore over because Scott suggested that you pick thin provisioning.
Unlike Windows, it's all or nothing so it appears on XS. All VMs are thin provisioned on a disk, or none.
So in this case you don't need to be asked. The expectation is you know the setting of your data store, and that setting will be applied.
