Re: [Veritas-bu] Change in NDMP level backups between 6.0 and 6.5?

[A Darren Dunham]

On Tue, Dec 15, 2009 at 11:22:28AM -0700, Patti Anderson wrote:
> 
> What version of 6.5 are you running?  I see this behavior reported under
> ET1435435 and resolved at 6.5.3.1 and 6.5.4.
> Upgrading to 6.5.4 should resolve the issue.

Ah, so just a bug (whew).  Yes, the two places I checked with this behavior are
6.5.3.  I have a 6.5.4 system that's just about to get an NDMP server,
so I can verify the fix there.  

Thank you!!

-- 
Darren
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

[Veritas-bu] NDMP to basic disk

[Spearman, David]

It was my understanding (and it was also noted in a Veritas white paper) that 
one could do an NDMP backup to basic disk starting with 6.5.2. We are running 
6.5.3 and will probably jump to 6.5.5 soon. Unfortunately when I try nothing 
happens. No error messages, no failures. Everything looks fine, the log says 
the job is writing, unfortunately not a single byte is ever written. The job 
just sits there forever until manually killed. Any thoughts? 

David Spearman
County of henrico
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Change in NDMP level backups between 6.0 and 6.5?

[Patti Anderson]

 
Hi,

What version of 6.5 are you running?  I see this behavior reported under
ET1435435 and resolved at 6.5.3.1 and 6.5.4.
Upgrading to 6.5.4 should resolve the issue.

Patti

-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of A Darren
Dunham
Sent: Tuesday, December 15, 2009 11:09 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Change in NDMP level backups between 6.0 and 6.5?

Posted this on the Symantec forums, but didn't have any nibbles yet, so
I'm asking here as well.

NDMP (or at least the netapp implementation of it) doesn't have the
concept of a true incremental.  I'm used to this being somewhat "faked"
by increasing the level numbers.  On my filers I can see that the level
numbers increase.  This is in a 6.0 environment.
 
Day 1 Full  - level 0
Day 2 Diff Incr - level 1
Day 3 Diff Incr - level 2
Day 4 Diff Incr - level 3
and so on...
 
But I just checked some machines in a 6.5 environment, and I don't see
this pattern.  Instead:
 
Day 1 Full  - level 0
Day 2 Diff Incr - level 9
Day 3 Diff Incr - level 9
Day 4 Diff Incr - level 9
and so on...
 
Is this a change between 6.0 and 6.5, or is something else happening?
Any way to get back the old behavior?  This do-level-9-for-incr-backups
uses more tape.  

Thanks!

--
Darren
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

[Veritas-bu] Change in NDMP level backups between 6.0 and 6.5?

[A Darren Dunham]

Posted this on the Symantec forums, but didn't have any nibbles yet, so
I'm asking here as well.

NDMP (or at least the netapp implementation of it) doesn't have the
concept of a true incremental.  I'm used to this being somewhat "faked"
by increasing the level numbers.  On my filers I can see that the level
numbers increase.  This is in a 6.0 environment.
 
Day 1 Full  - level 0
Day 2 Diff Incr - level 1
Day 3 Diff Incr - level 2
Day 4 Diff Incr - level 3
and so on...
 
But I just checked some machines in a 6.5 environment, and I don't see
this pattern.  Instead:
 
Day 1 Full  - level 0
Day 2 Diff Incr - level 9
Day 3 Diff Incr - level 9
Day 4 Diff Incr - level 9
and so on...
 
Is this a change between 6.0 and 6.5, or is something else happening?
Any way to get back the old behavior?  This do-level-9-for-incr-backups
uses more tape.  

Thanks!

-- 
Darren
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] EXT4 Filesystem

[Ed Wilts]

On Tue, Dec 15, 2009 at 8:50 AM, Matthew Opoka  wrote:

> Does anyone know offhand if EXT4 filesystem is supported in Netbackup 6.5?
>

The supported operating systems and file systems are documented in the
compatibility documentation.  Without looking it up, I would expect that
basic backups and restores will work.  I would expect that extended
attributes or ACLs may or may not.  FlashBackup is extremely unlikely to
work.  Those are my guesses but if ext4 is important to you, look it up in
the official compat docs.

   .../Ed

Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE
ewi...@ewilts.org
Contact Me Linkedin 
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

[Veritas-bu] EXT4 Filesystem

[Matthew Opoka]

Does anyone know offhand if EXT4 filesystem is supported in Netbackup 6.5?

Regards,

Matthew


  ___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Veritas Netbackup Report Status by each mount point.

[Bluejay Adametz]

The korn shell script below may help. It's rather resource-heavy as it has 
to go through the catalog and add up what was backed up from under which 
mount points, and produces something that looks like:

# ./bu_by_filesystem fred
Tue Dec 15 07:34:43 PST 2009 Collecting file system information
Tue Dec 15 07:34:55 PST 2009 Client is standard
Tue Dec 15 07:34:55 PST 2009 Identifying last full backup
Last full backup is from 12/11/2009 20:00:07 to 12/11/2009 20:00:07
Tue Dec 15 07:34:58 PST 2009 Scanning catalog...

 / backed up3,164,446k bytes,   105306 
files
 /boot backed up4,396k bytes,   24 
files
 /database backed up  204,800k bytes,5 
files
  /dev/pts backed up0k bytes,1 
files
  /pbx backed up  800,275k bytes,  884 
