Networker

Re: [Networker] NDMP Backups - Library connection req'd?

2008-05-14 13:11:42
Subject: Re: [Networker] NDMP Backups - Library connection req'd?
From: David Dulek <ddulek AT FASTENAL DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Wed, 14 May 2008 12:06:49 -0500
I don't think you need the -P if you backup to the NetWorker server.
nsrndmp_save -T dump -M

On Wed, 2008-05-14 at 12:37 -0400, Dias, Kent (Contractor) wrote:
> Yes - the current settings are as follows:
> 
> Backup command: nsrndmp_save -T dump -M -P 192.168.0.150 {the IP addr of
> Networker server}
> 
> Application information: 
>       CLIENT=y
>       HIST=y
>       DIRECT=y
>       UPDATE=y
>       EXTRACT_ACL=y
>  
> Remote user: root
> Password: ***********  - has been verified as correct and re-entered
> 
> Storage nodes: uspmuusricnsr01 {this is the Networker Server}
> 
> 
> 
> 
> -----Original Message-----
> From: Matthew Huff [mailto:mhuff AT ox DOT com] 
> Sent: Wednesday, May 14, 2008 12:31 PM
> To: Dias, Kent (Contractor); NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: RE: [Networker] NDMP Backups - Library connection req'd?
> 
> Did you take out the .snapshot from the savesets?
> 
> ----
> Matthew Huff       | One Manhattanville Rd
> OTA Management LLC | Purchase, NY 10577
> www.otaotr.com     | Phone: 914-460-4039
> aim: matthewbhuff  | Fax:   914-460-4139
> 
> -----Original Message-----
> From: Dias, Kent (Contractor)
> [mailto:Robert.K.Dias.contractor AT altria DOT com] 
> Sent: Wednesday, May 14, 2008 12:28 PM
> To: Matthew Huff; NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: RE: [Networker] NDMP Backups - Library connection req'd?
> 
> This is getting more & more annoying and frustrating. Whenever I include
> the -M argument, I get the following errors back:
> 
>       avegrp: suppressed 3 lines of verbose output
>       nsrndmp_save: Performing DAR Backup..
>       nsrdsa_save: READY:(host, ipaddr, port) = (192.168.0.150,
> 192.168.0.150, 9095)
>       nsrndmp_save: Host = 192.168.0.150 (192.168.0.150) port = 9095
>       nsrndmp_save: data start backup: illegal arguments in request
>       nsrndmp_save: Unable to start the NDMP backup process.
>       nsrndmp_save: Data server halted: The backup is aborted by
> operator.
>       nsrndmp_save: NDMP Service Log: Aborted by client
>       nsrndmp_save: Save session closed with NW server successfully 
> 
> Is there a piece I need to install or license to use DSA? Should I just
> take a fire axe to the whole thing and tell the bosses to put everything
> on paper?
> 
> -----Original Message-----
> From: Matthew Huff [mailto:mhuff AT ox DOT com] 
> Sent: Wednesday, May 14, 2008 11:59 AM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU; Dias, Kent (Contractor)
> Subject: RE: [Networker] NDMP Backups - Library connection req'd?
> 
> We use the -P to specify the exact interface to use since both the
> NetApp and backup server have multiple NICS (we have a dedicated backup
> network with jumbo frames turned on). The -P isn't just used for
> proxies, it also can be used to specify the IP address of the server
> that you want to use. You need to be using the "-M" for DSA (network
> based backups of NDMP).
> 
> From the manpage:
> 
> 
>    -M   An NDMP client will be backed up to a NetWorker storage
>           node  by  the nsrdsa_save program. This option provides
>           most of the NetWorker storage node  features,  such  as
>           backup  to  disk, multiplexing, automedia verification,
>           and   staging.   The   nsrndmp_save   program    spawns
>           nsrdsa_save locally.  A NetWorker storage node hostname
>           should be listed in the "storage  nodes"  attribute  of
>           server's client-name resource.
>           Notes:
>           Save sets  that  are  backed  up  by  nsrndmp_save  via
>           nsrdsa_save  will  be treated as regular NetWorker save
>           set and will have save set flags as 'N'  and  's'.  'N'
>           indicates  NDMP  client  and 's' indicates backed up to
>           NetWorker  storage  node.  See  mminfo  (1m)  for  more
>           details.
> 
> 
> ----
> Matthew Huff       | One Manhattanville Rd
> OTA Management LLC | Purchase, NY 10577
> www.otaotr.com     | Phone: 914-460-4039
> aim: matthewbhuff  | Fax:   914-460-4139
> 
> -----Original Message-----
> From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] 
> On
> Behalf Of Dias, Kent (Contractor)
> Sent: Wednesday, May 14, 2008 11:42 AM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] NDMP Backups - Library connection req'd?
> 
> According to EMC's whitepaper (yeah, I know....) the -P is required
> since the library isn't attached to the NetApp filers 
> 
> What is -M for?
> 
> -----Original Message-----
> From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] 
> On
> Behalf Of Yaron Zabary
> Sent: Wednesday, May 14, 2008 11:31 AM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] NDMP Backups - Library connection req'd?
> 
> Dias, Kent (Contractor) wrote:
> > I've changed the backup command to:
> >     nsrndmp_save -P uspmuusricnsr01 -T dump
> 
>    You are missing the -M option. Also, why use a proxy host ?
> 
> > 
> > Application Information is:
> >     HIST=Y
> >     DIRECT=y
> >     UPDATE=y
> >     EXTRACT_ACL=y 
> > 
> > Savesets are:
> >     /vol/vol0/.snapshot
> >     /vol/esxwinos/.snapshot
> >     /vol/esxwindata/.snapshot
> >     /vol/esxwinswap/.snapshot
> >     /vol/esxwinsqllog/.snapshot
> >     /vol/esxwinsqldata/.snapshot
> 
>    I am quite sure you are not supposed to backup snapshots (the dump 
> itself uses snapshots).
> 
> > 
> > The NetApp filers are also no longer configured in Networker as
> StorageNodes - just clients
> > 
> > Thanks, 
> >         Kent 
> > 
> > Kent Dias 
> > Windows System Administrator 
> > Northrop Grumman IT - Richmond 
> > robert.k.dias.contractor AT altria DOT com 
> > 
> > 
> > 
> > -----Original Message-----
> > From: Matthew Huff [mailto:mhuff AT ox DOT com] 
> > Sent: Wednesday, May 14, 2008 10:44 AM
> > To: NETWORKER AT LISTSERV.TEMPLE DOT EDU; Dias, Kent (Contractor)
> > Subject: RE: [Networker] NDMP Backups - Library connection req'd?
> > 
> > The Netapp can be backed up via network using NDMP. The name EMC uses
> is DSA. There are very good examples and diagrams on the NDMP chapter in
> the admin guide. What is your save command for that client, your
> savesets and your attributes?
> > 
> > ----
> > Matthew Huff       | One Manhattanville Rd
> > OTA Management LLC | Purchase, NY 10577
> > www.otaotr.com     | Phone: 914-460-4039
> > aim: matthewbhuff  | Fax:   914-460-4139
> > 
> > -----Original Message-----
> > From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
> On Behalf Of Kent Dias
> > Sent: Wednesday, May 14, 2008 10:35 AM
> > To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> > Subject: [Networker] NDMP Backups - Library connection req'd?
> > 
> > I'm trying to set up NDMP backups of our NetAPP NAS. We are running 
> > Networker 7.3.2 on Windows 2003 Server with 3 tape libraries attached
> via 
> > our SAN switch. The NetApp is NOT connected to the SAN - only the LAN
> at 
> > this time.
> > 
> > I have added the NAS nodes as clients and also added them as storage 
> > nodes. I've created a dedicated medias pool and pointed it to a single
> 
> > drive on Lib2. When I try to back them up I get the following: 
> > 
> > * pmurdenasp01:/vol/vol0/.snapshot nsrndmp_save: error, no matching 
> > devices for save of client `pmurdenasp01'; check storage nodes,
> devices or 
> > pools
> > 
> > 
> > Is this because the NAS doesn't have a connection to a tape library?
> > 
> > Our NAS Administrator insists that this can be done without the NAS
> having 
> > a connected library - I'm not so sure.
> > 
> > Any suggestions on proper implementation of NDMP backups ?
> > 
> > Thanks, 
> >         Kent 
> > 
> > Kent Dias 
> > Windows System Administrator 
> > Northrop Grumman IT - Richmond 
> > robert.k.dias.contractor AT altria DOT com 
> > 
> > To sign off this list, send email to listserv AT listserv.temple DOT edu and
> type "signoff networker" in the body of the email. Please write to
> networker-request AT listserv.temple DOT edu if you have any problems with 
> this
> list. You can access the archives at
> http://listserv.temple.edu/archives/networker.html or
> > via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
> > 
> > To sign off this list, send email to listserv AT listserv.temple DOT edu and
> type "signoff networker" in the body of the email. Please write to
> networker-request AT listserv.temple DOT edu if you have any problems with 
> this
> list. You can access the archives at
> http://listserv.temple.edu/archives/networker.html or
> > via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
> 
> 
> -- 
> 
> -- Yaron.
> 
> To sign off this list, send email to listserv AT listserv.temple DOT edu and
> type "signoff networker" in the body of the email. Please write to
> networker-request AT listserv.temple DOT edu if you have any problems with 
> this
> list. You can access the archives at
> http://listserv.temple.edu/archives/networker.html or
> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
> 
> To sign off this list, send email to listserv AT listserv.temple DOT edu and
> type "signoff networker" in the body of the email. Please write to
> networker-request AT listserv.temple DOT edu if you have any problems with 
> this
> list. You can access the archives at
> http://listserv.temple.edu/archives/networker.html or
> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
> 
> To sign off this list, send email to listserv AT listserv.temple DOT edu and 
> type "signoff networker" in the body of the email. Please write to 
> networker-request AT listserv.temple DOT edu if you have any problems with 
> this list. You can access the archives at 
> http://listserv.temple.edu/archives/networker.html or
> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

<Prev in Thread] Current Thread [Next in Thread>