Veritas-bu

[Veritas-bu] content of hot catalog backup

2007-03-22 10:46:00
Subject: [Veritas-bu] content of hot catalog backup
From: ddunham at taos.com (Darren Dunham)
Date: Thu, 22 Mar 2007 06:46:00 -0800 (PST)
> 
> Can you give me the exact syntax of your command bpflist and bplist command ??
[...]
> It's not exactly equivalent, but you can view the files saved with 'bplist' or
> 'bpflist'. 
> 
> For instance on my machine, these come from the actual DB backup:
> 
> 1 0 37 57 7 1 0 0 2065 /veritas/openv/db/staging/EMM_DATA.db 33206 root root 
> 26226688 1174132803 1174132813 1174132813
> 2 0 38 57 51233 1 0 0 2065 /veritas/openv/db/staging/EMM_INDEX.db
> 33206 root root 26226688 1174132813 1174132825 1174132825

In this case, I just wanted to see FULL backups.  The same should work
for incrementals as well.  All full backups, my policy is 'Catalog-hot',
give the client and a date range.

# bpimagelist -hoursago 200 -client <server> -policy Catalog-hot -st FULL

This returns a list of images (hopefully 2).

IMAGE <server> 0 0 7 <server>_1174132970 Catalog-hot 35 *NULL* NetBackup ...
IMAGE <server> 0 0 7 <server>_1174132835 Catalog-hot 7 *NULL* NetBackup ...

'35' represents an NBU_Catalog policy type, '7' a Sybase policy type.
So these are the right ones.

Now run bpflist on those images.  From past testing, bpflist is
"touchy".  Even though you can give a backupid exactly, it won't find
anything for me without also specifying a date range and a client.  

# bpflist -d 01/01/2000 -backupid <server>_1174132835 -client <server> -rl 99
# bpflist -d 01/01/2000 -backupid <server>_1174132970 -client <server> -rl 99

There's the filelist.

-- 
Darren Dunham                                           ddunham at taos.com
Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

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