nas share ownership

[bkain1]

I'm having a multiprotocol NAS set up, for my V1 alarms (10a, if it matters) to be written to, to be picked up by a process which sends them to a ticketing system, and I have what is probably a dumb question. I bring up V1 monitor, as my user id, in the services, the 3 V1 processes "run as" fordna1\veeamProxy, what group or id has to own (or at least be in a group of) that NAS share? (I'm really not a windows person).

thanks

becki kain

[HannesK]

Hello,
are you talking about the reporter? https://helpcenter.veeam.com/docs/one/r ... ml?ver=110

The path must refer to an existing folder. Veeam ONE will check if the specified folder exists and if the account under which Veeam ONE Reporting service runs has write permissions on the folder. If the folder cannot be accessed, Veeam ONE Web Client will display a warning message.

services.msc -> scroll to Veeam ONE Reporting service -> check the user

Best regards,
Hannes

[bkain1]

no, we're writing a powershell script as a "notification", with the 7 variables provided. Right now, I'm writing it locally, on the V1 box, but at some point, i have to write these alarm to a NAS drive, which will be shared with a linux box. I assume the proxy account that is the "run as", in V1 services, has to be in a FIM/AD group that owns that NAS drive, not my personal account?

[HannesK]

in Windows Server 2019 services.msc the column is called "Log On As", but I assume that we talk about the same. That account needs write permissions. There is no need to "own" the share / folder. Write permissions are good enough.

just because I'm interested... what is a FIM group?

[bkain1]

i have no idea. i was just told that a name

[wishr]

Hi Becki,

Have you managed to sort this out?

Thanks

[bkain1]

Yes, in theory. I'm still waiting on the NAS share to be created so I can try it with the "run as" account that I use in V1. Thank you

[wishr]

Great! Please let us know if any help is required.