Veritas-bu

[Veritas-bu] Re: NDMP Backups through a Firewall (Shai Harmelin)

2004-09-22 11:36:28
Subject: [Veritas-bu] Re: NDMP Backups through a Firewall (Shai Harmelin)
From: sharmelin AT isilon DOT com (Shai Harmelin)
Date: Wed, 22 Sep 2004 08:36:28 -0700
This is a multi-part message in MIME format.
--------------030204000009010302030602
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Hi All,

My reply is unrelated to the error code you mentioned but touches on the 
network architecture the firewall needs to be aware off during NDMP 
operations.
NDMP is similar to FTP where the data and control channels are separate. 
This is particularly true in a 3-way configuration.
Port 10000 is used by the DMA (NBU) to communicate with both the Tape 
server (Mover) and the Data server (Filer) and this is also the port 
used with

set_ndmp_attr -verify. The data channel is established directly between the 
tape server and the data server mediated by the DMA. The data channel port is 
allocated dynamically and needs to be identified by the firewall during the 
actually backup/restore to allow the data stream to pass through.
Shai


veritas-bu-request AT mailman.eng.auburn DOT edu wrote:

>Send Veritas-bu mailing list submissions to
>       veritas-bu AT mailman.eng.auburn DOT edu
>
>To subscribe or unsubscribe via the World Wide Web, visit
>       http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>or, via email, send a message with subject or body 'help' to
>       veritas-bu-request AT mailman.eng.auburn DOT edu
>
>You can reach the person managing the list at
>       veritas-bu-admin AT mailman.eng.auburn DOT edu
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of Veritas-bu digest..."
>
>
>Today's Topics:
>
>   1. Netbackup 5.1 disk caching (Vincent_Mase AT harvardpilgrim DOT org)
>   2. Re: File Exclusions (Darren Dunham)
>   3. Re: FW: [Veritas-bu] Drop built-in catalog backup for rsync? (Dan 
> Logcher)
>   4. Re: File Exclusions (Wayne T Smith)
>   5. RE: File Exclusions (Mark.Donaldson AT cexp DOT com)
>   6. RE: File Exclusions (Jim Langston)
>   7. RE: File Exclusions (Mark.Donaldson AT cexp DOT com)
>   8. RE: File Exclusions (Jim Langston)
>   9. Re: File Exclusions (Ed Wilts)
>  10. NDMP Backups through a Firewall (Steve.Bally AT radisys DOT com)
>  11. Re: NDMP Backups through a Firewall (nathan r. hruby)
>
>--__--__--
>
>Message: 1
>To: veritas-bu AT mailman.eng.auburn DOT edu
>From: Vincent_Mase AT harvardpilgrim DOT org
>Date: Tue, 21 Sep 2004 15:48:08 -0400
>Subject: [Veritas-bu] Netbackup 5.1 disk caching
>
>Upgrading to NBU 5.1 on Windows 2000 and plan to implement disk caching 
>storage units utilizing EMC
>CX600 and CX700 ATA storage.  I have been advised by Veritas that I should 
>configure the ATA storage
>using diskpar, a windows 2000 resource kit utility, to configure the LUN 
>partitions to begin on byte
>boundaries that are divisible by 64 KB.  There is a white paper by EMC that 
>describes this process
>and the benefits  in detail
>http://www.emc.com/pdf/techlib/H959_clariion_bu_stor_ms_exch_snapview_ldv.pdf. 
> (see page 18)  I
>have configured my ATA LUNS  according to the EMC recommendations and find 
>that I cannot upgrade the
>LUNS to dynamic disks.  I would like to use dynamic disks so I could span 
>volumes and create larger
>ATA disk storage units.   Has anyone else run into this issue?  Also looking 
>for feedback on NBU5.1
>and any issues w/ backup to disk and the disk caching units in general.
>
>Vincent Mase
>Perot Systems
>Harvard Pilgrim Health Care Account
>617 509 3355
>
>
>--__--__--
>
>Message: 2
>From: Darren Dunham <ddunham AT taos DOT com>
>Subject: Re: [Veritas-bu] File Exclusions
>To: Veritas-bu AT mailman.eng.auburn DOT edu
>Date: Tue, 21 Sep 2004 13:23:57 -0700 (PDT)
>
>  
>
>>For example, I have changed traditional status code 1 backups to 0's 
>>just be excluding the (Netscape) "parent.lock" file (on Windows 
>>desktops).  Finding the path to "parent.lock" is MUCH more difficult, as 
>>it varies from client to client.
>>    
>>
>
>Yes, but can't you just specify it as /*/parent.lock ?  That's how I'm
>interpreting the support document.
>
>  
>
>>This isn't a new feature, ladies and gentlemen; it's a (documented after 
>>the fact) bug.  :-(
>>    
>>
>
>It's a bug if they didn't intend it to happen and are working to remove
>it.  There's no sign that they're working to change this.
>
>  
>
>>If Veritas refuses to correct this, shouldn't we have a tool to help 
>>find the entries that no longer work?  A fairly simple server script 
>>using bpgetconfig should do the trick.
>>    
>>
>
>It seems to me that not only finding them, a simple translation by
>adding /* could be done also.
>
>Of course if that were possible, you'd presume that the NBU process
>could do the same thing after reading the file into memory before acting
>on it....
>
>  
>

--------------030204000009010302030602
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Hi All,<br>
<br>
My reply is unrelated to the error code you mentioned but touches on
the network architecture the firewall needs to be aware off during NDMP
operations.<br>
NDMP is similar to FTP where the data and control channels are
separate. This is particularly true in a 3-way configuration.<br>
Port 10000 is used by the DMA (NBU) to communicate with both the Tape
server (Mover) and the Data server (Filer) and this is also the port
used with <br>
<pre wrap="">set_ndmp_attr -verify. The data channel is established directly 
between the tape server and the data server mediated by the DMA. The data 
channel port is allocated dynamically and needs to be identified by the 
firewall during the actually backup/restore to allow the data stream to pass 
through.
Shai
</pre>
<br>
<a class="moz-txt-link-abbreviated" href="mailto:veritas-bu-request AT 
mailman.eng.auburn DOT edu">veritas-bu-request AT mailman.eng.auburn DOT 
edu</a> wrote:
<blockquote cite="mid200409212136.i8LLaQXl013883 AT mailman.eng.auburn DOT edu"
 type="cite">
  <pre wrap="">Send Veritas-bu mailing list submissions to
        <a class="moz-txt-link-abbreviated" href="mailto:veritas-bu AT 
mailman.eng.auburn DOT edu">veritas-bu AT mailman.eng.auburn DOT edu</a>

To subscribe or unsubscribe via the World Wide Web, visit
        <a class="moz-txt-link-freetext" 
href="http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu";>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu</a>
or, via email, send a message with subject or body 'help' to
        <a class="moz-txt-link-abbreviated" href="mailto:veritas-bu-request AT 
mailman.eng.auburn DOT edu">veritas-bu-request AT mailman.eng.auburn DOT edu</a>

You can reach the person managing the list at
        <a class="moz-txt-link-abbreviated" href="mailto:veritas-bu-admin AT 
mailman.eng.auburn DOT edu">veritas-bu-admin AT mailman.eng.auburn DOT edu</a>

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Veritas-bu digest..."


Today's Topics:

   1. Netbackup 5.1 disk caching (<a class="moz-txt-link-abbreviated" 
href="mailto:Vincent_Mase AT harvardpilgrim DOT org">Vincent_Mase AT 
harvardpilgrim DOT org</a>)
   2. Re: File Exclusions (Darren Dunham)
   3. Re: FW: [Veritas-bu] Drop built-in catalog backup for rsync? (Dan Logcher)
   4. Re: File Exclusions (Wayne T Smith)
   5. RE: File Exclusions (<a class="moz-txt-link-abbreviated" 
href="mailto:Mark.Donaldson AT cexp DOT com">Mark.Donaldson AT cexp DOT com</a>)
   6. RE: File Exclusions (Jim Langston)
   7. RE: File Exclusions (<a class="moz-txt-link-abbreviated" 
href="mailto:Mark.Donaldson AT cexp DOT com">Mark.Donaldson AT cexp DOT com</a>)
   8. RE: File Exclusions (Jim Langston)
   9. Re: File Exclusions (Ed Wilts)
  10. NDMP Backups through a Firewall (<a class="moz-txt-link-abbreviated" 
href="mailto:Steve.Bally AT radisys DOT com">Steve.Bally AT radisys DOT com</a>)
  11. Re: NDMP Backups through a Firewall (nathan r. hruby)

--__--__--

Message: 1
To: <a class="moz-txt-link-abbreviated" href="mailto:veritas-bu AT 
mailman.eng.auburn DOT edu">veritas-bu AT mailman.eng.auburn DOT edu</a>
From: <a class="moz-txt-link-abbreviated" href="mailto:Vincent_Mase AT 
harvardpilgrim DOT org">Vincent_Mase AT harvardpilgrim DOT org</a>
Date: Tue, 21 Sep 2004 15:48:08 -0400
Subject: [Veritas-bu] Netbackup 5.1 disk caching

Upgrading to NBU 5.1 on Windows 2000 and plan to implement disk caching storage 
units utilizing EMC
CX600 and CX700 ATA storage.  I have been advised by Veritas that I should 
configure the ATA storage
using diskpar, a windows 2000 resource kit utility, to configure the LUN 
partitions to begin on byte
boundaries that are divisible by 64 KB.  There is a white paper by EMC that 
describes this process
and the benefits  in detail
<a class="moz-txt-link-freetext" 
href="http://www.emc.com/pdf/techlib/H959_clariion_bu_stor_ms_exch_snapview_ldv.pdf";>http://www.emc.com/pdf/techlib/H959_clariion_bu_stor_ms_exch_snapview_ldv.pdf</a>.
  (see page 18)  I
have configured my ATA LUNS  according to the EMC recommendations and find that 
I cannot upgrade the
LUNS to dynamic disks.  I would like to use dynamic disks so I could span 
volumes and create larger
ATA disk storage units.   Has anyone else run into this issue?  Also looking 
for feedback on NBU5.1
and any issues w/ backup to disk and the disk caching units in general.

Vincent Mase
Perot Systems
Harvard Pilgrim Health Care Account
617 509 3355


--__--__--

Message: 2
From: Darren Dunham <a class="moz-txt-link-rfc2396E" href="mailto:ddunham AT 
taos DOT com">&lt;ddunham AT taos DOT com&gt;</a>
Subject: Re: [Veritas-bu] File Exclusions
To: <a class="moz-txt-link-abbreviated" href="mailto:Veritas-bu AT 
mailman.eng.auburn DOT edu">Veritas-bu AT mailman.eng.auburn DOT edu</a>
Date: Tue, 21 Sep 2004 13:23:57 -0700 (PDT)

  </pre>
  <blockquote type="cite">
    <pre wrap="">For example, I have changed traditional status code 1 backups 
to 0's 
just be excluding the (Netscape) "parent.lock" file (on Windows 
desktops).  Finding the path to "parent.lock" is MUCH more difficult, as 
it varies from client to client.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Yes, but can't you just specify it as /*/parent.lock ?  That's how I'm
interpreting the support document.

  </pre>
  <blockquote type="cite">
    <pre wrap="">This isn't a new feature, ladies and gentlemen; it's a 
(documented after 
the fact) bug.  :-(
    </pre>
  </blockquote>
  <pre wrap=""><!---->
It's a bug if they didn't intend it to happen and are working to remove
it.  There's no sign that they're working to change this.

  </pre>
  <blockquote type="cite">
    <pre wrap="">If Veritas refuses to correct this, shouldn't we have a tool 
to help 
find the entries that no longer work?  A fairly simple server script 
using bpgetconfig should do the trick.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
It seems to me that not only finding them, a simple translation by
adding /* could be done also.

Of course if that were possible, you'd presume that the NBU process
could do the same thing after reading the file into memory before acting
on it....

  </pre>
</blockquote>
</body>
</html>

--------------030204000009010302030602--

<Prev in Thread] Current Thread [Next in Thread>
  • [Veritas-bu] Re: NDMP Backups through a Firewall (Shai Harmelin), Shai Harmelin <=