Date: Wed, 19 Sep 2001 23:05:46 +0200 (SST) From: Peter Olsson <pol@leissner.se> To: "Thyer, Matthew" <Matthew.Thyer@dsto.defence.gov.au> Cc: <freebsd-questions@FreeBSD.org>, <freebsd-emulation@FreeBSD.org> Subject: Re: About HP OmniBack disk agent in FreeBSD Message-ID: <Pine.BSF.4.33.0109192254031.13568-100000@nic-i.leissner.se> In-Reply-To: <Pine.BSF.4.33.0109192158030.13568-100000@nic-i.leissner.se>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello again!
I noticed that if I backed up /export and then removed /export
completely it didn't restore to /export but to /usr/compat/linux/export.
I had to create /export to get it to restore there.
This got me wondering about the /usr/compat/linux structure.
I moved everything out of /usr/compat/linux and tried vbda.
I had to restore lib and etc in /usr/compat/linux to get it
running, but the rest don't seem to be needed! Which means that
I can now for example browse my real FreeBSD /usr. I am just now
running a complete backup of /usr to see what happens when I restore
some of the files in it. Should work fine as long as /usr exists.
I have no idea what this does to the linux support, it is probably
not so good if you use the linux support for other things than
omniback. I know nothing about linux, I just installed the linux
support to get the omniback client.
Peter Olsson
On Wed, 19 Sep 2001, Peter Olsson wrote:
> Solved it :) I have been trying for over an hour now so it is
> possible that I forgot something I changed earlier tonight, but
> I think this is the only thing I needed to get it working:
> cd /etc
> ln fstab mtab
>
> Now backup/restore works fine, and I can even browse my FreeBSD!
> The results of the browsing are unfortunately the contents of
> /usr/compat/linux, not the FreeBSD contents. But everything directly
> below / that doesn't have an equally named directory in /usr/compat/linux,
> for example /export, is browseable with real FreeBSD content!
>
> Here are my diffs for .util. I use .util from the A.04.00 release.
> It would probably be nicer to keep the use of uname for getting ARCH
> and OS_REV and instead changing the awk arguments, but this works:
>
> $ diff .util .util.old
> 16c16
> < ARCH=FreeBSD
> ---
> > ARCH=`echo ${UNAME} | awk '{print $1}'`
> 47,52d46
> < FreeBSD)
> < MACHINE=FreeBSD
> < OS_REV=4.3-RELEASE
> < SERIES=gpl/i386/freebsd
> < STRING="gpl i386 freebsd-${OS_REV}"
> < ;;
> 282,284d275
> < ;;
> < gpl/i386/freebsd)
> < /bin/df -t ufs 2>/dev/null | awk '$6 ~ /\/.*/ {print $6}'
>
> Peter Olsson
>
> On Wed, 19 Sep 2001, Thyer, Matthew wrote:
>
> > [cc'd to the lists for future reference for people wishing to run
> > Hewlett Packard OpenView OmniBack disk agent on FreeBSD]
> >
> > You are trying to do a lot more than me.
> >
> > I cannot browse, I have simply defined my datalist manually specifying
> > that I only want to backup the /export filesystem (dont choose from
> > the browse list but just type it in).
> >
> > I will be interested to see what mods you have made to
> > /usr/omni/bin/.util to be able to see the list of mounted filesystems.
> >
> > I dont do any browsing except when I am restoring, then I browse the
> > OmniBack database to choose what to restore but as far as I know, you
> > cannot browse the list of mounted filesystems or the files in them
> > when you are actually communicating with the FreeBSD box.
> >
> > I may well have run "brandelf -t Linux /usr/omni/bin/*" to make vbda
> > work.
> >
> > Compare the below with your system:
> >
> > % sudo file /usr/omni/bin/*
> > /usr/omni/bin/#inet: setuid setgid ELF 32-bit LSB executable, Intel 80386, version 1 (GNU/Linux), statically linked, stripped
> > /usr/omni/bin/cat_d: setuid setgid ELF 32-bit LSB executable, Intel 80386, version 1 (GNU/Linux), statically linked, not stripped
> > /usr/omni/bin/cat_e: ELF 32-bit LSB executable, Intel 80386, version 1 (GNU/Linux), statically linked, not stripped
> > /usr/omni/bin/echo_d: ELF 32-bit LSB executable, Intel 80386, version 1 (GNU/Linux), statically linked, not stripped
> > /usr/omni/bin/echo_e: ELF 32-bit LSB executable, Intel 80386, version 1 (GNU/Linux), statically linked, not stripped
> > /usr/omni/bin/fsbrda: ELF 32-bit LSB executable, Intel 80386, version 1 (GNU/Linux), statically linked, stripped
> > /usr/omni/bin/inet: setuid setgid ELF 32-bit LSB executable, Intel 80386, version 1 (GNU/Linux), statically linked, stripped
> > /usr/omni/bin/install: directory
> > /usr/omni/bin/obkbackup: ELF 32-bit LSB executable, Intel 80386, version 1 (GNU/Linux), dynamically linked (uses shared libs), not stripped
> > /usr/omni/bin/obkrestore: ELF 32-bit LSB executable, Intel 80386, version 1 (GNU/Linux), dynamically linked (uses shared libs), not stripped
> > /usr/omni/bin/omnigetmsg: ELF 32-bit LSB executable, Intel 80386, version 1 (GNU/Linux), statically linked, stripped
> > /usr/omni/bin/rbda: ELF 32-bit LSB executable, Intel 80386, version 1 (GNU/Linux), statically linked, stripped
> > /usr/omni/bin/rrda: ELF 32-bit LSB executable, Intel 80386, version 1 (GNU/Linux), statically linked, stripped
> > /usr/omni/bin/srun: ELF 32-bit LSB executable, Intel 80386, version 1 (GNU/Linux), statically linked, stripped
> > /usr/omni/bin/utilns: directory
> > /usr/omni/bin/vbda: ELF 32-bit LSB executable, Intel 80386, version 1 (GNU/Linux), statically linked, stripped
> > /usr/omni/bin/vrda: ELF 32-bit LSB executable, Intel 80386, version 1 (GNU/Linux), statically linked, stripped
> >
> >
> > Also ignore anything that gets redirected under /compat/linux as you'll
> > end up backing up the wrong stuff.
> >
> > % ls -l /usr/compat/linux/
> > total 10
> > drwxr-xr-x 2 root root 1024 Jul 26 15:15 bin
> > drwxr-xr-x 2 root root 512 Feb 7 1996 boot
> > drwxr-xr-x 6 root root 1024 Aug 24 10:45 etc
> > drwxr-xr-x 3 root root 2048 Jul 26 15:15 lib
> > drwxr-xr-x 4 root root 512 Jul 26 15:14 mnt
> > drwxr-xr-x 2 root root 512 Aug 24 1999 opt
> > dr-xr-xr-x 1 root root 0 Sep 19 14:40 proc
> > drwxr-xr-x 2 root root 512 Jul 26 15:14 sbin
> > drwxr-xr-x 17 root root 512 Jul 26 15:15 usr
> > drwxr-xr-x 13 root root 512 Jul 26 15:15 var
> >
> > So you wont get all of /bin, /boot, /etc, /lib, /mnt, /opt, /sbin,
> > /usr or /var backed up in the normal way with OmniBack.
> >
> > The solution to that problem is to set up your FreeBSD boxes as
> > file servers where all data is under /export. If you really really
> > want to backup the other filesystems, you can NFS mount them on a
> > Linux box and use OmniBack on that Linux box as OmniBack can be
> > used to backup NFS mounted filesystems. You could use on Linux
> > box to do all FreeBSD 'other' filesystems.
> >
> > e.g. mount freebie1:/ tux:/backup/freebie1/root
> > mount freebie1:/var tux:/backup/freebie1/var
> > mount freebie2:/ tux:/backup/freebie2/root
> >
> > Peter Olsson wrote:
> > >
> > > Hello!
> > >
> > > Sorry to disturb you. I need some help if you have the time.
> > >
> > > I had a working disk agent installed in a linux. I tarred /usr/omni
> > > and copied it to a freebsd. I got the freebsd imported as a client in
> > > our win2000 OmniBack Manager. After some hacking in /usr/omni/bin/.util
> > > to get a working df command I can see the mountpoints /, /usr and /var.
> > >
> > > When I try to browse down the directory tree it doesn't work. The command
> > > being run is "/usr/omni/bin/fsbrda -browse /usr" which doesn't seem to
> > > work in freebsd. After a while the result is "Cannot browse: invalid
> > > mountpoint". This is probably what you write about as the significant
> > > problem below?
> > >
> > > And when I choose for example to backup /var and I come to the
> > > final screen where the backup operation is made, it doesn't work
> > > either. vbda doesn't seem to understand freebsd.
> > >
> > > Have you had this problem and know what to do about it?
> > > >From your text below it seems you have been able to both browse and
> > > backup directory /export/home in freebsd. How did you do this?
> > >
> > > Is there anything I have to change under /usr/omni after copying it
> > > from the linux? (By the way, is changing .util the right thing to do?)
> > >
> > > Is there some way of setting up the mountpoints and directories statically
> > > for the freebsd client system in OmniBack win2000 Manager?
> > >
> > > Thanks!
> > >
> > > Peter Olsson
> >
> >
>
>
--
Peter Olsson Direkt: 0520-490 511
Leissner Data AB Växel: 0520-300 00
pol@leissner.se Fax: 0520-300 89
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.33.0109192254031.13568-100000>