Hi all,
I recently read an interesting implementation guide using Riverbed's Cloud Gateway appliance to store backup data in Amazon's S3 Cloud. The guide is located here:
http://www.riverbed.com/assets/media/documents/briefs/SolutionBrief-Riverbed-Tivoli.pdf
I was wondering if anyone has tried this, or a similar solution. I envision the solution as using the S3 cloud as the primary sequential access pool using a FILE type device class. This would keep disk as the primary random access pool with the S3 storage as the next pool. One of my concerns is what impact this would have on reclamations since the data would need pulled and pushed for this process. In the guide linked above, they suggest a reclamation threshold of 80 or greater.
Any thoughts would be appreciated.
Thank you,
Don
I recently read an interesting implementation guide using Riverbed's Cloud Gateway appliance to store backup data in Amazon's S3 Cloud. The guide is located here:
http://www.riverbed.com/assets/media/documents/briefs/SolutionBrief-Riverbed-Tivoli.pdf
I was wondering if anyone has tried this, or a similar solution. I envision the solution as using the S3 cloud as the primary sequential access pool using a FILE type device class. This would keep disk as the primary random access pool with the S3 storage as the next pool. One of my concerns is what impact this would have on reclamations since the data would need pulled and pushed for this process. In the guide linked above, they suggest a reclamation threshold of 80 or greater.
Any thoughts would be appreciated.
Thank you,
Don