Commvault Simpana 10 & 11 have added the ability to use S3 compatible storage as a backup target.
As the Content Gateway provides a wide variety of s3 methods we can use a domain on gateway as a backup target for Commvault.
The first thing to do is to create an s3 token & keypair on Content portal to provide access to Commvault for our chosen domain.
log into the admin portal with your access credentials
Once you've logged into your domain, go to settings → tokens and create a new s3 token for your domain.
next we go to our commcell console.
Log in as a user who has permissions to create a library cvadmin for example
expand the commcell console to view the available media agents.In our example here we have one which is called simpana 10
Right click on the media agent and select all tasks → create library → cloudstorage library
enter the token + keypair and the domain as above.By default the connection will try to do ssl. If you are not using ssl or your s3 connection is running on an alternate port you will need to enter the port in a domain:port format.
Commvault creates the bucket if it is not already created so feel free to enter any name here and the bucket will be created.
It is possible to use a non ssl enabled end point. To do this make sure to have a service host entry entered like so "http://<domain-name>:<s3port>" this is required to tell Commvault not to attempt an ssl connection.
"Https://" may also be required for an s3 endpoint depending on Commvault service pack level + version.
if the media agent can connect to the storage ok you'll see a new entry like below.
if you go to the bucket in content portal you will see an index file created and some other Commvault assets inside the bucket.
to actually start using the library you will need to associate it with a storage policy and add that storage policy to subclients for backup.