I don't know if you found an answer but I was looking to do the same thing. I ended up creating a batch file that does an if exists and returns 0. Then I created a role xml for File Servers that uses my custom script. When adding the role to a machine, you can change the variable of the test script to point to your share. I set mine to default to c$ so it will pretty much always pass by default so you should point it to your share. Hopefully this helps somebody else. I have a single Veeam server. If you have a more complicated environment this might not work depending on routing and stuff.
The batch looks for two arguments: "FSShare.bat 192.168.1.1 sharename" would test \\192.168.1.1\sharename
Old thread, I know....thank you Trent, I'll give it a try.
But again: It would be nice to have this feature integrated in Veeam, without using custom XMLs.
I personally believe that SureBackup is a really underestimated feature of Veeam. Is there any competitor in the backup market who can do something else?
We always tell our customers "you can have the best backup, but its nothing worth if you can't restore anything". Using the GUI with only a few clicks to test the entire environment (and I believe a fileserver is essential, like a dc, mail and sql is, too) would be really great!
I imagine you could use a net use command to map a drive and then remove it if you wanted to test accessibility. I personally just run chkdsk on them via psexec. Once you get the hang of how to do custom scripts for surebackup, it's not too much effort.
Hi all,
Please note that in V9 the custom XML files must be placed in Backup/SBRoles for B&R and in Console/SBROLES for the console itself (even if the console is installed on the VBR server)
Of course you'll have to copy each XML file to any additional remote console you'll set up.
jpverlande wrote:Hi all,
Please note that in V9 the custom XML files must be placed in Backup/SBRoles for B&R and in Console/SBROLES for the console itself (even if the console is installed on the VBR server)
Of course you'll have to copy each XML file to any additional remote console you'll set up.
It is a known issue for vanilla v9, that was fixed in Update1.
So if anyone will read it having v9 Update1 or above, placing xml in Backup\SBRoles is sufficient.
I added your script to my installation and wanted to implement it in my SureBackup Jobs.
Now I have the problem, that it always exits errorlevel 1 instead of 0.
The fileshares are existing, but the check cannot successfully verify that. Did others have the same problem and can tell me how to fix this?