tag:blogger.com,1999:blog-9726833.post9141895764209871161..comments2023-11-11T19:20:51.515+00:00Comments on The Trouble with Tribbles...: Compressing Backup CatalogsPeter Tribblehttp://www.blogger.com/profile/09363446984245451854noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-9726833.post-50389094200125199142010-01-30T17:33:01.448+00:002010-01-30T17:33:01.448+00:00I did the same with netbackup on Solaris when we u...I did the same with netbackup on Solaris when we updated from Version 5.x to the latest 6.5.x about one year ago. We have a catalog of about 60Gb and the compression ratio with ZFS default compression is 1.98. This works really great and I think netbackup do not have limitations in catalog size if you run the system in 64bit environment. By the way, Solaris and netbackup works really great together.tonisolerhttps://www.blogger.com/profile/12686692441881140952noreply@blogger.comtag:blogger.com,1999:blog-9726833.post-37914336471097523472010-01-24T14:07:38.389+00:002010-01-24T14:07:38.389+00:00Hey Derek - my current catalog, mostly compressed,...Hey Derek - my current catalog, mostly compressed, is well over 100G on disk. On just one server. The replacement will consolidate some other backup systems, and add much data that's not backed up. I'm looking at 1TB uncompressed as a starting point, allowing for a little growth; and I regard our environment as small.Peter Tribblehttps://www.blogger.com/profile/09363446984245451854noreply@blogger.comtag:blogger.com,1999:blog-9726833.post-21206738578413337002010-01-24T03:07:42.983+00:002010-01-24T03:07:42.983+00:00Very cool idea. My backup background is with Tivol...Very cool idea. My backup background is with Tivoli Storage Manager, which uses a catalog/database for the same reasons. Instead of compressing, when TSM reaches the 100-150GB range, IBM tells you to setup a new TSM instance. Just curious -- how large can Netbackup catalogs get?delewishttps://www.blogger.com/profile/06588971532691351980noreply@blogger.com