Tridion Sites can store binary Content Manager content in the Content Manager database, on the file system, in an Amazon S3 bucket, or in Azure Blob storage. Use the PowerShell cmdlet Convert-TcmBinaries to convert your binaries from one storage type to another.
Procedure
- On your Content Manager server, open %TRIDION_HOME%\config\Tridion.ContentManager.config for editing.
- In the
configSections section, find the section section that configures storage currently.
- Change the
name attribute of this section element from permanentContentStorage to fallbackPermanentContentStorage. This turns your old storage medium into a read-only repository.
- Also change the name of the child element,
permanentContentStorage, to fallbackPermanentContentStorage.
- Add a new
section element, set its name attribute to permanentContentStorage, and configure its type attribute and permanentContentStorage child element for the new storage type you want to use for binaries. All new binaries will be stored in this new storage medium.
- Restart your Service Host and IIS to apply these changes.
- To migrate the existing binaries in your old repository, run the cmdlet called Convert-TcmBinaries.
After prompting you for Content Manager database credentials, the tool migrates your binaries from the old storage to the new, reporting its progress while doing so, and reporting the total number of binaries moved when done.
- As a verification step, you can run the following cmdlets on all storage types other than Content Manager database storage:
- Run Convert-TcmBinaries again to verify that your old repository is now empty.
- Run Find-TcmOrphanBinaries to checks for binaries in your new target repository that are not linked to any items.
- Run Find-TcmMissingBinaries to check for links to binaries that are absent on your new target repository.