Actually you can not take a snapshot from a read-only volume such as a
SnapMirror destination volume but the dump application, started through
NDMP, will always backup the data from a snapshot.
The following has been observed using NetApp Filer with Ontap 6.x and 7.x
1) Writable volumes, without specifying a named snapshot (e.g. /vol/vol0)
will cause a snapshot to be taken for the backup
2) Writable volumes, with specifying a named snapshot (e.g.
/vol/vol0/.snapshot/daily.0) will backup from snapshot daily.0
3) Read-only volume, without specifying a named snapshot, will use that
youngest (last) snapshot on the volume.
4) Read-only volume, with specifying a named snapshot (e.g.
/vol/volx/.snapshot/daily.0) will backup from snapshot daily.0
5) Read-only volume, without snapshots available, don't know. But this
situation should logically not be possible because a snapmirrored volume
will always have snapshots.
Bye
Ernie
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On
Behalf Of N.J.Tustain
Sent: Wednesday, October 26, 2005 4:44 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] NDMP 7.2
We have two filers, take snapshots on the first, snapmirror then take
backups of the snapshot.
I'll test with the extra parameter.
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On Behalf Of Matthew Huff
Sent: 26 October 2005 12:44
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] NDMP 7.2
Why do you have the snapshot in the saveset definition? The nsrndmp_save
will create snapshots during the backup automatically. Try adding "DIRECT=Y"
to the App Info and see if it makes a difference.
BTW, we backup around 7TB but we have broken up the savesets by doing the
backups by qtree savesets which increases the parallelism
--
Matthew Huff | One Manhattanville Rd
Director of Operations | Purchase, NY 10577
OTA LLC | Phone: 914-460-4039
mailto:mhuff AT ox DOT com | Fax: 914-460-4139
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On Behalf Of N.J.Tustain
Sent: Wednesday, October 26, 2005 4:11 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] NDMP 7.2
One point I didn't mention is our smallest NDMP client (10GB) backups up
successfully. I think this proves it isn't a configuration issue.
Saveset: /vol/serv1vol_dst/.snapshot/serv1.monday
Backup Command: nsrndmp_save -T dump
App Info: NSR_NDMP_TMP_DIR=E:\nsr\tmp HIST=y UPDATE=y
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On Behalf Of Matthew Huff
Sent: 25 October 2005 17:14
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] NDMP 7.2
What does your NetApp client configuration look like?
What does your "backup command:" set to?
What is your "Application Information:" set to?
What is your "Save set:" set to?
----
Matthew Huff | One Manhattanville Rd
Dir of Operations | Purchase, NY 10577
OTA LLC | Phone: 914-460-4039
www.otaotr.com | Fax: 914-460-4139
> -----Original Message-----
> From: Legato NetWorker discussion
> [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On Behalf Of Kilpatrick, Mark
> Sent: Tuesday, October 25, 2005 12:01 PM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] NDMP 7.2
>
> The interesting thing here is that your backups ran correctly before
> the upgrade. I am going to run a test on our old system to compare the
> difference in time (networker 7.1.3).
>
> My backup just spent 30 minutes appearing to do nothing. Then it
> started to write to disk. If my 120,000 files took 30 mins then your
> ten million files could take approx 20 hours.
>
> Can you try a smaller volume specified in the saveset? I will let you
> know how my test with 7.1.3 goes.
>
> -----Original Message-----
> From: N.J.Tustain [mailto:N.J.Tustain AT OPEN.AC DOT UK]
> Sent: 25 October 2005 14:17
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] NDMP 7.2
>
> Stan/Mark,
>
> Thanks for the responses.
>
> We are running Networker nw_7_2_LGTpa69733.Build.6 Eval, which at the
> time of installation I believe was the latest version plus a fix for a
> portmapper vulnerability. Since we've added subsequent patches:
> 75442,72402,75831.
>
> We have 3 NDMP clients the largest being 110GB, but with 10million
> files!
>
> Our Filer is a NetApp F810, running NDMP version 3, which is still
> apparently supported.
>
> This all worked fine until the Networker upgrade. Apparently 7.2 now
> deals with NDMP backups in a modified way utilising disk as opposed to
> memory, to increase backup performance! Our ...\nsr\tmp directory now
> requires over 4GB of free space and also
> apparently only supports up to
> 15 levels (not sure if that's a new feature)
>
> I'm fairly sure the nothing is happening, twice I've set the backup
> running...checking late at night (were the data component was
> completing) in the morning the group is still active, but nothing is
> happening....so its been left for around 8 hours.
>
> I noticed that when a backup is set running, before a backup rate is
> indicated against a drive it shows 192KB, that is still the case.
>
> In an attempt to secure to tape I've started using the Filers' 'dump'
> command, although I haven't been able to perform a test restore.
>
> Thanks
> Nick
>
>
> -----Original Message-----
> From: Stan Horwitz [mailto:stan AT temple DOT edu]
> Sent: 25 October 2005 12:51
> To: Legato NetWorker discussion; N.J.Tustain
> Subject: Re: [Networker] NDMP 7.2
>
>
>
> On Oct 25, 2005, at 3:36 AM, N.J.Tustain wrote:
>
> > Hello,
> >
> > Since upgrading to 7.2 we've had trouble backing up our
> NDMP clients.
> > Since the upgrade, we've patched Networker
> (75442,72402,75831), which
> > changed the behaviour. The present issue appears to be, the
> local data
>
> > part of the backup writes to tape, but the index isn't
> written back to
>
> > the NW server. The group sits active with no activity, although
> > nsrndmp_save and nsrndmp_2fh processes are still running.
> >
> > Has anyone else had similar problems and found a workaround?
>
> Are you running NetWorker 7.2.1? What kind of NAS are you working
> with? I am running NetWorker 7.2.1 and NDMP backups work fine, as do
> recovers. I did have a problem with a test I did of backing up NDMP
> data to non-NDMP tape devices where the backup succeeded, but the
> recover failed. This is with using a Mirapoint message store as the
> NDMP client.
>
> 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
> wit 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
>
>
>
> Due to continued expansion Sabeo Technologies have moved office - to
> The Courtyard, Carmanhall Road, Sandyford, Dublin 18. Our telephone
> and fax numbers remain unchanged. A location map is available on our
> website www.sabeo.com.
>
>
>
> **********************************************************************
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> Sabeo Technologies.
>
> This footnote also confirms that this email message has been swept for
> the presence of computer viruses.
> **********************************************************************
>
> 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 wit 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
wit 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 wit 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
wit 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 wit 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
wit 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
|