Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Users may lose content from content libraries backed by SMB share when upgrading from vSphere 6.5 to vSphere 6.7 (57867)

Last Updated: 10/17/2018Categories: InformationalTotal Views: 3787Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

After upgrading vSphere 6.5 to vSphere 6.7, users might not be able to access the content of some libraries that are backed by SMB share.

Cause

Content Library does not detect SMB mount error when creating libraries backed by SMB shares in vSphere 6.5, therefore such libraries can be created without any error and uploading content to such libraries will consume storage on vCenter server. When upgrading from vSphere 6.5 to vSphere 6.7, the content of such libraries will not be migrated, and they won't be accessible from content library after the upgrade.

Resolution

To resolve this issue, perform the workaround steps provided in KB 58932 before upgrading to 6.7.

In case you still have libraries backed by SMB shares with content on vCenter Server during the upgrade, perform the following steps to recover the content of such libraries after upgrade:

1. Power down the upgraded target vCenter Server (6.7.x) and power on the source vCenter Server (6.5.x)

2. Find out the libraries backed by SMB shares by running the following SQL query against VCDB of the source vCenter (6.5.x):

select lib.id, lib.name, storage.storageuri from cl_library lib, cl_library_storage lib_storage, cl_storage storage where lib.id = lib_storage.library_id and lib_storage.storage_id = storage.id and storage.storageuri like 'file:///etc/vmware-content-library/winmounts/library-win-mount%';

Sample Result:
id                  |  name  |                                                                                       storageuri
--------------------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------
d822d849-6a01-4461-8249-98aa8f7e8d88 | smblib | file:///etc/vmware-content-library/winmounts/library-win-mount-d822d849-6a01-4461-8249-98aa8f7e8d88-ClsPathSeparator-smb://cls-qe-testdata.eng.vmware.com/storage/cl
_qe/smbBackupMount/

3. For each library from the list returned by the SQL query, run the following command on the source vCenter server to find out if the smb mount is actually on local file system, and add the affected libraries to a SMB library list:

(a) Get the mount path on file system from the storage URL (the last column) in the SQL query result:

sample command:
echo "file:///etc/vmware-content-library/winmounts/library-win-mount-d822d849-6a01-4461-8249-98aa8f7e8d88-ClsPathSeparator-smb://cls-qe-testdata.eng.vmware.com/storage/cl_qe/smbBackupMount/" | sed 's/file:\/\/\(.*\)-ClsPathSeparator-smb:.*/\1/'
/etc/vmware-content-library/winmounts/library-win-mount-d822d849-6a01-4461-8249-98aa8f7e8d88

(b) Check if the mount path is actually mounted on the server:

Sample command:
mount | grep "/etc/vmware-content-library/winmounts/library-win-mount-d822d849-6a01-4461-8249-98aa8f7e8d88"

If this command returns no entry (null), it means the library is consuming storage space from the vCenter server, and then add it to the SMB library list.

4. For each SMB library in the SMB library list, download all item files locally and organize them per library accordingly.

5. Power off the source vCenter (6.5.x) and power on the target vCenter (6.7.x)

6. For each SMB library in the SMB library list, perform the following actions to restore content on the target vCenter (6.7.x):

a. Create a new library on the target vCenter (6.7.x) with storage on datastore, or NFS share if applicable.
b. Upload all item files to the library that are downloaded in step 4.
c. Now all the content are restored to the upgraded vCenter (6.7.x), and the affected SMB library can be deleted.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

Take Our Survey

Support Assistant