VBRcatalog placement and protection

[bcravn]

Hi!

As we are beginning to embrace the malware scanning feature using the fileindexing on more and more customers. We are looking into the placement of the VBRcatalog folder. In the past is has been placed in the same drive as used for repo (protected by different kinds of raids) but on mechanical drives.
We do, however, have a ssd based cache drive, used for instant restores and such. And random IOs would be a lot better, than the repo with spinning disks.. But the cache location is not protected by any raid levels. So in case of a failure, the cache will just be replaced.

So, my question is: Would it make sense to move the VBRcatalog folder to a fast SSD ? And in case of a failure, just let re-create the indexes and move on ? And would we really "loose" ? beside perhaps the option to know about where a file was place a month ago for file level restore in the enterprise mananger.

[david.domask]

Hi Bjarke,

There's some logic to it, and in fact it's the current standing recommendation to place it on SSDs. So the idea is sound, but to be clear, if you're not seeing any slowness or problems with having it on spinning disks, then probably there's nothing to worry about, but SSD for the Catalog is a standing recommendation.

But continuing the Catalog in the event that you lose the disk hosting the Catalog should be as simple as just replace the faulty SSD and run another job that utilizes indexing, and you can just protect the Catalog folder with for example an Unstructured Data Backup job.