Feb 02 2015

vSphere 6.0 blog – Multi Site Content Library


This is the third part of the new vSphere 6.0 improvements and or new features blog series. The first part covered the vMotion improvements and can be found here and the second part covered the vSphere Fault Tolerance feature and can be found here.

VMware vSphere 6.0 documentation page including release notes, installation documents, upgrade documents, component documentation and so on can be found here.

This part will cover the Multi-Site Content Library. For those of you knows me or follows (thank you all for following) my blog knows that i have worked quite a lot with vCloud Director (vCD) in the past and that i really liked the product.The way of providing end users with both virtual machine (VM) management capabilities and the same time content (read VM, VM Templates, ISO and Floppy) management capabilities was just amazing.

When VMware announced the new, read approximately 1 year old, direction of targeting vCD for service provides and vRealize Automation, which offers a lot of amazing features, for the non service providers they also said that existing vCD features will be migrated to either vRealize Automation or to vCenter Server.

You can think of the Multi-Site Content Library, which is a built in feature and not a plugin, as an extension of the content management feature in vCD. This feature makes it possible for vSphere Administrators to keep things like VM Templates, vApps, ISO images and also scripts synchronised across vCenter Server and also sites.
Guess you will save quite same time during e.g. VM Template patching if you got more than one vCenter Server and/or vCenter Server and site.

Content Library facts:

  • Read/Write permissions are required for the vCenter Server and the library can be stored on e.g.
    • VMFS Datastore
    • NFS Datastore
    • CIFS share
    • local disk
  • A maximum of 10 libraries and 250 items per library.
  • When publishing content to one vCenter Server you can subscribe to the content form other vCenter Server. Almost like vCD 🙂
  • Port 443 is used for Content Library communication and the bandwidth can be limited.
  • Content can be deployed to a host or a cluster.
  • VM’s are stored as OVF files. To update the OVF you need to deploy a VM from the OFV and then make a new package.

vSphere 6.0 configuration maximums can be found here.


Skip to comment form

  1. Nick Korte

    With them moving the content libraries to the more common vsphere offering, do you think VMware will be trying to phase it out of vCD? Or totally eliminate VCD altogether? Curious of your thoughts.

  2. magander3

    Really not sure since they have pushed vCD for the service provider area for now. Really think the combination of content management and VM management in vCD is really awesome for the moment.


  3. Paulo Reis

    With this new feature, we can distribute through vCenters. It facilitate administrator jobs.

  4. Yuri

    I think that for sites that don’t have vCD implemented, this content and VM management will provide VMware administrators keep more organize and makes thing simplier.

  5. ScoZel

    It is nice to see this capability included with vSphere 6!

  6. Zsolt Pamuki

    This looks very handy. Tinkering with the templates and install images across multiple sites always been a pain in the back.

  7. magander3

    yeah, totally agree. an awesome feature from an administrative perspective. My point above in regards of content management is that it’s available for the end users in vCD.


  8. Mike Medrano

    Great blog!
    Nice work Magnus!

  9. Looneyduk

    Another nice blog! Looking forward to using this new feature to “organize my life”

  10. magander3

    thanks, yes this will make life easier.


  11. Thomas True

    This feature will make life easier in some environments.

  12. Syed Fayyaz Hussain Rizvi

    Nice Article,

  13. Cris Rodriguez

    Good Article look forward to using this feature.


  14. Andres Rojas

    Thx for the post great summary

  15. Mohamed Ibrahem

    Thanks for the good article

  16. Alessandro

    Thank you.

  17. Amit Gumber


  18. vervoort jurgen

    i will defintly use this because i always build templates first. library will com ein handy

  19. Rahim

    look forward for usinf this feature.. Thx for the explanation

  20. Geoff Neish


  21. Alex

    Really nice to see the integration of a central repository for files, templates, etc! Excited to upgrade to 6.0 when released. You mentioned integration for vRealize Automation…is this feature already included in v6.2?

  22. Zsolt Pamuki

    Content libraries are a must have in multi site environments.

  23. Andres Rojas

    Thx for the great facts on the content library

  24. Jagannath S

    Great Article 🙂

  25. Mohammed Sadiq

    Thanks for the great knowledge .

  26. Shawn

    I am thinking this could come in very handy, while playing with vCloud Air having an easy place to get my ovf file from to deploy. I am assuming that, I will be able to directly connect.

  27. Francisco Amadi

    Interesting feature, thanks!

  28. Satish Kumar B


  29. Chris

    Do you know how to change the datastore where the content library is located once is installed ?
    Maybe because is full and you cannot enlarge it.
    I wasn’t able to change it automatically.


  30. magander3

    never tried actually. I can have a look and see what i can find. If you complete it before i update, please tell how you did


  31. Johnny

    Hi Magnus
    Thanks for info. You wrote vCenter 6 Content Library use port 443.
    I have been trying to find out exactly how a CL subscription is really using the infrastructure when sync job is running. Is source and target ESXi host involved or is it only vCenter to vCenter traffic on port 443.
    I have a multi vCenter site set-up and subscription in remote site from local on premises CL sync fail.
    My remote ESXi management IP address is not viable from on premises, only vCenter via NAT ip address.
    Any idea where I can look up CL port usage?
    Br Johnny

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code class="" title="" data-url=""> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong> <pre class="" title="" data-url=""> <span class="" title="" data-url="">