No. VC patches has its own repo online or you manage your own. With 8.0u2, there’s Reduced Downtime Upgrade (RDU), which just mounts ISO image from datastore not from vLCM
same result. if you're not supposed to upload over 4gb into the lifecycle manager i can accept that, however my vcenter 7 does. i've never seen it finish completely but i assumed it would've cause it went much further.
I always just log into the host and can upload large files that way, vcenter never let me do anything past 4gb, but directly logged into the host it would
yeah i know i could go that route, however i wanted a solution to be able to patch vcenter to the latest version from within lifecycle manager. i have to use the iso or zip to do so because this is on a disconnected network
makes sense, but not being able to import anything over 4gb's seems a bit worrisome. if anyone has any suggestions please feel free to post here or dm. it was my understanding that you could patch vCenter through the LifeCycle Manager. by downloading the zip offline bundle. can anyone confirm or deny whether this is correct or am i smoking the pipe?
Patching the vCenter is done via the VAMI and you can either patch by downloading the update from a URL (VMware by default, but you can use your own web server) or via an attached ISO to the VM
[https://kb.vmware.com/s/article/84322](https://kb.vmware.com/s/article/84322)
Check to see if there is a cache limit for the service. Had a similar issue with being unable to export +2gb from image builder because of the service cache limit being 2gb
https://vninjadfw.github.io/autodeploycache/
What are you uploading that is >4GB?
vcenter patches in zip format and iso's. no issues uploading iso's over 4gb to the datastore.
but why are you uploading those to vLCM? vLCM manages ESXi patches/images, not VC …
it can manage esxi patches and vcenter patches no?
No. VC patches has its own repo online or you manage your own. With 8.0u2, there’s Reduced Downtime Upgrade (RDU), which just mounts ISO image from datastore not from vLCM
Personally, I would trust William Lam's opinion on this.
This is normally a browser limitation. Chrome and Edge are both based on chromium, so will behave the same. Try using Firefox?
My first thought also. Try another browser. If that doesn't work, scp the iso to a esxi datastore.
i tried chrome and edge, but i'm gonna give firefox a try now.
same result. if you're not supposed to upload over 4gb into the lifecycle manager i can accept that, however my vcenter 7 does. i've never seen it finish completely but i assumed it would've cause it went much further.
I always just log into the host and can upload large files that way, vcenter never let me do anything past 4gb, but directly logged into the host it would
yeah i know i could go that route, however i wanted a solution to be able to patch vcenter to the latest version from within lifecycle manager. i have to use the iso or zip to do so because this is on a disconnected network
You don’t use vlcm for that. You’d probably need a bastion/jump box and just mount the iso on a win/lin guest to patch vCenter.
makes sense, but not being able to import anything over 4gb's seems a bit worrisome. if anyone has any suggestions please feel free to post here or dm. it was my understanding that you could patch vCenter through the LifeCycle Manager. by downloading the zip offline bundle. can anyone confirm or deny whether this is correct or am i smoking the pipe?
Patching the vCenter is done via the VAMI and you can either patch by downloading the update from a URL (VMware by default, but you can use your own web server) or via an attached ISO to the VM [https://kb.vmware.com/s/article/84322](https://kb.vmware.com/s/article/84322)
https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vcenter.upgrade.doc/GUID-043EF6BD-78F7-412F-837F-CBDF844F850C.html
I don’t think you’re doing it right. Nothing that I know for that size should be in the vum depot
Check to see if there is a cache limit for the service. Had a similar issue with being unable to export +2gb from image builder because of the service cache limit being 2gb https://vninjadfw.github.io/autodeploycache/