All,

FYI - Now that I've upgraded my Solaris media server to 6.0 as well, it 
seems to work a lot better. All I have to do is configure an Offline 
catalog backup of /usr/openv/netbackup/db and /usr/openv/var and all the 
other files I need get included automatically:

Host: sparky
Date: 11/10/2005 14:34:17

Offline catalog backup to media id PXT008 SUCCEEDED

Paths backed up:
----------------
  greebo:/usr/openv/netbackup/db
  greebo:/usr/openv/var/auth
  greebo:/usr/openv/var/vxss
  greebo:/usr/openv/var/license.txt
  greebo:/usr/openv/var/global
  greebo:/usr/openv/db/data/NBDB.db
  greebo:/usr/openv/db/data/EMM_DATA.db
  greebo:/usr/openv/db/data/EMM_INDEX.db
  greebo:/usr/openv/db/data/vxdbms.conf
  greebo:/usr/openv/var/global/server.conf
  greebo:/usr/openv/var/global/databases.conf
  greebo:/usr/openv/db/data/NBDB.log

So in summary - for full catalog protection with 6.0 the media server 
that does your catalog backups ALSO needs to be at 6.0 !!

Cheers

James

James Pattinson wrote:

> Hi All
>
> Not sure how many of you have played with NBU 6.0 yet, but I've just 
> upgraded to it from 5.1 MP3 over the weekend. Everything seems to work 
> OK but I'm a little concerned about the recovery of my catalog backups 
> at present.
>
> Environment:
>
> 6.0 master on RHEL 4.2 with no tape drives (greebo)
> 5.1 MP3 media server on Solaris 9 attached to the tape library (sparky)
> 5.1 MP3 media server on RHEL for disk staging (morbo)
>
> My catalog paths are configured as below:
>
>    greebo:/usr/openv/netbackup/db
>    greebo:/usr/openv/volmgr/database
>    greebo:/usr/openv/var
>    sparky:/usr/openv/netbackup/db
>    sparky:/usr/openv/volmgr/database
>
> (note that morbo doesn't need a catalog backup as it doesn't have a 
> mediaDB)
>
> Since greebo has no tape drive I'm using sparky as the catalog backup 
> server.
>
> Now, I'm only concerned about recovering the new EMM database after a 
> disaster. The manual implies that this is automatically backed up 
> during the catalog backup, but when I do a bprecover -l on the media 
> server, there are no .db files listed.
>
> Also, being a 5.1 media server I cannot specify any nbdb options on 
> the bprecover command line.
>
> I've tried adding each of the following lines in turn to my catalog 
> backup, but they've all failed with error 141:
>
> NETBACKUP_RELATIONAL_DATABASE_FILES
> greebo:NETBACKUP_RELATIONAL_DATABASE_FILES
> greebo:greebo.internal.org:NETBACKUP_RELATIONAL_DATABASE_FILES
>
> I guess the first question is - Is it supported to have a 6.0 master 
> doing catalog backups to a 5.1 media server? And why doesn't the 
> NETBACKUP_RELATIONAL_DATABASE_FILES directive work?
>
> I'd love to hear comments from any gurus on here!
>
> Thanks,
>
> James
>


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.