joemailey's Posts

So how do you do that? Create a new VM, then on the hardware config screen, add existing drive, save it and then that should be it?
So what are you saying?? You can't recover replicated VMs??
How do I do that that??
I have 3 hosts all togather. 2 local and one remote and I'm using vCenter to manage them. The 2 local hosts replicate to the remote host. I have one local physical server that has vCenter ins... See more...
I have 3 hosts all togather. 2 local and one remote and I'm using vCenter to manage them. The 2 local hosts replicate to the remote host. I have one local physical server that has vCenter installed on it and use it for managing the 3 esxi hosts. Vsphere replication appliance is installed on one of the local esxi hosts.
I just have a few questions on vSphere Replication, I've deployed the appliance on one of my ESXi hosts and I've setup replications for a few of my VMs. They have replicating successfully, these... See more...
I just have a few questions on vSphere Replication, I've deployed the appliance on one of my ESXi hosts and I've setup replications for a few of my VMs. They have replicating successfully, these replicate to a host that is located at another one of my sites(although there all on the same network, as the other site is linked directly via 100mb BT fibre link) My issue is this: if something happens to the building where our core servers are located and also where I have vCenter server setup for managing my ESXi environment, how do I get the replicated VMs to work on the host they've been replicated too? Hoping this makes sense, I know I can use the web management interface to manage vreplication appliance to recover VMs and deploy them to any host you want. But if the core site is down I won't have access to the vsphere web management interface or te vreplication appliance. So how do you bring the replicated VMs online? I have been using vranger for replicating VMs and when replicated to the host that is off site, they just appear as VMs and I can power them on by logging in to the server directly using the vsphere client, as they just appear normally as VM's on that host. But that doesn't seem to be the case with the vSphere replication appliance. Hoping someone shed some light on this.
My host has 2 local datastorea Basically store 1 & store 2, then there is a DAS(direct attached storage) attached to the host, which has few more guests. Can I move all guests to the DAS th... See more...
My host has 2 local datastorea Basically store 1 & store 2, then there is a DAS(direct attached storage) attached to the host, which has few more guests. Can I move all guests to the DAS then rebuild?
Can I reinstall ESX4 without losing datastores and my VMs?
I've cleared the tmp directory but it only frees up a small amount of space. Filesystem            Size  Used Avail Use% Mounted on /dev/sde5             4.9G  4.2G  388M  92% / Is there... See more...
I've cleared the tmp directory but it only frees up a small amount of space. Filesystem            Size  Used Avail Use% Mounted on /dev/sde5             4.9G  4.2G  388M  92% / Is there anyway to say put the /tmp on a data store or something, so it can use as much space as it wants and stop causing me errors?
I don't have a seperate /tmp partition. anyway to create one after the install?
I think the issue is caused because I have a volume that is at 100% use I done a vdf -h and it says my /dev/sde5 volume is full: vdf -h Filesystem            Size  Used Avail Use% Mounted on ... See more...
I think the issue is caused because I have a volume that is at 100% use I done a vdf -h and it says my /dev/sde5 volume is full: vdf -h Filesystem            Size  Used Avail Use% Mounted on /dev/sde5             4.9G  4.9G     0 100% / /dev/sdd1             1.1G   97M  930M  10% /boot /dev/sde2             2.0G   83M  1.8G   5% /var/log /vmfs/devices         1.8T     0  1.8T   0% /vmfs/devices /vmfs/volumes/4ab3ab16-3c3b12aa-b006-0024e83fcd83                       1.8T  657G  1.1T  36% /vmfs/volumes/Storage1 (2) /vmfs/volumes/4ab3afd4-03fc26e9-de2c-0024e83fcd85                       1.7T  601G  1.1T  35% /vmfs/volumes/Storage2 /vmfs/volumes/4ce2c91a-3661b618-3a1b-0024e83fcd85                       1.8T  354G  1.5T  19% /vmfs/volumes/Dell DAS 1 /vmfs/volumes/4d94b24f-3a42f36c-c0a7-0024e83fcd85                       1.8T  1.0T  837G  55% /vmfs/volumes/DAS esxstorage 2 I looked at the KB article http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003564 It told me to run this command: du -cshP /vmimages /var/core /root /var/log which out putted the following: [root@esx3 ~]# du -cshP /vmimages /var/core /root /var/log 193M    /vmimages 4.0K    /var/core 76K     /root 48M     /var/log 241M    total How can I fix this?
When I click on patches under update manager on a host and check patch details, alot of them come up as missing:
It is already ticked. update use to work prefectly fine until today, now it is refusing to work. I get esxupdate error codes 10 & 5 when I try a scan now of a host.
From what I can tell nothing has changed in the update manager and yes what you quoted is my patch store. I'm not sure what to check or how to proceed, any advice tips would be great.
I'm getting a lot of different codes when I try to update hosts: The host returns esxupdate error codes: 15. Check the Update Manager log files and esxupdate log files for more details. The... See more...
I'm getting a lot of different codes when I try to update hosts: The host returns esxupdate error codes: 15. Check the Update Manager log files and esxupdate log files for more details. The host returns esxupdate error codes: 5. Check the Update Manager log files and esxupdate log files for more details. The host returns esxupdate error codes: 10. Check the Update Manager log files and esxupdate log files for more details. I've no idea how to update a my host using update manager, I've attached the esxupdate.log, I hope someone can point me in the right direction. I'm not sure what to do or how to fix it.
I have got mine configured. I needed to install dell open manage on my esx server so I could manage the MD1200. I needed a PERC H800A adapter also. Jobs done.
I currently have 1 server running ESX 4.1, That as 4TB of storage. This server is used to store replications from our other 2 ESX servers. The server is running out of storage at the minu... See more...
I currently have 1 server running ESX 4.1, That as 4TB of storage. This server is used to store replications from our other 2 ESX servers. The server is running out of storage at the minute, I would like to add more storage to it. One of the ways I'm considering is buying a Dell MD1200. My issue is I'm not sure how it works or how you would configure it. My server is a Dell R710, so I will need a PERC H800A. Then I can connect the MD1200directly to the server. Will ESX just pick this up, once I start the server back up? or what do I need to do, to get the ESX server to find the attached storage? Hope this makes sense and that someone can explain a bit more to me.
Most likely because the staging process was complete - aka the downloading off the updates. Staging downloads your updates. If you stage everything first, remediate will install the... See more...
Most likely because the staging process was complete - aka the downloading off the updates. Staging downloads your updates. If you stage everything first, remediate will install the updates in minutes.
Stage the updates. Stage may take a while but just let it run. When it is done. you remediate the updates. I don't know why it takes so long. But that is the only way that works for ... See more...
Stage the updates. Stage may take a while but just let it run. When it is done. you remediate the updates. I don't know why it takes so long. But that is the only way that works for me. Stage the updates. once the stage is complete proceed to remediate your updates. Stage is the longest part. So don't expect it to be done quickly. just let it run over night or something or leave it running all day. That is the resolution.
Here is how you update in Vsphere: 1. Stage the updates. Your esx server will continue to run normally. 2. When staging is done(staging downloads the updates doesn't install them), that... See more...
Here is how you update in Vsphere: 1. Stage the updates. Your esx server will continue to run normally. 2. When staging is done(staging downloads the updates doesn't install them), that is when you run the remediate update. 3. Remediate update installs the updates you select. If you have not staged the updates before hand you have to wait until the server downloads them, before it can install them. This is all done in maintainence mode. Stage the updates first. this doesn't require maintaince mode. Then run remediate updates. If you stage it first, remediate will not need to download the updates as it was already done and should install in no time.
Only way I got mine to work was to do the patches 1 at a time. 1 update took up to 30 minutes to complete. Now when I say 1 update I mean it only was that update. Thing I don't... See more...
Only way I got mine to work was to do the patches 1 at a time. 1 update took up to 30 minutes to complete. Now when I say 1 update I mean it only was that update. Thing I don't like about it is you don't get any information that the ESX server is doing anything. my advice is to do one update at a time. Seemed to work for me. But I had to reboot the server that was running vCenter update manage and reboot the ESX server and then proceed to do one update at a time.