UNSOLVED
A
antoineschokker
1 Rookie
•
70 Posts
0
1047
April 8th, 2009 01:00
Remote Installationfor (new) Networker Clients
To make sure not to Hi-jack the thread
https://forums.emc.com/forums/thread.jspa?threadID=114101
I started this thread.
The discussion is: Is an Remote Installation option (other than the NSRPUSH) an hugh improvement for Networker. Specialy for new clients?
I think it is, but Hrvoje states that it would be an potential security issue.
Why do you think that Hrvoje?
I´ve worked a while with HP Dataprotector and the way they created an Remote Installation was an releave for me.
Please feel free to participate....
Is Networker able to push to new clients or just to
push an update to already known clients?
I started this thread.
The discussion is: Is an Remote Installation option (other than the NSRPUSH) an hugh improvement for Networker. Specialy for new clients?
I think it is, but Hrvoje states that it would be an potential security issue.
Why do you think that Hrvoje?
I´ve worked a while with HP Dataprotector and the way they created an Remote Installation was an releave for me.
Please feel free to participate....
What i did love about the upgrade was the ability
to
push the client packes out to the clients from the
server.
to
push the client packes out to the clients from the
server.
Is Networker able to push to new clients or just to
push an update to already known clients?
Update only (if talking about about nsrpush).
That's something I think EMC has to improve.
It would be such an timesaver if it was possible to push client-software to new > > client.
It would be such an timesaver if it was possible to push client-software to new > > client.
Yes and no. It would be easier, but it would be also potential security issue that >in enterprise environment I would not allow. I believe with Windows you could use >RIS and with UNIX systems creating scripted package and deploying it with ssh >could do the trick.
ble1
6 Operator
•
14354 Posts
•
56186 Points
155
0
Posted April 8th, 2009 02:00
We have backup server A and then client's B, C....Z. And they are Window, Solaris, AIX, HPUX, MacOS, etc... mixed environment.
From development point of view, the easiest way is to either:
a) use native OS tool or 3rd party tool (might not be possible)
b) use application to do the task (requires agent already installed and this is what we have currently)
You are after a). To get to the box you require admin user/pass to be passed over the network or from some repository to connect to the box and pass the package. Then this package needs to be executed and installed in one of following ways:
a) default installation (no questions asked)
b) custom installation according to conf file from the package
To pass the package from server or repository that way you pass your user/password across the network. So probably you need ssh for that. On Windows you do not have it while on most UNIX boxes might be there, but default setup or company policy might disallow using root for that. To change that you need to go to client to either install ssh package or modify setting - while there why not install NetWorker anyway
So, due to security restrictions, many environment do NOT allow root usage even over ssh. Period. Actually, if you wish to log as root the you either connect via some user and the do su/sudo things or connect to machine via console. Of course, you may wish to for that case use specially created user, but while there you could also install NW (of course you could use user via LDAP and etc etc... but the point is there). Obviously if those would not be your concerns that you can do it. We mostly use ignite/yum and similar to push what we need from repository (on UNIX) and that keeps us happy.