files
  /proc/sys/fs/binfmt_misc backed up0k bytes,0 
files
  /sys backed up0k bytes,1 
files
   /var/lib/nfs/rpc_pipefs backed up0k bytes,6 
files
/var/named/chroot/proc backed up0k bytes,0 
files
/var/named/chroot/var/run/dbus backed up0k bytes,1 
files

4,173,918k bytes, 106228 files total

Tue Dec 15 07:35:23 PST 2009 Complete.
#

Here's the script itself. It could probably be implemented in perl or 
something to be more efficient, but maybe this will give you some ideas.

#!/bin/ksh

# Report the amount of stuff backed up by file system

# Validate parameters
if [[ "$1" = "" ]] ; then
   echo "Usage: $1 [client|backupid]"
   exit 1
fi

if [[ $1 = *_* ]] ; then
   # User specified a backup id
   CLIENT=`echo "$1" | cut -d _ -f 1`
   BUDATE=`echo "$1" | cut -d _ -f 2`
else
   CLIENT=$1
   BUDATE=""
fi

# Identify the file systems on the client

echo `date` Collecting file system information >&2
bpcoverage -c $CLIENT | awk '
BEGIN { FOUND_DRIVES=0; }
$0 == "" { FOUND_DRIVES=0; }
FOUND_DRIVES == 1 && substr($1,1,5) != "-" {
   P=substr($0,1,PATHEND-1);
   while ( P != "" && substr(P,1,1) == " " ) P=substr(P,2);
   while ( P != "" && substr(P,length(P),1) == " " ) 
P=substr(P,1,length(P)-1);
   print P;
}
( $1 == "Drive" && $2 == "Letter" ) || ( $1 == "Mount" && $2 == "Point" ) 
{
   FOUND_DRIVES=1;
   PATHEND=index($0,"Device");
   if ( PATHEND == 0 ) PATHEND=index($0,"Backed Up By Policy");
}
' >/tmp/bu_by_filesystem_$$.tmp

# Find out the client type

if bpplclients -allunique | grep -q "^PC.*$CLIENT$" ; then
   POLICYTYPE="13 -nt_files"
   echo `date` Client is Windows >&2
else
   POLICYTYPE=0
   echo `date` Client is standard >&2
fi

# Set the date range for the bplist. If the user specified a backup image,
# use the date of that image. Otherwise, find the date of the last full
# image for the client, and any other full backup images started within
# 8 hours of that one (to pick up all the streams) and set the date range
# based on those images.

if [[ "$BUDATE" != "" ]] ; then
   STARTDATE=`convdate  "+%m/%d/%Y %H:%M:%S" $BUDATE`
   ENDDATE=`convdate  "+%m/%d/%Y %H:%M:%S" $BUDATE`
else
   echo `date` Identifying last full backup >&2
   /usr/openv/netbackup/bin/admincmd/bpimmedia -client $CLIENT -sl full 
2>/dev/null \
| grep ^IMAGE \
| cut -d " " -f 4 \
| sort -r -t _ -n -k2 \
| awk -F _ 'BEGIN { CUTOFF=0; }
{ if ( CUTOFF == 0 ) CUTOFF=$2 - 28800;
  if ( $2 > CUTOFF ) print $0; }' 
>/tmp/bu_by_filesystem_images_$$.tmp
   STARTDATE=`tail -1 /tmp/bu_by_filesystem_images_$$.tmp | cut -d _ -f 2`
   ENDDATE=`head -1 /tmp/bu_by_filesystem_images_$$.tmp | cut -d _ -f 2`
   if [[ "$STARTDATE" = "" ]] ; then
  echo Could not determine start date of the full backup >&2
  exit 1
   fi
   if [[ "$ENDDATE" = "" ]] ; then
  echo Could not determine end date of the full backup >&2
  exit 1
   fi
   STARTDATE=`convdate  "+%m/%d/%Y %H:%M:%S" $STARTDATE`
   ENDDATE=`convdate  "+%m/%d/%Y %H:%M:%S" $ENDDATE`
   rm /tmp/bu_by_filesystem_images_$$.tmp

   echo "Last full backup is from $STARTDATE to $ENDDATE" >&2
fi

# Now get the catalog data and see how much stuff came from which file 
systems

echo `date` Scanning catalog... >&2
echo >&2
bplist -C $CLIENT -t $POLICYTYPE -s $STARTDATE -e $ENDDATE -l -R / |
awk -v FSTEMP=/tmp/bu_by_filesystem_$$.tmp '
function add_commas ( STRIN ) {
   STROUT="";
   for ( Ic=length(STRIN)-2; Ic>=2 ; Ic=Ic-3 ) STROUT=substr(STRIN,Ic,3) 
"," STROUT;
   STROUT=substr(STRIN,1,Ic+2) "," STROUT;
   STROUT=substr(STROUT,1,length(STROUT)-1);
   return STROUT;
}

BEGIN {
FSYST[0]="unknown"; FSBYTES[0]=0; FSFILES[0]=0;
I=1; LONGESTFS=-1;
while ( ( getline  0 ) {
   FSYST[I]=$0; FSBYTES[I]=0; FSFILES[I]=0;
   if ( index(FSYST[I],":\\") != 0 ) {
  # UNIX-ize the path for windows systems
  FSYST[I]="/" substr(FSYST[I],1,index(FSYST[I],":\\")-1) "/" 
su