I'm going to go out on a limb and say that it was related the the
"streams" file for that particular client. Creating a new policy must
have kicked NBU and cleared the situation.
-Tim
On Nov 18, 2005, at 1:33 PM, Piszcz, Justin wrote:
> The problem was fixed by duplicating the current policy and testing
> /boot and / separately then deleting that test policy and then doing a
> regular backup again and it was fixed.
>
> The netBackup tech was not sure what fixed it but he said there may
> have
> been some policy corruption somewhere .
>
> -----Original Message-----
> From: Mark.Donaldson AT cexp DOT com [mailto:Mark.Donaldson AT cexp DOT com]
> Sent: Friday, November 18, 2005 2:08 PM
> To: Piszcz, Justin; jamesp AT hisser DOT org
> Cc: veritas-bu AT mailman.eng.auburn DOT edu; Butts, Shawn
> Subject: RE: [Veritas-bu] Backups are not backing up /boot on RedHat ES
> Linux Release 4 with ALL_LOCAL_DRIVES??
>
> Do you have "Enable multiple streams" set on the policy?
>
> -----Original Message-----
> From: veritas-bu-admin AT mailman.eng.auburn DOT edu
> [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of Piszcz,
> Justin
> Sent: Friday, November 18, 2005 9:07 AM
> To: James Pattinson
> Cc: veritas-bu AT mailman.eng.auburn DOT edu; Butts, Shawn
> Subject: RE: [Veritas-bu] Backups are not backing up /boot on RedHat ES
> Linux Release 4 with ALL_LOCAL_DRIVES??
>
>
> # /usr/openv/netbackup/bin/bpbackup /boot
>
> This seems to work just fine.
>
> (using the User-Backup facility/policy/schedule)
>
>
> 11:02:28.676 [2651] <2> mount build_mount_list: INF - Processing (ext3)
> /dev/hda1 on /boot
> 11:02:28.681 [2651] <2> mount build_mount_list: INF - Processing (ext3)
> /dev/hda1 on /boot
> 11:02:28.682 [2651] <2> mount build_mount_list: INF - Processing (ext3)
> /dev/hda1 on /boot
> 11:02:28.682 [2651] <2> mount build_mount_list: INF - Processing (ext3)
> /dev/hda1 on /boot
> 11:02:28.683 [2651] <2> mount build_mount_list: INF - Processing (ext3)
> /dev/hda1 on /boot
> 11:02:28.683 [2651] <8> bpbkar SelectFile: WRN - /boot is in a
> different
> file system from /. Skipping.
> 11:02:28.683 [2651] <2> mount build_mount_list: INF - Processing (ext3)
> /dev/hda1 on /boot
>
> Skipping?!?!!?
>
> The policy is the same for all of the internal clients.
>
> ALL_LOCAL_DRIVES
>
> -----Original Message-----
> From: James Pattinson [mailto:jamesp AT hisser DOT org]
> Sent: Friday, November 18, 2005 11:02 AM
> To: Piszcz, Justin
> Cc: veritas-bu AT mailman.eng.auburn DOT edu; Butts, Shawn
> Subject: Re: [Veritas-bu] Backups are not backing up /boot on RedHat ES
> Linux Release 4 with ALL_LOCAL_DRIVES??
>
> That's strange, it works for me. Suggest you enable logging for bpbkar
> on the client machine, and it should walk the filesystems and tell you
> why it's not backing it up. I assume the policy is configured OK?
>
> James
>
> Piszcz, Justin wrote:
>
>> When I specify ALL_LOCAL_DRIVES, all that gets backed up is / and not
>> /boot?
>>
>>
>>
>> Why is this?
>>
>>
>>
>> $ df -h
>>
>> Filesystem Size Used Avail Use% Mounted on
>>
>> /dev/hda3 72G 4.6G 64G 7% /
>>
>> /dev/hda1 190M 8.4M 172M 5% /boot
>>
>> none 506M 0 506M 0% /dev/shm
>>
>>
>>
>> $ cat /etc/redhat-release
>>
>> Red Hat Enterprise Linux AS release 4 (Nahant Update 2)
>>
>>
>>
>> $ cat /etc/fstab
>>
>> # This file is edited by fstab-sync - see 'man fstab-sync' for details
>>
>> LABEL=/ / ext3
>> defaults 1 1
>>
>> LABEL=/boot /boot ext3
>> defaults 1 2
>>
>> #LABEL=/boot /boot ext3 defaults,nodev 1 2
>>
>> none /dev/pts devpts
>> gid=5,mode=620 0 0
>>
>> none /dev/shm tmpfs
>> defaults 0 0
>>
>> none /proc proc
>> defaults 0 0
>>
>> none /sys sysfs
>> defaults 0 0
>>
>> LABEL=SWAP-hda2 swap swap
>> defaults 0 0
>>
>> /dev/hdc /media/cdrom auto
>>
> pamconsole,fscontext=system_u:object_r:
> removable_t,exec,noauto,managed,n
> odev,nosuid
>> 0 0
>>
>> /dev/fd0 /media/floppy auto
>>
> pamconsole,fscontext=system_u:object_r:
> removable_t,exec,noauto,managed,n
> odev,nosuid
>> 0 0
>>
>>
>> --
>> This message has been scanned for viruses and
>> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and
> is
>> believed to be clean.
>
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>
> _______________________________________________
> 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
>
|