I’m in process of replacing a couple of Windows based Commvault A600 media agent appliances with Linux based media agents that are virtualized. We downsized greatly and our backup needs are a lot smaller, plus the A600s are now EOL.
I’m trying to gather all best practices for configuring the Linux MA, specifically regarding disk parameters (size, blocksize, alignment,etc.). The A600s were originally built by an automated setup process built by Commvault out of box. I’m doing this all manually for the new build.
My current MA houses about 10TB of data, which works out to an app size of about 45TB. My DDB currently consumes about 30GB on disk. Our needs will likely decrease over time vs increase.
I plan to provide a single 12TB volume (64KB block size) for the library content and about a 100GB single volume (4KB block size) for the dedupe database.
Is this OK? The A600 is currently able to provide 150TB and the setup created multiple 9TB volumes for the content library. I don’t know why, exactly. Is 9 a magic or max number? Is 12 above too much? Should I do smaller?
Are my block sizes OK? Commvault is currently configured for 128KB block sizes on top of the OS defined 64KB blocks on the existing library. I assume that’s OK to persist?
Anyway looking for any guidance, especially in the realm of Linux as I’m primarily a Windows guy.
Best answer by Prasad NaraView original