From: Beerse, Corné (c.beerse@torex-hiscom.nl)
Date: Fri Mar 28 2003 - 10:54:50 EST
I asked something direct to Thomas while trying it out myself. I like to add
some of that here too, for your info.:
> > > That will shutdown the OmniBack daemons on the Unix server, prevent
them
> > > from starting up again, and make it available to be imported into
another
> > > OmniBack cellserver.
> > >
> > > Now, on the Windows server, select "Import Client" and enter the name
of the
> > > HP-UX server. It will probably prompt for the root password. You then
will
> > > need to add it to the list of installation servers.
>
> > By adding a client, I also need to add the software distribution, Isn't
it a
> > problem if that's the same machine? Do I need to install any software?
Would
> > that overwrite the source and hence byte me in the nose/tail?
>
> The important difference is to "Import" the HP-UX installation server, not
> "Add" it. The "Import" will query the candidate system to determine what
> has already been installed. It doesn't automatically find the
installation
> services, however, so you need to go to that tab in the GUI and "Add" the
> HP-UX system. Unlike the "Client" tab, this will not attempt to install
> anything, just fill out the properties for the new Install server.
I did not think about it and just added the distribution-server (and old
cellmanager) to the new cellmanager. Yep, I used the `add new client`
option, not the import. I have the next reason to believe it should not
harm:
The installation server is an other process and uses other datasets
(software depots) than the software it installs. The software is installed
form genuine HP-UX depots (same format is used for all unix variants, at
least for storage). So the software will not overwrite itself.
And for installation the rcp and remsh tools/protocols are used not the
omniback tools/protocols. It can be an other protocol but it is definitly
not omnibacks own to avoid chicken and egg problems, and it asks for
username and password if the ~/.rhosts file for root is not set for the
backup server.
CBee
--
C. Beerse
mailto:c.beerse@torex-hiscom.nl <mailto:c.beerse@torex-hiscom.nl>
talkto:+31(71)5256660
-----Original Message-----
From: "Beerse, Corné" [mailto:c.beerse@torex-hiscom.nl]
Sent: vrijdag 28 maart 2003 15:29
To: 'maillist HP-UX-admin'
Subject: [HPADM] summary: OmniBack: from 2 to 1 cellmanager.
Thanks to Thomas V. Myers:
Disable the cell manager for now: `/sbin/init.d/omni stop`. This only
disables the cell manager, things like software distribution, backup and
other stuff initiated from an other instance are started from inetd.
Disable the cell manager after future reboots: `/usr/sbin/ch_rc -a -p
'OMNI=0'`. This prevents the cellmanager to be started from
`/sbin/init.d/omni start`. And I found out, it also prevents the cellmanager
to be stopped with `/sbin/init.d/omni stop` so the order is important here.
Next remove the current cell setting: `mv /etc/opt/omni/cell/cell_server
/etc/opt/omni/cell/cell_server.prev`
Now the machine can be added to an other cell. For this it is (unfortunate)
required to install software like device or media agent but only one is
required. The cell will recognize already installed software so there is no
need to install all.
btw: I tested the above by doing so. I will see next monday if the resulting
situation realy is capable of making backups (and restores). If problems
arize, I will update this summary.
Most other responces where kind of like remove the cellmanagers software.
Unfortunatly, from the media I have, I cannot 'just remove the cellmanager',
It removes all omniback software from the system, leaving me with a chicken
and egg problem for not having a machine that distributes the software.
Some other responces where to install the 'Manager of Cell Managers'.
Licensing prevents me from doing this. An other problem would be that only
the HP-UX machine with the obsolete cellmanager was avaliable to do so,
hence leaving me an other challence.
CBee
--
C. Beerse
mailto:c.beerse@torex-hiscom.nl <mailto:c.beerse@torex-hiscom.nl>
talkto:+31(71)5256660
-----Original Message-----
From: "Beerse, Corné" [mailto:c.beerse@torex-hiscom.nl]
Sent: donderdag 27 maart 2003 18:06
To: 'maillist HP-UX-admin'
Subject: [HPADM] OmniBack: from 2 to 1 cellmanager.
HP-OmniBackup: how to move from 2 cellmanagers to 1 cellmanager.
We started OmniBackup to backup our M$Windows machines. This M$Windows based
cellmanager is hooked to a tape robot (24 SuperDLT tapes in 2 racks: roughly
24 * 320 GByte). That leaves room to backup the unix (linux, sco and HP-UX)
machines too.
SO I installed the unix software to a HP-UX box to distribute the unix
software from there. I also made this machine a cellmanager to be able to
test/try settings while the other cellmanager is operational.
Currently I've moved several unix boxes to backup to the M$Windows based
cellmanager, all operational. Unfortunatly, In the M$Windows based
cellmanager, I cannot create the client for the HP-UX box that hosts the
test-cellmanager. How do I do this?
I know I can uninstall the cellmanager but that also removes the software
distributor for the unix software so I cannot re-install it from the
M$Windows based cellmanager. (The M$Windows based cellmanager cannot
distribute unix softare)
Should I hack my way around in the settins of both cellmanagers?
Can I disable/uninstall the HP-UX based cellmanager?
WHo has an IDEA?
CBee
--
C. Beerse
mailto:c.beerse@torex-hiscom.nl <mailto:c.beerse@torex-hiscom.nl>
talkto:+31(71)5256660
--
---> Please post QUESTIONS and SUMMARIES only!! <---
To subscribe/unsubscribe to this list, contact majordomo@dutchworks.nl
Name: hpux-admin@dutchworks.nl Owner: owner-hpux-admin@dutchworks.nl
Archives: ftp.dutchworks.nl:/pub/digests/hpux-admin (FTP, browse only)
http://www.dutchworks.nl/htbin/hpsysadmin (Web, browse & search)
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 11:02:28 EDT