Veritas-bu

Re: [Veritas-bu] What do you do with old clients?

2008-03-06 14:38:57
Subject: Re: [Veritas-bu] What do you do with old clients?
From: Justin Piszcz <jpiszcz AT lucidpixels DOT com>
To: "Rosenkoetter, Gabriel" <Gabriel.Rosenkoetter AT radian DOT biz>
Date: Thu, 6 Mar 2008 14:12:15 -0500 (EST)
Filesystem and disk are good, it has even been migrated to a new array and 
have plenty of inodes available..  Thx for the suggestions.

Justin.

On Thu, 6 Mar 2008, Rosenkoetter, Gabriel wrote:

> That said, getting 41s while doing the image portion of a catalog backup
> probably speaks more to a problem with the file system or disk subsystem
> under /usr/openv/netbackup/db/images than it does about the number of
> inodes in use there...
>
>
> --
> gabriel rosenkoetter
> Radian Group Inc, Unix/Linux/VMware Sysadmin / Backup & Recovery
> gabriel.rosenkoetter AT radian DOT biz, 215 231 1556
>
>
> -----Original Message-----
> From: Bobby Williams [mailto:bobbyrjw AT comcast DOT net]
> Sent: Thursday, March 06, 2008 10:51 AM
> To: 'Justin Piszcz'; veritas-bu AT mailman.eng.auburn DOT edu
> Subject: Re: [Veritas-bu] What do you do with old clients?
>
> If there is not data left for the client and you don't back the client
> up
> any longer, delete the directory name.
>
> If this is the complete output of the clients image directory, it is
> empty
> and safe to be deleted.
>
> I have always seen that a client image directory is never deleted by
> NetBackup.
>
>
>
>
> Bobby Williams
> 2205 Peterson Drive
> Chattanooga, Tennessee  37421
> 423-296-8200
>
> -----Original Message-----
> From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
> [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Justin
> Piszcz
> Sent: Thursday, March 06, 2008 10:35 AM
> To: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: [Veritas-bu] What do you do with old clients?
>
>   Version: NetBackup 6.0MP5
> Directory: $install_path/netbackup/db/images
>
> bash-2.03# du -sh client-hostname.fqdn.com
> 20K     client-hostname.fqdn.com
> bash-2.03# find client-hostname.fqdn.com client-hostname.fqdn.com
> client-hostname.fqdn.com/1203000000
> client-hostname.fqdn.com/1203000000/tmp
> client-hostname.fqdn.com/1203000000/tmp/.lck
> client-hostname.fqdn.com/STREAMS.lck
> client-hostname.fqdn.com/STREAMS
> bash-2.03#
>
> Even after a cleanup, the old data persists:
>
> bash-2.03# /usr/openv/netbackup/bin/admincmd/bpimage -cleanup -client
> client-hostname.fqdn.com bash-2.03# du -sh client-hostname.fqdn.com
> 20K     client-hostname.fqdn.com
> bash-2.03# find client-hostname.fqdn.com client-hostname.fqdn.com
> client-hostname.fqdn.com/1203000000
> client-hostname.fqdn.com/1203000000/tmp
> client-hostname.fqdn.com/1203000000/tmp/.lck
> client-hostname.fqdn.com/STREAMS.lck
> client-hostname.fqdn.com/STREAMS
> bash-2.03#
>
> Even though this client contains no VALID (UBAK/UBAK.f) images the old
> garbage remains, and a bpimage -cleanup does not delete the directory.
>
> Has anyone come up with their own methods to cleanup the catalog or?
>
> I am trying to investigate why my catalog (sometimes/usually) times out
> with
> an error 41 and it occurs when its reading the images from
> openv/db/images,
> so.. that is why I am currently targeting this area.
>
> Justin.
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
>
>
>
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

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