I called tech support today, and was told I'm wasting my time doing indexing anyway. He said indexing is only useful if you're using Enterprise Manager. I don't believe we have Enterprise Manager. We only have one backup server.
It would be nice to know why I couldn't get it it to work with the user account I created, but I'm going to abandon it and just untick the option.
The option says:
"Creates catalog of guest files to enable browsing, searching and 1-click restores of individual files.
Indexing is optional, and is not required to perform instant file level recoveries."
Somewhere along the line I read that and made the assumption that I needed it. Probably because I was new to VBR, and didn't know what an "instant file level recovery" or a "1-click restore" was. I assumed I would need to browse and click to restore individual files, so therefore I would need a catalog. I ticked it, set the credentials for a Windows machine, did a test backup, then successfully tested restoring one file, so assumed I'd done the right thing. Then later I added Linux machines to the backup, and started seeing errors about indexing. When I tried to test FLR on a Linux backup, it asked awkward questions about nodes, etc, so I assumed it was falling back to some other method of accessing the file system.
Can I suggest that this be reworded to make this all clearer? Perhaps mention Enterprise Manager in the option description.
Finally, do I now have catalogs on my Windows servers taking up space unnecessarily? If so, what can I do about them?