Solved!
Go to Solution1378
0
Posted October 8th, 2012 11:00
NETWORK deny everything is problem for Windows remote shell, for example WinRS -r:backupserver "savegrp test" does not work so is really needed deny all for NETWORK?
1378
0
Posted October 8th, 2012 11:00
Well, I don't need remote shell for savegrp to work - I wonder why you need it?
1378
0
Posted October 8th, 2012 11:00
What do you mean but what? Deny everything
1378
0
Posted October 8th, 2012 12:00
Ah, I see what your are doing. Why simply not start save from the client? Or if you are building a chain make cascaded group or even probe based backup.
1378
0
Posted October 8th, 2012 12:00
I need to start savegrp from other server than backupserver, for example:
serverA- production server with main script
serverB- Networker
so i need run savegrp on serverB after some actions done in main script
1378
0
Posted October 8th, 2012 12:00
>Why simply not start save from the client?
because data ready to backup created on ServerB after main script on ServerA makes some actions, I need start backup on ServerB from ServerA
1378
0
Posted October 8th, 2012 13:00
Reminds me of a guy who was trying to go cheap and avoid licenses
In your case I would explore world of probe based backups or cascaded groups.
danag2
20 Posts
1378
0
Posted October 10th, 2012 18:00
The default permissions are as listed in the screenshot. Just remove Network, the other explicetldy defined permissions will allow you to do what you need to do without adding to the ACL/DACL list.
P.S. What you are trying to do is one reason why savepnc functionality is built into Networker. We have Servers that executes scripts and dynamically build a list of what to backup. These scripts run on Server B agaisnt Server A.
We have Servers that run a local backup to disk of IIS and COTS applications before making a RPC call to another server to run its backup.