I want to understand to what extent I can trigger backups on the client side.
Client-side CV software includes Q commands but does that mean I can, for example, run ON THE CLIENT :
# qlogin -cs <blah> -u <user>
# qoperation execute <details>
THis is for SQL server. Customer wants to trigger backups only after daily DB maintenance is completed - but the time that will complete may tend to vary.
I see that this iData agent does support qoperations. I see also that we can integrate into SQL Management studio but that will not be hapening here.
Assuming that I can give control to the client, I need to be sure of the security. This is a multi-tenanted, utility backup service and just one end-customer wants to do this. I cannot risk other customers.
I can lock it down with a service user on the Commserve and define the associated entities for that user. I can provide the specifics to the customer in a template file plus download the script from the CC console but the client would in principle be able to mod those, if they knew what they were doing. How else could I constrain the customer?
At some point we will deploy a self-service portal but again, right now, I am looking for a quick - but safe - solution.