|
[Veritas-bu] Vault Catalog Issue
2003-06-20 03:50:57
This is a multipart message in MIME format.
--=_alternative 002B21DC86256D4B_=
Content-Type: text/plain; charset="us-ascii"
You can do a restore in a DR without the MediaDB's from the media servers.
I, personally, don't like manually adding volumes into my VolDB in a
DR... and if you're also going to do backups, a newly added (and
unassigned) tape could get accidentally overwritten.
If it were me, I would forget about the media servers for the vault
catalog backups (at least until this is fixed), but add the
volmgr/database entry back in.
- Scott
"Greg Campbell" <gcampbell AT rgv.rr DOT com>
Sent by: veritas-bu-admin AT mailman.eng.auburn DOT edu
06/19/2003 10:09 PM
To: <veritas-bu AT mailman.eng.auburn DOT edu>
cc:
Subject: [Veritas-bu] Vault Catalog Issue
I have a NetBackup 4.5 MP4 system running Win2000 on the master and 37
media
servers. The problem I am running into deals with vaulting the catalog. I
seem to have run into a maximum string length issue for the bpbackupdb
command. If the length of the command plus the paths to the catalog files
exceed 2000 characters the catalog vault fails. A total length less than
2000 completes successfully. Veritas tech support has had me remove the
paths to the Netbackup\var and the VolMgr\database directories to reduce
this length while thay are investigating the problem. My question is has
anyone else ran into this problem with Vault? If so what did you do about
it? Just getting a partial backup of the catalog does not seem to be the
answer.
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
--=_alternative 002B21DC86256D4B_=
Content-Type: text/html; charset="us-ascii"
<br><font size=2 face="Arial">You can do a restore in a DR without the
MediaDB's from the media servers. I, personally, don't like manually
adding volumes into my VolDB in a DR... and if you're also going to do backups,
a newly added (and unassigned) tape could get accidentally overwritten.</font>
<br>
<br><font size=2 face="Arial">If it were me, I would forget about the media
servers for the vault catalog backups (at least until this is fixed), but add
the volmgr/database entry back in.</font>
<br>
<br>
<br><font size=2 face="Arial">- Scott</font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>"Greg Campbell" <gcampbell
AT rgv.rr DOT com></b></font>
<br><font size=1 face="sans-serif">Sent by: veritas-bu-admin AT
mailman.eng.auburn DOT edu</font>
<p><font size=1 face="sans-serif">06/19/2003 10:09 PM</font>
<br>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To:
<veritas-bu AT mailman.eng.auburn DOT edu></font>
<br><font size=1 face="sans-serif"> cc:
</font>
<br><font size=1 face="sans-serif"> Subject:
[Veritas-bu] Vault Catalog Issue</font></table>
<br>
<br>
<br><font size=2 face="Courier New">I have a NetBackup 4.5 MP4 system running
Win2000 on the master and 37 media<br>
servers. The problem I am running into deals with vaulting the catalog. I<br>
seem to have run into a maximum string length issue for the bpbackupdb<br>
command. If the length of the command plus the paths to the catalog files<br>
exceed 2000 characters the catalog vault fails. A total length less than<br>
2000 completes successfully. Veritas tech support has had me remove the<br>
paths to the Netbackup\var and the VolMgr\database directories to reduce<br>
this length while thay are investigating the problem. My question is has<br>
anyone else ran into this problem with Vault? If so what did you do about<br>
it? Just getting a partial backup of the catalog does not seem to be the<br>
answer.<br>
<br>
_______________________________________________<br>
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu<br>
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu<br>
</font>
<br>
<br>
--=_alternative 002B21DC86256D4B_=--
|
|
|
