Skip to main content
Answer

What is the best practice to backup millions of voice recording with Commvault.

  • August 25, 2021
  • 2 replies
  • 451 views

What is the best practice to backup millions of voice recording with Commvault.

Best answer by Damian Andre

Jumping ahead from @Mike Struening‘s questions, since the voice recordings should stay static, I’d say use a regular file system agent in regular mode with a bunch of streams. The first backup will obviously take much longer, but incrementals should be much quicker. If you are on a more recent feature release, larger files will be backed up automatically with multiple streams (file extent backups).

Alternatively, if that first backup is simply taking too long, you can enable block level backups which skips much of the scan phase and file/open/close API which should improve performance at the sacrifice of granular restore performance (although much faster if you restore an entire disk).

2 replies

Mike Struening
Vaulter
Forum|alt.badge.img+22

Hey @BrianSiphelele , great question!  First, we’ll need to know a few things….are these flat files?  Where do they exist (on a filer, windows server, etc.)?  How often are they accessed?  What is their size (total and per record)?

The initial answer would be to just back them up as flat files via the OS based Agent (i.e. the Windows File System iDA).  However, if they are on a filer, there may be a better option.


Damian Andre
Vaulter
Forum|alt.badge.img+22
  • Vaulter
  • Answer
  • August 25, 2021

Jumping ahead from @Mike Struening‘s questions, since the voice recordings should stay static, I’d say use a regular file system agent in regular mode with a bunch of streams. The first backup will obviously take much longer, but incrementals should be much quicker. If you are on a more recent feature release, larger files will be backed up automatically with multiple streams (file extent backups).

Alternatively, if that first backup is simply taking too long, you can enable block level backups which skips much of the scan phase and file/open/close API which should improve performance at the sacrifice of granular restore performance (although much faster if you restore an entire disk).