A "backup stg" of a NetApp Dump format storage pool (required for a
NetApp/N-series direct to tape NDMP backup) hands off the actual copy
to the filer, which performs an NDMP copy operation from one drive to
another. TSM doesn't touch the data in this case.
I should say "a" filer, since TSM seems to pick an arbitrary filer
that has access to the drives/tape volumes, and asks that filer to do
the copy -- even if it's not that filer's data.
Steve, does IBM have N-series software support as well as hardware
support? Maybe they would be more helpful, since NDMP is really a
software operation. (Or does IBM not make a distinction for N-series?
I'm not sure how NetApp does it, since a different group manages our
NetApps even though I "get to" back them up to TSM.)
=Dave
Ehresman,David E. wrote:
>
> I'm confused. A "backup stg" copies data from a primary TSM storage
> pool (tape in your case) to a copy TSM storage pool (again tape).
> During this process there should not be any N-Series involvement. It
> strictly a TSM tape to tape function. What am I missing?
>
> David
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Steven Harris
> Sent: Wednesday, April 25, 2012 7:11 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] TSM 6.3 NAS Filer backup stg issues
>
> Hi All
>
> I've got a problem with running backup stg of nas filer NDMP backups.
>
> I have a TSM 6.3.1 server on RHEL 5.7 X86_64, an N-Series filer at Data
> On-Tap 8.1RC2 and A shared TS3310 library with LTO5 drives. Actually I
> have two setups exactly the same in different cities, except one has
> more data and 3 drives and the other has less data and two drives.
>
> NDMP backups are configured to write directly to tape and seem to work
> fine. The backup completes cleanly if slowly, and the limited restores
> I have done worked once I went to 6.3.1.
>
> But, I want an offsite copy, and so run backup stg against the NAS
> primary tape pool. This is consistently failing - but only on certain
> filer volumes. On the first filer with the problem it seems to copy
> correctly on volumes that are cifs shared, but fail on volumes that are
> used by FC, at least I thought that was the difference. On the second
> filer there are no FC volumes, but somehow those copies are failing too.
>
> TSM support points at the filer people because the error is a bad return
> code from an operation that is handed off to the filer. I have been
> working with N-series hardware support on this for a month and only now
> realize that they have co concept of what the problem is..... they
> thought backup stg produced an NDMP backup.
>
> Has any one else seen this problem? Does anyone on the list know how to
> get traction on these sorts of issues from Nseries hardware support ?
>
> Regards
>
> Steve
>
> Steven Harris
> TSM Admin
> Canberra Australia
>
--
Hello World. David Bronder - Systems Architect
Segmentation Fault ITS-EI, Univ. of Iowa
Core dumped, disk trashed, quota filled, soda warm. david-bronder AT uiowa
DOT edu
|
