Just a quick how-to- make sure that you can install new Data Protector clients using SSH.
ISO, PXE, OBDR tape, USB or eSATA storage), a variety of network protocols (incl. IBM Tivoli Storage Manager, HP DataProtector, Symantec NetBackup, EMC. Its setup-and-forget nature removes any excuses for not having a disaster. Well with an rsync based backup that is pushed back to the backup client.
All this is done FROM the Linux the installation server, using the root user.
First of all, you have to copy the .omnirc-file if you have not done it before.
cp /opt/omni/.omnirc.TMPL /opt/omni/.omnirc
Then, edit the .omnirc file in /opt/omnic/ and make sure that OB2_SSH_ENABLED is set to “1”.
Then you need to make sure that the installation server can SSH to the client(s) without being asked for a password. If you do not have a SSH-key, you can generate one by running ssh-keygen.
Now copy your public key to the client(s) that you are going to install Data Protector on, by running ssh-copy-id root@<client>. Test it afterwards by SSHing to the client(s), if you do not get asked by a password, you are good to go!
PS: You have to SSH to the client at least once, as you will be asked to confirm the client certificate the first time.
Update 2017/01/09: After some discussions with colleagues… you need to know, that for Data Protector clients “systemd” is used and only on Cell Manager the legacy mode with “xinetd” is leveraged. Even with the legacy mode there is no need to change to “systemd”, as “xinetd” is supported on RHEL too.
There are Data Protector customers interested to use
systemd on RHEL 7, instead of xinetd . A colleague (Michael S.) sent a short how to with the required steps.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |