|
[Veritas-bu] Netbackup DB Catalog File Paths
2001-03-13 14:16:46
|
Subject: |
[Veritas-bu] Netbackup DB Catalog File Paths |
|
From: |
Price, Michael MPrice AT dantis DOT com |
|
Date: |
Tue, 13 Mar 2001 13:16:46 -0600 |
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C0ABF2.7C98A42C
Content-Type: text/plain;
charset="iso-8859-1"
We recently put ours on NAS. I'd love to know if anyone has any
insight or experiences on that, especially using EMC.
At Veritas training, I asked about NFS and they said it was a bad
idea because a problem with the mount may result to writing locally and then
not being able to sync. But I wish i had explained that I was thinking of
NAS. Our NAS is EMC.
Any comments appreciated.
-----Original Message-----
From: Karamchedu, Rajeev K. [mailto:rajeev AT tigr DOT org]
Sent: Tuesday, March 13, 2001 1:02 PM
To: Veritas-Bu (E-mail)
Subject: [Veritas-bu] Netbackup DB Catalog File Paths
Hello
Have you had any experiences with storing NB Catalogs
on an NFS Filesystems ? I am trying to find out if they
are problematic. Our netbackup catalog size is ever
increasing due to our increasing backup tasks
and I am thinking of throwing a part of it on a Netapp
filer so that I can grow it on demand..
(or I could add an internal disk, but that's only migrating
the problem to a future time...)
I appreciate your inputs.
Thanks
Rajeev
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
------_=_NextPart_001_01C0ABF2.7C98A42C
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2650.12">
<TITLE>RE: [Veritas-bu] Netbackup DB Catalog File Paths</TITLE>
</HEAD>
<BODY>
<BR>
<P> <FONT SIZE=3D2>We =
recently put ours on NAS. I'd love to know if anyone has any =
insight or experiences on that, especially using EMC.</FONT></P>
<P> <FONT SIZE=3D2>At Veritas =
training, I asked about NFS and they said it was a bad idea because a =
problem with the mount may result to writing locally and then not being =
able to sync. But I wish i had explained that I was thinking of =
NAS. Our NAS is EMC.</FONT></P>
<P> <FONT SIZE=3D2>Any =
comments appreciated.</FONT>
</P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Karamchedu, Rajeev K. [<A =
HREF=3D"mailto:rajeev AT tigr DOT org">mailto:rajeev AT tigr DOT org</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Tuesday, March 13, 2001 1:02 PM</FONT>
<BR><FONT SIZE=3D2>To: Veritas-Bu (E-mail)</FONT>
<BR><FONT SIZE=3D2>Subject: [Veritas-bu] Netbackup DB Catalog File =
Paths</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Hello</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Have you had any experiences with storing NB =
Catalogs</FONT>
<BR><FONT SIZE=3D2>on an NFS Filesystems ? I am trying to find out if =
they</FONT>
<BR><FONT SIZE=3D2>are problematic. Our netbackup catalog size is =
ever</FONT>
<BR><FONT SIZE=3D2>increasing due to our increasing backup tasks</FONT>
<BR><FONT SIZE=3D2>and I am thinking of throwing a part of it on a =
Netapp</FONT>
<BR><FONT SIZE=3D2>filer so that I can grow it on demand..</FONT>
</P>
<P><FONT SIZE=3D2>(or I could add an internal disk, but that's only =
migrating</FONT>
<BR><FONT SIZE=3D2>the problem to a future time...)</FONT>
</P>
<P><FONT SIZE=3D2>I appreciate your inputs.</FONT>
</P>
<P><FONT SIZE=3D2>Thanks</FONT>
</P>
<P><FONT SIZE=3D2>Rajeev</FONT>
<BR><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Veritas-bu maillist - =
Veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; =
TARGET=3D"_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas=
-bu</A></FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C0ABF2.7C98A42C--
|
|
|
