[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cobalt-users] RE: Second drive in RaQ3i
- Subject: [cobalt-users] RE: Second drive in RaQ3i
- From: Johan-Kristian Wold <jkwold@xxxxxxxxxxx>
- Date: Fri May 26 02:38:51 2000
Howdy,
<snip>
At 23:26 -0700 23.05.2000 in cobalt-users digest, Vol 1 #845, David D wrote:
I had a disastrous experience last week while using the RaQ3's built-in backup
utility (e.g., it didn't work and failed miserably during restore). So I
checked the Cobalt web site and user archives on Arkeia and Legato to see what
else was available and being used. We basically just wanted to find a solution
that allows a similar backup as the built-in utility to allow a backup then a
download from the RaQ3 server to a local Windows based PC (nothing fancy).
<snip>
My sympathies - discovering the backup system can't recover is not a
fun experience...
We're using Legato to backup our single NASRaQ (as well as some
solaris boxes and our Oracle database server).
Getting the built-in Legato client (on the NASRaQ) required some
trial and error. I posted an article about it, but for some reason it
didn't show up in the archives ? I have included a repost of the
article below.
As for a second drive, there was some articles on it on this list a
while ago - I sugest you search the archives...
Anyway - here is how I got Legato to work:
IANAE (I Am Not An Expert), but here's an attempt to describe how I
did it, with a bit more info on Legato as well:
(I am not a Lawyer either, but follow these instructions on your own
risk as well... :^)
Setting up Legato Networker on the Cobalt NASRaQ
General about Legato:
Legato Networker uses a client/server model, consisting of clients,
one or more backup servers, and storage nodes. I'm not going to cover
the initial setup of the server(s) and storage node(s), since this is
covered in the Legato documentation.
A computer can be client, server, storage node, a combination or all three.
Currently, Legato Networker is only available for Linux (and
therefore Cobalt) as a client. You'll need to set up either a Unix, a
VMS or an NT backup server.
A list of what's available on what platform can be found on
<http://www.legato.com/Products/html/software_cg.html>
Licensing
The licensing system in Legato, differentiates between the operating
system of the clients. Whenever you want to add a new type of client
OS, you'll have to purchase a ClientPak for that kind of OS. The
ClientPak includes licenses for up to 10 clients. Additional clients
can be purchased one by one, or in larger volumes. If you have an NT
server and want to backup Unix boxes, you need a ClientPak for NT. If
you have a Solaris server and want to backup a different unix type
(such as a Cobalt box), you'll need a ClientPak for Unix. If you have
a Solaris server, and want to back up a Linux machine and an Irix
machine, you'll only need one ClientPak for Unix, though.
This means, that unless you have a ClientPak for Unix already, you'll
have to license a ClientPak for Unix. This is a fairly expensive
option, costing around NOK 17 500,- at the time of writing. This will
enable you to backup up to 10 clients, before you'll have to buy more
licenses.
There are three variants of the Legato networker server: Workgroup,
network and Power edition. There are limits on what kind of options
you can add to each of them, so you'll want to check with your Legato
reseller on what server you need, in order to be able to add the
ClientPak.
Whether you want to use an NT server or a Unix server is up to you -
We have a Solaris box as our primary file server, so this is what I
use for a backup server. (Actually, when you need to dig in the OS
innards, I find it easier to dig in Unix entrails, than NT
entrails...:^)
Setup
This setup assumes a Unix backup server. Check chapter 5 of the
Legato administrator guide for details on setting up other servers.
Here, I've called the server "Ultron" and the Cobalt "Magneto". The
server resides at 192.168.1.13 and the cobalt resides at 192.168.1.48
- fill inn the appropriate values for your own network here...
You must telnet to the machines as root to do most of this. If you
haven't done any Linux/unix work before, you should seriously
consider getting some help from somebody that nows a bit about
Linux/Unix before you attempt this...
- In the web interface on the Cobalt, check that the Legato service
has been enabled.
- Check that the cobalt and the server sees each other by pinging
between them - both from the cobalt to the server, and from the
server to the cobalt.
- Add the Cobalt to the /etc/hosts file on the server:
127.0.0.1 localhost
192.168.1.13 Ultron loghost
192.168.1.48 magneto
- Add the server to the /etc/hosts file on the Cobalt:
127.0.0.1 localhost
192.168.1.48 magneto.nortrykk.no magneto # main interface
192.168.1.13 ultron.nortrykk.no ultron nsrserverhost nsrhost
(Note the aliases "nsrserverhost" and "nsrhost")
- In /nsr/res on the Cobalt, modify the "servers" file, so that it
identifies the backup server (nsrhost and nsrserverhost should be
there too):
ultron.nortrykk.no
ultron
nsrhost
nsrserverhost
- Check what the Cobalt identifies itself as, by calling hostname:
[root@magneto /]# hostname
magneto.nortrykk.no
Now you are ready to add the client to the server:
- In Legatos administrative interface on the server, use "manage
clients", and select "Create".
- You must name the client exactly the same as what hostname
reported. In the example above, the client name should be
"magneto.nortrykk.no"
- Set the client up with "Unix standard directives" at first - this
can be modified at a later date.
- Assign it to your regular backup group. (I use "Default").
- Assign aliases. I have assigned it the following aliases
magneto
magneto.nortrykk.no
Checking if it works
Telnet to the Cobalt as root and try the following ("ultron" should
be replaced by the name of your backup server):
save -s ultron /etc/rd.d
The Cobalt should chew on that a bit, while contacting the server.
After a while, you should get a report on what files is backed up. If
it does absolutely nothing in, say, 5 minutes or so, you'll need to
do some debugging:
Debugging
If the save command fails, you may need to check the portmapper:
- Telnet to the server and do a "rpcinfo -p <client name>"
- Telnet to the Cobalt and do likewise against the server:
rpcinfo -p <server name>
If any of these returns an error, you should try to enable the portmapper:
-If the server can't see any rpc services on the cobalt, telnet the
cobalt and check what the portmapper boot script is called:
ls /etc/rc.d/init.d
- If you can find a file called portmap:
ln -s /etc/rc.d/init.d/portmap /etc/rc.d/rc3.d/S11portmap
- if you instead find a file called portmap.init, do:
ln -s /etc/rc.d/init.d/portmap.init /etc/rc.d/rc3.d/S11portmap.init
- reboot the cobalt, by running "reboot".
- Test the "save" command anew.
Further checking
Now, let the regular automatic scripts run, and see if it will do an
automated backup at night. If it does, everything should be all right.
If the "save" test worked at once, and the automated one didn't,
check the portmapper as described above. (manual saves are initiated
from the client, while automated ones are initiated from the server)
Automated backups
Are the basis of Legato. Automated backups are don by setting up
Groups and schedules, and assigning clients to the groups.
Manual backups
Are started on the client (i.e. the cobalt). Use the "save -s <backup
server name> <directory or file name>" command to do this.
A short description on save can be found in the man pages.
Restores
- can be done by running "recover -s <backup server name>" on the
Cobalt. This must be done via telnet. Recover is an interactive
utility.
Do "man recover" for a description on how to use it. You may also use
"?<enter>" on recovers command line.
I'd reccomend testing a restore of a couple of files before I'd call
it up and running.
A note to mac users:
The Appletalkshares on the Cobalt must be treated with a bit of
respect, or you'll cripple your files doing save/restore. Every
directory on an Appletalk svare contains a directory called
".AppleDouble". This directory contains the resource fork of the
files in that directory. If you are saving or restoring a Mac file,
be very sure to include the resource fork as well.
Reccomended reading
Chapter 5 of Legatos Administrators guide
Legato Whitepapers at
<http://www.legato.com/documents/papers/Whitepapers.html> - "Setting
Up Schedules & Policies for Legato NetWorker" and others.
I hope this will help anyone in trouble...
Give me a note if this has been of any help.
Sorry for the lengthy post... ;^)
Kind regards
Johan-Kristian
--
Johan-Kristian Wold, M.Sc. |
Computer systems administrator | Recursive: Adj. See recursive.
Nor-Trykk Narvik AS |
jkwold@xxxxxxxxxxx | SAM007HM02