Veritas-bu

[Veritas-bu] Linux - all filesystems are not being backed up

2004-03-02 18:15:31
Subject: [Veritas-bu] Linux - all filesystems are not being backed up
From: David Rock <dave-bu AT graniteweb DOT com> (David Rock)
Date: Tue, 2 Mar 2004 17:15:31 -0600
--PNTmBPCT7hxwcZjr
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* King, Cheryl <cheryl.king AT intrado DOT com> [2004-03-02 11:45]:
> I have some Linux clients that aren't backing up all file systems.=20
>=20
> Five clients are working as expected with all filesystems backing up
> everytime.

Are these schedules being backed up by the same policy, or by different
policies?

> One client backs up all file systems for the FULL but only / for the Cumm=
ulative Incrementals.

Check that there are no exclude_list files in /usr/openv/netbackup that
pertain to the Incrementals.

> One client backs up only / for the FULL and all file systems for the Cumm=
ulative Incrementals  The df -k command shows /

Ditto, but in reverse ;-)

> one client backs up /dev/shm    /dev/pts    /proc/bus/usb only all the ti=
me.  There's no actual data in any of those.  The df -k command shows /    =
  /boot      home     /dev/shm    /usr

USE an exclude_list file to tell NetBackup to not back up these
filesystems.

> They are all the same version.
> uname -a =3D Linux <client_name> 2.4.9-e.27smp #1 ...
> Has anyone seen this behavior? =20
>=20
> I remember seeing the command that gets run by NBU to determine what
> filesystem get backed up.  Does anyone know what that command is?  I'd
> like to test it.  Thanks.

bpcoverage

--=20
David Rock
david AT graniteweb DOT com

--PNTmBPCT7hxwcZjr
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFARRWTMrO4/Yb/xwYRAlSMAJ9bbMTF4G0sVpCGEXkTVl37/qO+VwCgphJj
gppu/sufa75XS8zdMdi8X3M=
=REx/
-----END PGP SIGNATURE-----

--PNTmBPCT7hxwcZjr--

<Prev in Thread] Current Thread [Next in Thread>