Veritas-bu

[Veritas-bu] NDMP and normal filesystem backups sharing the same media?

2002-06-12 08:16:04
Subject: [Veritas-bu] NDMP and normal filesystem backups sharing the same media?
From: maddenca AT myrealbox DOT com (Chris Madden)
Date: Wed, 12 Jun 2002 14:16:04 +0200
This is a multi-part message in MIME format.

------=_NextPart_000_02DE_01C2121B.AFFCC330
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I have a strange situation but let me first describe my environment:

NB 3.4
1 x Master (Sol2.6) [no drives, although running NDMP for NetBackup to =
control NDMP drives]
3 x Media (Sol2.6) [4 LTO drives each]
3 x Netapp [4 LTO drives each]
2 x L700 connected to the Master server

We have several hundred clients doing normal filesystem backups (any =
available storage unit) that get handed off to one of the three media =
servers.  We then have a few dozen NetApp NDMP 3-way backups that have =
their storage unit statically assigned to one of the three NetApps that =
have drives attached.

Now, if someone asked me if I thought that NDMP backups and 'regular' =
backups would share the same physical media I would say no but in our =
environment it seems to be the case (which surprises me but I suppose =
that's the way it works).  The strange thing is that I thought at the =
time a tape was "assigned" to NetBackup it was done so to a single media =
server....and in our setup it would be the master for NDMP backups, and =
one of the 3 media servers for the regular backups.  Today I just got =
called as the Ops staff was having issues with a restore and I found the =
tape for a regular restore being requested on the master server:

13:51:12 (987260.004) Restoring from image created Thu Jun 06 00:02:06 =
2002
13:51:14 (987260.004) INF - Waiting for mount of media id CS4733 on =
server master.acme.net.
13:52:12 (987260.004) INF - Waiting for positioning of media id CS4733 =
on server master.acme.net.
13:53:35 (987260.004) INF - Beginning restore from server =
master.acme.net to client system5.acme.net.

Here's the bpstulist from the master:
na1_NDMP 3 master.acme.net 8 0 6 4 0 *NULL* 0 1 0 na1.acme.net
na2_NDMP 3 master.acme.net 8 1 6 4 0 *NULL* 1 1 0 na2.acme.net
na3_NDMP 3 master.acme.net 8 0 6 4 0 *NULL* 1 1 0 na3.acme.net
media1 2 media1.acme.net 8 0 6 4 0 *NULL* 0 6 0 *NULL*
media2 2 media2.acme.net 8 1 6 4 0 *NULL* 0 6 0 *NULL*
media3 2 media3.acme.net 8 1 6 2 0 *NULL* 0 6 0 *NULL*
media3-a 2 media3.acme.net 8 0 6 2 0 *NULL* 0 6 0 *NULL*

Now reviewing that specific media I found it to contain both NDMP =
backups and normal filesystem backups....how can this be?  The media =
server on the master only knows of the NDMP drives, how did that tape =
get mounted and written to by another media server?

For this restore I've just used "bpmedia -movedb -ev EA2122 -newserver =
media1.acme.net -oldserver master.acme.net" to change the media server =
so that the restore request will go somewhere that has drives to fulfill =
it.  It's in progress so but hopefully it will work.  After I moved it I =
just ran these two commands which I thought would have the same media =
server now:

master# bpmedialist -l -o -ev CS4733
CS4733 *NULL* 1 hcart 6 06/05/02:181531 06/10/02:213148 08/11/02:213148 =
06/11/02:135212 166410812 219 219 4 1 1 0 0 0 0 0 1 512 1024 0 0 0 0 0 0 =
0 0 0 master.acme.net

master# bpverify -pb -client system5.acme.net -hoursago 100
Media id =3D CS4706  Server =3D media3.acme.net
Media id =3D CS1907  Server =3D media3.acme.net
Media id =3D CS3294  Server =3D media2.acme.net
Media id =3D CS2680  Server =3D media1.acme.net
Media id =3D CS2882  Server =3D media2.acme.net
Media id =3D CS4902  Server =3D media2.acme.net
Media id =3D CS4986  Server =3D media3.acme.net
Media id =3D CS4729  Server =3D media3.acme.net
Media id =3D CS0498  Server =3D media1.acme.net
Media id =3D CS4733  Server =3D media1.acme.net
Media id =3D CS3112  Server =3D media3.acme.net

So it looks like the media is still assigned to master.acme.net, =
although the server NB thinks it used for the backup of system5.acme.net =
is media1.acme.net.

Anyone have an explanation on what's going on here?

Regards,
-Chris

------=_NextPart_000_02DE_01C2121B.AFFCC330
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2712.300" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I have a strange situation but let me =
first=20
describe my environment:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>NB 3.4</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>1 x Master (Sol2.6) [no drives, =
although running=20
NDMP for NetBackup to control NDMP drives]</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>3 x Media (Sol2.6) [4 LTO drives =
each]</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>3 x Netapp [4 LTO drives =
each]</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>2 x L700 connected to the Master=20
server</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>We have several hundred clients doing =
normal=20
filesystem backups (any available storage unit) that get handed off to =
one of=20
the three media servers.&nbsp; We then have a few dozen NetApp NDMP =
3-way=20
backups that have their storage unit&nbsp;statically assigned to one of =
the=20
three NetApps that have drives attached.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Now, if someone asked me if I thought =
that NDMP=20
backups and 'regular' backups would share the same physical media I =
would say no=20
but in our environment it seems to be the case (which surprises me but I =
suppose=20
that's the way it works).&nbsp; The strange thing is that I thought at =
the time=20
a tape was "assigned" to NetBackup it was done so to a single media=20
server....and in our setup it would be the master for NDMP backups, and =
one of=20
the 3 media servers for the regular backups.&nbsp; Today I just got =
called as=20
the Ops staff was having issues with a restore and I found the tape for =
a=20
regular restore being requested on the master server:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>13:51:12 (987260.004) Restoring from =
image created=20
Thu Jun 06 00:02:06 2002<BR>13:51:14 (987260.004) INF - Waiting for =
mount of=20
media id CS4733 on server master.acme.net.<BR>13:52:12 (987260.004) INF =
-=20
Waiting for positioning of media id CS4733 on server=20
master.acme.net.<BR>13:53:35 (987260.004) INF - Beginning restore from =
server=20
master.acme.net to client system5.acme.net.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Here's the bpstulist from the =
master:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>na1_NDMP 3 master.acme.net 8 0 6 4 0 =
*NULL* 0 1 0=20
na1.acme.net<BR>na2_NDMP 3 master.acme.net 8 1 6 4 0 *NULL* 1 1 0=20
na2.acme.net<BR>na3_NDMP 3 master.acme.net 8 0 6 4 0 *NULL* 1 1 0=20
na3.acme.net<BR>media1 2 media1.acme.net 8 0 6 4 0 *NULL* 0 6 0=20
*NULL*<BR>media2&nbsp;2 media2.acme.net 8 1 6 4 0 *NULL* 0 6 0=20
*NULL*<BR>media3&nbsp;2 media3.acme.net 8 1 6 2 0 *NULL* 0 6 0=20
*NULL*<BR>media3-a 2 media3.acme.net 8 0 6 2 0 *NULL* 0 6 0 =
*NULL*</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Now reviewing that specific media I =
found it to=20
contain both NDMP backups and normal filesystem backups....how can this=20
be?&nbsp; The media server on the master only knows of the NDMP drives, =
how did=20
that tape get mounted and written to by another media =
server?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>For this restore I've just used =
"bpmedia -movedb=20
-ev EA2122 -newserver media1.acme.net -oldserver master.acme.net" to =
change the=20
media server so that the restore request&nbsp;will go somewhere that has =
drives=20
to fulfill it.&nbsp; It's in progress so but hopefully it will =
work.&nbsp; After=20
I moved it I just ran these two commands which I thought would have the =
same=20
media server now:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>master# bpmedialist -l -o -ev =
CS4733<BR>CS4733=20
*NULL* 1 hcart 6 06/05/02:181531 06/10/02:213148 08/11/02:213148 =
06/11/02:135212=20
166410812 219 219 4 1 1 0 0 0 0 0 1 512 1024 0 0 0 0 0 0 0 0 0=20
master.acme.net</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>master# bpverify -pb -client =
system5.acme.net=20
-hoursago 100</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Media id =3D CS4706&nbsp; Server =3D=20
media3.acme.net<BR>Media id =3D CS1907&nbsp; Server =3D =
media3.acme.net<BR>Media id=20
=3D CS3294&nbsp; Server =3D media2.acme.net<BR>Media id =3D CS2680&nbsp; =
Server =3D=20
media1.acme.net<BR>Media id =3D CS2882&nbsp; Server =3D =
media2.acme.net<BR>Media id=20
=3D CS4902&nbsp; Server =3D media2.acme.net<BR>Media id =3D CS4986&nbsp; =
Server =3D=20
media3.acme.net<BR>Media id =3D CS4729&nbsp; Server =3D =
media3.acme.net<BR>Media id=20
=3D CS0498&nbsp; Server =3D media1.acme.net<BR>Media id =3D CS4733&nbsp; =
Server =3D=20
media1.acme.net<BR>Media id =3D CS3112&nbsp; Server =3D =
media3.acme.net</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>So it looks like the media is still =
assigned to=20
master.acme.net, although the server NB thinks it used for the backup of =

system5.acme.net is media1.acme.net.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Anyone have an explanation on what's =
going on=20
here?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Regards,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>-Chris</FONT></DIV></BODY></HTML>

------=_NextPart_000_02DE_01C2121B.AFFCC330--


<Prev in Thread] Current Thread [Next in Thread>
  • [Veritas-bu] NDMP and normal filesystem backups sharing the same media?, Chris Madden <=