Il 24/01/2012 11:18, Xabier Elkano ha scritto: > El 24/01/12 10:49, Marcello Romani escribió: >> Il 24/01/2012 10:05, Xabier Elkano ha scritto: >>> El 23/01/12 16:28, Uwe Schuerkamp escribió: >>>> DB Size: >>>> Total clients: 107 Total bytes stored: 34.41 TB >>>> Total files: 47495362 Database size: 31.64 GB >>> Hi Uwe, >>> >>> I am having the same problem, backups are fast, but restores takes too >>> long creating directory tree with bat. I have a lot of files to backup >>> per client. I am using mysql with innodb engine, my File table is about >>> 17GB on disk. >>> >>> My numbers: >>> >>> BytesPerJobAvg: 6539156346 >>> ClientCount: 31 >>> FileCount: 113286836 >>> FileRetentionAvg: >>> FilenameCount: 29713190 >>> FilesPerJobAvg: 184213 >>> JobRetentionAvg: >>> PathCount: 6671143 >>> TotalBytes: 1588763249151 >>> TotalFiles: 44919364 >>> >>> First, I considered to create more bacula servers to separate clients on >>> diferent databases, but now I am testing a configuration with one >>> catalog per client. With this config, each client goes in separate db, >>> It's more difficult to administer and setup it but I guess is the best >>> way to scale the platform. Has anyone tried this config? >>> >>> Sorry for my bad english. >>> >>> Xabier >>> >>> >>> ------------------------------------------------------------------------------ >>> Keep Your Developer Skills Current with LearnDevNow! >>> The most comprehensive online learning library for Microsoft developers >>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, >>> Metro Style Apps, more. Free future releases when you subscribe now! >>> http://p.sf.net/sfu/learndevnow-d2d >>> _______________________________________________ >>> Bacula-users mailing list >>> Bacula-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/bacula-users >> You mean 31 catalogs ?! >> > > Yes, now, I am only testing with two catalogs and it's working Ok, what > are the downsides using this config? > According to the documentation bacula supports it: > > " The Catalog Resource defines what catalog to use for the current job. > Currently, Bacula can only handle a single database server (SQLite, > MySQL, PostgreSQL) that is defined when configuring*Bacula*. However, > there may be as many Catalogs (databases) defined as you wish. For > example, you may want each Client to have its own Catalog database, or > you may want backup jobs to use one database and verify or restore jobs > to use another database." > > > > ------------------------------------------------------------------------------ > Keep Your Developer Skills Current with LearnDevNow! > The most comprehensive online learning library for Microsoft developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-d2d > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users
I'm just thinking out loud, but I don't see how having a catalog for each client can help you scale, since you can't put them on different db servers. You'd probably have a higher ROI by upgrading the DBMS hardware and/or migrating to postgres and/or throwing some (consultancy) money at tuning. Just my 2 cents. -- Marcello Romani ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
