Posted by Brian on Jul 12, 2011 in vCenter Server, VMware, vSphere | 3 comments
In case you were sleeping today VMware announced vSphere 5 and all of its 150 plus glorious new features. I’ve been lucky enough to be using it for sometime in the Beta program and its really a big step forward. There are tons of new features that people have been waiting for.
But with all of the new stuff it seams a licensing change has kind of put a cloud over the shinny new features. Along with the new version VMware has change the licensing model that vSphere 5 will use, moving towards a vRAM pooled model that I will attempt to explain further. Now for some organizations this will be great and for others it will add additional cost.
There has been a lot of banter on twitter today about the licenses changes and in the VMware forums. I am holding back making a decision until I can digest this further. But from what it looks like is building a scaled up design model would be more expensive with the new licensing model.
Here is some highlights from the vSphere 5 license white paper that VMware release. You can download the full paper here.
vSphere 5.0 will be licensed on a per-processor basis with a vRAM entitlement. Each vSphere 5.0 CPU license will entitle the
purchaser to a specific amount of vRAM, or memory configured to virtual machines. The vRAM entitlement can be pooled across
a vSphere environment to enable a true cloud or utility based IT consumption model. Just like VMware technology offers
customers an evolutionary path from the traditional datacenter to cloud infrastructure, the vSphere 5.0 licensing model allows
customers to evolve to a cloud-like “pay for consumption” model without disrupting established purchasing, deployment and license management practices and processes.
You will still be buying your licenses based on sockets but there is now the vRAM amount to factor in.
Licensing Unit: Per Processor (CPU)
vSphere 5.0 is still licensed on a per-processor basis, allowing customers to continue leveraging established purchasing,
deployment and license-management processes.
So what is a vRAM Entitlement
We have introduced vRAM, a transferable, virtualization-based entitlement to offer customers the greatest flexibility for vSphere configuration and usage. vRAM is defined as the virtual memory configured to virtual machines. When a virtual machine is created, it is configured with a certain amount of virtual memory (vRAM) available to the virtual machine. Depending on the edition, each vSphere 5.0-CPU license provides a certain vRAM capacity entitlement. When the virtual machine is powered on, the vRAM configured for that virtual machine counts against the total vRAM
entitled to the user. There are no restrictions on how vRAM capacity can be distributed among virtual machines: a customer can configure many small virtual machines or one large virtual machine. The entitled vRAM is a fungible resource configured to meet customer workload requirements.
What is Pooled vRAM Capacity in vSphere 5?
An important feature of the new licensing model is the concept of pooling the vRAM capacity entitlements for all processor licenses (see Figure 1). The vRAM entitlements of vSphere CPU licenses are pooled—that is, aggregated—across all CPU licenses managed by a VMware vCenter instance (or multiple linked VMware vCenter instances) to form a total available vRAM capacity (pooled vRAM capacity). If workloads on one server are not using their full vRAM entitlement, the excess capacity can be used by other virtual machines within the VMware vCenter instance. At any given point in time, the vRAM capacity consumed by all powered-on virtual machines within a pool must be equal or lower than the pooled vRAM capacity.
How would I monitor the Pooled vRAM Capacity
Available and consumed vRAM capacity can be monitored and managed using the licensing-management module of VMware vCenter Server. Customers can create reports and set up alerts to obtain automated notification of when the level of vRAM consumption surpasses a specified level of the available pooled capacity.
So if I run out of Pool vRAM how would I increase the Pooled vRAM Capacity
If necessary, the easiest way to expand pooled vRAM capacity is to add more vSphere CPU licenses of the same edition to the vRAM pool. Alternatively, customers can upgrade all CPU licenses in the vRAM pool to a vSphere edition with a higher base vRAM entitlement.
Some Licensing Examples
vSphere 5 License pricing
read more
Posted by Brian on Jul 12, 2011 in VMware, vSphere | 2 comments
Following up on today’s announcement from VMware about vSphere 5 the next step towards building the cloud on VMware. I have gathered up some of the more important new and updated features on vSphere 5. There will be other posts written over the next weeks and months diving deeper into these features. But for now this will wet your appetite.
- Convergence. vSphere 5.0 is the first vSphere release built exclusively on the vSphere ESXi 5.0 hypervisor architecture as the host platform. VMware will not include ESX hypervisor architecture-based releases in this vSphere release or later releases. The vSphere 5.0 management platform, vCenter Server 5.0, provides support for ESXi 5.0 hosts as well as ESX/ESXi 4.x and ESX/ESXi 3.5 hosts.
- VMware vSphere Auto Deploy. Combining the features of host profiles, Image Builder, and PXE, VMware vSphere Auto Deploy simplifies the task of managing ESXi installation and upgrade for hundreds of machines. New hosts are automatically provisioned based on rules defined by the user. Rebuilding a server to a clean slate is as simple as a reboot. To move between ESXi versions, you update a rule using the Auto Deploy PowerCLI and perform a test compliance and repair operation.
- Unified CLI Framework. An expanded and enhanced esxcli framework offers a rich set of consistent and extensible commands, including new commands to facilitate on-host troubleshooting and maintenance. The framework allows consistency of authentication, roles, and auditing, using the same methods as other management frameworks such as vCenter Server and PowerCLI. You can use the esxcli framework both remotely as part of vSphere CLI and locally on the ESXi Shell (formerly Tech Support Mode).
- New Virtual machine capabilities. ESXi 5.0 introduces a new generation of virtual hardware with virtual machine hardware version 8, which includes the following new features:
o 32-way virtual SMP. ESXi 5.0 supports virtual machines with up to 32 virtual CPUs, which lets you run larger CPU-intensive workloads on the VMware ESXi platform.
o 1TB virtual machine RAM. You can assign up to 1TB of RAM to ESXi 5.0 virtual machines.
o Nonhardware accelerated 3D graphics for Windows Aero support. ESXi 5.0 supports 3D graphics to run Windows Aero and Basic 3D applications in virtual machines.
o USB 3.0 device support. ESXi 5.0 features support for USB 3.0 devices in virtual machines with Linux guest operating systems. USB 3.0 devices attached to the client computer running the vSphere Web Client or the vSphere Client can be connected to a virtual machine and accessed within it. USB 3.0 devices connected to the ESXi host are not supported at this time.
o UEFI virtual BIOS. Virtual machines running on ESXi 5.0 can boot from and use the Unified Extended Firmware Interface (UEFI).
- Graphical User Interface to configure multicore virtual CPUs. You can now configure the number of virtual CPU cores per socket in the Virtual Machine Properties view in the vSphere Web Client and the vSphere client. Previously this feature was only configurable through advanced settings.
- Client-connected USB devices. USB devices attached to the client computer running the vSphere Web Client or the vSphere Client can be connected to a virtual machine and accessed within it.
- Smart card reader support for virtual machines. Smart card readers attached to the client computer running the vSphere Web Client or the vSphere Client can be connected to one or more virtual machines and accessed within them. The virtual machine remote console, available in the vSphere Web Client and the vSphere Client, supports connecting smart card readers to multiple virtual machines, which can then be used for smart card authentication to virtual machines.
- Expanded support for VMware Tools versions. VMware Tools from vSphere 4.x is supported in virtual machines running on vSphere 5.0 hosts. Additionally, the version of VMware Tools supplied with vSphere 5.0 is also compatible with ESX/ESXi 4.x.
- Apple Mac OS X Server guest operating system support. VMware vSphere 5.0 adds support for the Apple Mac OS X Server 10.6 (“Snow Leopard”) as a guest operating system. Support is restricted to Apple Xserve model Xserve3,1 systems. For additional information, see the vSphere 5.0 RC Release notes.
- Host UEFI boot support.vSphere 5.0 supports booting ESXi hosts from the Unified Extensible Firmware Interface (UEFI). With UEFI you can boot systems from hard drives, CD-ROM drives, or USB media. Booting over the network requires the legacy BIOS firmware and is not available with UEFI.
- Support for up to 512 virtual machines. vSphere 5.0 supports up to 512 virtual machines totaling a maximum of 2048 virtual CPUs per host.
- Support for larger systems. vSphere 5.0 supports systems with up to 160 logical CPUs and up to 2TB RAM.
- Improved SNMP support. vSphere 5.0 adds the capability to convert CIM indications to SNMP traps. Check with your hardware vendor to see whether their CIM provider supports this functionality. In addition, vSphere 5.0 now supports the Host Resources MIB (RFC 2790) and allows for finer control over the types of traps sent by the SNMP agent.
- Storage DRS. This feature delivers the DRS benefits of resource aggregation, automated initial placement, and bottleneck avoidance to storage. You can group and manage similar datastores as a single load-balanced storage resource called a datastore cluster. Storage DRS makes VMDK placement and migration recommendations to avoid I/O and space utilization bottlenecks on the datastores in the cluster.
- Policy-driven storage delivery. This solution allows you to have greater control and insight into characteristics of your storage resources. It also enables virtual machine storage provisioning to become independent of specific storage available in the environment. You can define virtual machine placement rules in terms of storage characteristics and monitor a virtual machine’s storage placement based on these administrator-defined rules. The solution delivers these benefits by taking advantage of the following items:
Storage
o Integrating with Storage APIs – Storage Awareness to deliver storage characterization supplied by storage vendors.
o Enabling the vSphere administrator to tag storage based on customer-specific descriptions.
o Using storage characterizations to create virtual machine placement rules in the form of storage profiles.
o Providing easy means to check a virtual machine’s compliance against these rules.
As a result, managing storage usage and choice in vSphere deployments has become more efficient and user-friendly.
- VMFS5. VMFS5 is a new version of vSphere Virtual Machine File System that offers improved scalability and performance.
- Accelerator. An accelerator has been delivered for specific use with View (VDI) workloads. With this option configured in ESXi, a read cache is constructed in memory that is optimized for recognizing, handling, and deduplicating VDI client images. The cache is managed from within the View Composer and delivers a significant reduction, as high as 90% by early estimates, in IOPS from each ESXi host to the storage platform holding client images. This reduction in IOPS enables large scaling of the number of clients in case multiple I/O storms, typical in large VDI deployments, occur.
- iSCSI UI support. Usability improvements in this release include the ability to configure dependent hardware iSCSI and software iSCSI adapters along with the network configurations and port binding in a single dialog box using the vSphere Client. Full SDK access is also available for these configurations.
- Storage I/O Control NFS support. vSphere 5.0 extends Storage I/O Control (SIOC) to provide cluster-wide I/O shares and limits for NFS datastores.
- Storage APIs – Array Integration: Thin Provisioning. Offers an ability to reclaim blocks of a thin provisioned LUN on the array when a virtual disk is deleted.
- Swap to SSD. vSphere 5.0 provides new forms of SSD handling and optimization. The VMkernel automatically recognizes and tags SSD devices that are local to ESXi or are on the network. In addition, the VMkernel scheduler is modified to allow ESXi swap to extend to local or network SSD devices, which enables memory overcommitment and minimizes performance impact.
- 2TB+ LUN support. vSphere 5.0 provides support for 2TB+ VMFS datastores.
- Storage vMotion snapshot support. Allows Storage vMotion of a virtual machine in snapshot mode with associated snapshots. You can better manage storage capacity and performance by leveraging flexibility of migrating a virtual machine along with its snapshots to a different datastore.
- Enhanced Network I/O Control. vSphere 5.0 builds on network I/O control to allow user-defined network resource pools, enabling multi-tenancy deployment, and to bridge virtual and physical infrastructure QoS with per resource pool 802.1 tagging.
- vNetwork Distributed Switch Improvements. vSphere 5.0 provides improved visibility into virtual machine traffic through Netflow and enhances monitoring and troubleshooting capabilities through SPAN and LLDP.
- ESXi Firewall. The ESXi 5.0 management interface is protected by a service-oriented and stateless firewall, which you can configure using the vSphere Client or at the command line with esxcli interfaces. A new firewall engine eliminates the use of iptables and rule sets define port rules for each service. For remote hosts, you can specify the IP addresses or range of IP addresses that are allowed to access each service.
- Next-generation browser-based vSphere Client. A browser-based, fully-extensible, platform-independent implementation of the vSphere Client based on Adobe Flex. The vSphere 5.0 release includes both the new browser-based client and the Windows-based client available in prior releases. In this release, the browser-based client includes a subset of the functionality available in the Windows-based client, primarily related to inventory display and virtual machine deployment and configuration.
- vCenter Server Appliance. A vCenter Server implementation running on a pre-configured Linux-based virtual appliance. This appliance significantly reduces the time required to deploy vCenter Server and associated services and provides a low-cost alternative to the traditional Windows-based vCenter Server.
- Inventory Extensibility. VMware customers and partners can extend vCenter Server in multiple ways, including the inventory, graphical user interface, and agents. vCenter Server includes a manager to monitor the extensions. By deploying extensions created by VMware partners, you can use vCenter Server as a unified console to manage your virtualized datacenter.
- Solution Installation and Management. The vCenter Solutions Manager provides a consistent interface to configure and monitor vCenter-integrated solutions developed by VMware and third parties. It provides a simpler installation, configuration, and monitoring interface for managing solutions. Using the new vSphere ESX Agent Manager, you can deploy, update, and monitor vSphere agents on ESXi hosts. vSphere agents inter-operate efficiently with other vSphere features such as maintenance mode and distributed power management.
- Enhanced logging support. vSphere 5.0 adds several enhancements to system message logging. All log messages are now generated by syslog, and messages can now be logged on either local and/or one or more remote log servers. A given server can log messages from more than one host. Log messages can be remotely logged using either the Secure Sockets Layer (SSL) or TCP connections. The vSphere syslog listener is available as an optional plug-in to vCenter on Windows; in the vCenter Virtual Appliance (VCVA), logging is accomplished using the native syslog-ng facility. With vSphere 5.0, log messages from different sources can be configured to go into different logs for more convenience. Configuration of message logging can also be accomplished using ESXCLI in addition to the vSphere client.
- Fault Domain Manager — VMware High Availability has been transformed into a cloud-optimized availability platform. With Fault Domain Manager, VMware HA is more reliable in operation, more scalable in its ability to protect virtual machines, and can provide better uptime than before. All hosts in the cluster can now be primary nodes while the cluster also uses shared storage as a channel for host heartbeat detection. This enables VMware HA to react accurately and efficiently to host failures, allowing customers to grow their vSphere cluster.
Networking
- Enhanced Network I/O Control. vSphere 5.0 builds on network I/O control to allow user-defined network resource pools, enabling multi-tenancy deployment, and to bridge virtual and physical infrastructure QoS with per resource pool 802.1 tagging.
- vNetwork Distributed Switch Improvements. vSphere 5.0 provides improved visibility into virtual machine traffic through Netflow and enhances monitoring and troubleshooting capabilities through SPAN and LLDP.
- ESXi Firewall. The ESXi 5.0 management interface is protected by a service-oriented and stateless firewall, which you can configure using the vSphere Client or at the command line with esxcli interfaces. A new firewall engine eliminates the use of iptables and rule sets define port rules for each service. For remote hosts, you can specify the IP addresses or range of IP addresses that are allowed to access each service.
VMware vCenter Server
- Next-generation browser-based vSphere Client. A browser-based, fully-extensible, platform-independent implementation of the vSphere Client based on Adobe Flex. The vSphere 5.0 release includes both the new browser-based client and the Windows-based client available in prior releases. In this release, the browser-based client includes a subset of the functionality available in the Windows-based client, primarily related to inventory display and virtual machine deployment and configuration.
- vCenter Server Appliance. A vCenter Server implementation running on a pre-configured Linux-based virtual appliance. This appliance significantly reduces the time required to deploy vCenter Server and associated services and provides a low-cost alternative to the traditional Windows-based vCenter Server.
- Inventory Extensibility. VMware customers and partners can extend vCenter Server in multiple ways, including the inventory, graphical user interface, and agents. vCenter Server includes a manager to monitor the extensions. By deploying extensions created by VMware partners, you can use vCenter Server as a unified console to manage your virtualized datacenter.
- Solution Installation and Management. The vCenter Solutions Manager provides a consistent interface to configure and monitor vCenter-integrated solutions developed by VMware and third parties. It provides a simpler installation, configuration, and monitoring interface for managing solutions. Using the new vSphere ESX Agent Manager, you can deploy, update, and monitor vSphere agents on ESXi hosts. vSphere agents inter-operate efficiently with other vSphere features such as maintenance mode and distributed power management.
- Enhanced logging support. vSphere 5.0 adds several enhancements to system message logging. All log messages are now generated by syslog, and messages can now be logged on either local and/or one or more remote log servers. A given server can log messages from more than one host. Log messages can be remotely logged using either the Secure Sockets Layer (SSL) or TCP connections. The vSphere syslog listener is available as an optional plug-in to vCenter on Windows; in the vCenter Virtual Appliance (VCVA), logging is accomplished using the native syslog-ng facility. With vSphere 5.0, log messages from different sources can be configured to go into different logs for more convenience. Configuration of message logging can also be accomplished using ESXCLI in addition to the vSphere client.
Availability
- Fault Domain Manager — VMware High Availability has been transformed into a cloud-optimized availability platform. With Fault Domain Manager, VMware HA is more reliable in operation, more scalable in its ability to protect virtual machines, and can provide better uptime than before. All hosts in the cluster can now be primary nodes while the cluster also uses shared storage as a channel for host heartbeat detection. This enables VMware HA to react accurately and efficiently to host failures, allowing customers to grow their vSphere cluster.
read more
Posted by Brian on Jul 1, 2011 in VMware | 0 comments
It is a great honor to announce that I have been name a vExpert for 2011 by VMware. It was in the middle of the night last night that the email arrived in my box and when reading email this morning I received the great news.
This is a huge honor to me to be recognized by my peers and VMware for helping to raise awareness about VMware. I will continue to try and raise the bar going forward. I am working on a few projects privately of which one will arrive in book form sometime this year on a yet to be released product.
I would like to congratulate all the fellow vExperts for 2011 on their hard work. And most of all I would like to say that the community and social media teams over at VMware are the best in any industry!!!! These people are fronted by John Troyer and their access to us is unmatched by any company that I’ve worked with and willing to get you the answers that cannot be found. They create great events and access to products and details about upcoming releases is second to none.
read more
Posted by Brian on Jun 11, 2011 in View, VMware | 0 comments
I’ve been working with VMware View a lot this year and since the new VMware Desktop Certifications are out, I figured it was time to go take one. Today I passed the VCA-DT exam. It was a pretty tough exam for an entry level certification. Not so much that they were very difficult crazy questions. It was a lot of situational type questions about what is the status of something is when a certain task is going on.
Now for me these are kind of crazy questions sometimes, these are the things that you don’t really pay attention to unless an issue comes up. Then you leap into action and solve the problem. Anyways I guess my only suggestion is to make sure you know the ins and outs of the console and what happens when a certain task is running.
read more
Posted by Brian on Jun 9, 2011 in Cisco, Cisco UCS, Hardware | 1 comment
I was helping out a team member with setting up AD authentication on a UCS chassis in our internal lab. It looked to be a pretty easy task but turned out to be a dog fight. In the end it was easy but I found a few errors in the Cisco document that explains how to configure LDAP for Cisco UCS. I will point out the items that caused me grief.
In the end its now working as expected and is a great feature to put to use. With so many different pieces of equipment in your environments being able to have a unified log in is much better than trying to remember 20 different local ID’s.
You can download and view a copy of the LDAP for Cisco UCS guide from here or a Google search will turn up the same thing.
Error #1
In the “Creating LDAP Provider” section the main part that tripped me up was the following.
If you refer to the image below shows the highlighted portion according to the document. I have updated the instruction below. Once I changed this the authentication worked immediately. Before changing it would just fail and according to the logs on the AD server it was not even making the attempt and failing.
c) This should be the string for the Bind user that you created earlier in the document. Example below
BindDN value is CN=ucsbind,OU=CiscoUCS,DC=sampledesign,DC=com
Error #2
This section in the collecting information section was also wrong. It did not cause me any issues but did require me to go back and read things a few more times to make sure.
In part d it references OU=CiscoUsers in the string. But the instructions never requested us to create this OU. It should just be the OU=CiscoUCS that you did create. Nothing to cause you issue just to clear things up.
read more
Posted by Brian on Jun 6, 2011 in Labs, VMware | 0 comments
The Chicago VMware Forum for 2011 is just around the corner on June 15th. Along with all of the great break out sessions topics and vendor booths VMware is going to be having their famous Hands on Labs. These are a great way to get you feet wet playing with some of the coolest technology from VMware and get your questions answered by VMware experts on-site.
We have added FREE Hands-On Labs for all attendees at VMware Forum 2011. This is your chance to explore our software firsthand with experts available to answer your questions. Topics include:
- VMware vSphere™ — Install & Configure
- VMware View™ 4.5 — Install and Configure
- VMware ThinApp™ 4.6
- VMware Performance Management vCenter™ Operations Standard and Enterprise
- VMware vCenter™ Site Recovery Manager – Extended Configure & Troubleshooting
- VMware vCloud Director — Install & Configure
- VMware vSphere Performance & Tuning
Register Now and don’t miss out on attending VMware Forum 2011 in your local city or online.
read more
Posted by Brian on Jun 3, 2011 in VDI, View, VMware | 8 comments
So I’ve been working with a customer on a specific use case that required extensive use of VMware View Local Mode. I will explain more about this in a moment. To sound a bit like a bad TV show, the names in this story have been changed to protect the innocent. First I’ll talk a bit about the customers requirements and then explain how View Local Mode works.
Now on to the customer use case that brought up all these questions and led me to do some deep dive research into View Local Mode operations. The use case that I was looking into was for a consulting firm. They have teams of consultants that work at customer locations 80% of the time and are only in a remote office 20% of their time. There would be 1500 mobile users and 500 office workers who would be working in a connected mode, meaning they are always in an office or a location with a network connection.
So naturally we talked about several designs that might work for them. There are 2 primary ones that would meet their needs and both would be built with VMware View 4.6.
Design #1
This design would use VMware View 4.6 to provide virtual desktops to 2000 users. The office workers are the easy part. They would be provided virtual desktops via Linked Clones and their profiles will be layered with one of the 3rd party profile tools. A few of the tools out today are AppSense, Liquidware Labs Profile unity, RingCube, UniDesk and several others.
Now the mobile users would be provided persistent desktops from View with the option to check out for Local Mode. This would allow users to check out their desktop so that it will run locally on their laptop. The checkout process will take a while because the first time a user checks out they must download the entire virtual machine. Once checked out they can replicate changes back to the datacenter to keep the copy that is locked in the datacenter up to date. This way if there is a disaster on their laptop they can recover up to the point of their last sync. This method is pretty straightforward to design, the only drawbacks with this method would be the additional disk space required and they will need to be managed like a standard PC when it comes to OS patching. The benefit to this method is by using persistent virtual machines the user only needs to check out the entire VM once, unless they are checking it out on a different end point. This greatly reduces time and bandwidth requirements.
Design #2
With this design we are still trying to accomplish the same goal, were just going about it a different way. The connected office workers will be designed in the same manor as Design #1. The difference comes in how we design for the mobile users. In this architecture we want to use the benefits of Linked Clones in VMware View. This will allow us to save on disk space and will take less effort to manage OS level patching. Since there is just a parent image to keep up to date and then all Linked Clones will pull from that image.
The tricky part comes in with using the Transfer servers and users having to do the initial image sync on check out. Then each time the parent image is recomposed for something like patching every Local Mode user will have to download the entire parent image again. This is a lot of data to pull down for 1500 users across 45 remote offices. So we will need a method to ease this burden.
The initial idea was hey we can just put the View Transfer servers out in the remote offices and users can pull their data for a local server. Well that turned out to be not possible, I will explain in more detail below. The option that was uncovered was the ability to use a Web proxy to cache data at the remote site that the users data would flow through. This proxy would only be able to cache the parent image data since other disks would be user specific. Once the first user pulled down the updated parent image the proxy would populate the cache and would speed up the process for the next users. You can find out more about this in the View administration PDF guide. The OS delta disk and user persistent disk would still be pulled down from the datacenter across the WAN in this design.
Facts about VMware View Transfer servers
A transfer server is a server that will handle the communications for users when they check out or in a View desktop. They will access a compressed version of the parent image being used for the Linked Clone View pool that the user is a member of. If you are allowing a persistent desktop to be checked out the transfer server does not cache these and it will just be pulled directly from the datastore that it sits on.
- Transfer server must be a virtual server on vSphere & part of same vCenter of View install
- Transfer servers should be kept in Datacenter near vSphere hosts and storage that contains the parent image
- They do not cache the delta disks or user Persistent disks, these must be pulled directly from the source
- You can check out and in desktops via View Security server but speed is slower, around 50% of direct speed
- After a recompose of parent image you will be required to download entire image again
- VMware recommends about 20 max concurrent transfers per server. At this point through testing a 1gb network connection will become saturated. So you will need to scale the number of transfer servers based on this. It really depends on how many concurrent transfers you expect to have as there is no assigned users hard limit.
- If you have multiple transfer servers they will use a repository to store the compressed image, this is just a CIFS or NFS share that all server must have access to.
If you have more questions about how anything works on this process drop your question in the comments and I will try and get you an answer. I will also try and keep this post up to date as new things are discovered about the Local Mode process.
read more
