ADSM-L

Re: [ADSM-L] Question about NDMP and TSM.

2014-07-16 04:26:45
Subject: Re: [ADSM-L] Question about NDMP and TSM.
From: Grant Street <grants AT AL.COM DOT AU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 16 Jul 2014 18:24:52 +1000
Hi

First check compatibility with IBM and EMC.

Ron has mentioned a solution that applies to NetApp that may not apply to EMC isilon eg. isilon does not have a vfiler concept.

I found that the restrictions of NDMP did not warrant the effort to use it on something like an isilon cluster. The benefit of isilon is the size you can grow them to and the bandwidth you have to storage with multiple nodes.

Using NDMP negates all of this and reduces the functionality.
- you are limited to the bandwidth a single host(TSM server) and single isilon node can service. - There is no incremental only differential. There is no snapdiff type functionality that NetApps have
- you can't use NDMP to back up part of it.
- The time it would take to do a full backup.
- The time it would take to do a restore.

One other niggle is that you need a windows machine to do a graphical restore (Web/Java UI).

That said if your data is small then these probably don't matter so much.


Grant

On 16/07/14 13:51, Gee, Norman wrote:
I found out that this is true a long time ago, but it does not stop you from 
manually doing a move data to empty out a tape volume.  It is just a very 
manual form of reclaim.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Steven Harris
Sent: Tuesday, July 15, 2014 6:48 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Question about NDMP and TSM.

And as a bonus, ndmp storage pools cannot be reclaimed and this means that
they hold tapes until the last data has expired.  TSM format storage pools
can be reclaimed, and if they are file storage pools can be deduped as well.


Regards

Steve

Steven Harris
TSM Admin
Canberra Australia



On 16 July 2014 05:38, Ron Delaware <ron.delaware AT us.ibm DOT com> wrote:

Ricky,

The configuration that you are referring to is what could be considered
the 'Traditional' implementation of NDMP.  As you have found for yourself,
there are a number of restrictions on how the data can be managed though.

If you configure the NDMP environment so that a Tivoli Storage Manager
controls the data flow instead of the NetApp Appliance, you have more
options


This configuration will allow you backup up to TSM storage pools (Disk,
VTL, Tape), send copies offsite, because the TSM Server controls the
destination.  You have the option to use a traditional TSM Client utilizing
the NDMP protocol or have the TSM server perform the backup and restores
using the BACKUP NODE and RESTORE NODE commands. It a table of contents
storage pool (disk based only highly recommended) you can perform single
file restores.  you can also create virtual filespace pointers to your
vfiler that will allow you to run simultaneous backups of the vfiler, that
could shorten your backup and restore times.





Best Regards,

_________________________________________________________
* Ronald C. Delaware*
IBM Level 2 - IT Plus Certified Specialist – Expert
IBM Corporation | Tivoli Software
IBM Certified Solutions Advisor - Tivoli Storage
IBM Certified Deployment Professional
Butterfly Solutions Professional
916-458-5726 (Office
925-457-9221 (cell phone)

email: *ron.delaware AT us.ibm DOT com* <ron.delaware AT us.ibm DOT com>
*Storage Services Offerings*
<http://www-01.ibm.com/software/tivoli/services/consulting/offers-storage-optimization.html>





From:        "Schneider, Jim" <jschneider AT USSCO DOT COM>
To:        ADSM-L AT vm.marist DOT edu
Date:        07/15/2014 12:19 PM
Subject:        Re: [ADSM-L] Question about NDMP and TSM.
Sent by:        "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
------------------------------



Ricky,

The Isilon uses the OneFS file system and TSM views it as one huge file
system.  If backing up to disk, TSM will attempt to preallocate enough
space to back up the entire allocated space on the Isilon. Defining Virtual
File systems will not help because directory quota information is not
passed to TSM, and TSM only sees the total allocated space.

We were able to back up the Isilon to disk when we started on a test
system with little data on it, around 25 GB.  When we attempted to
implement the same backups on a second, well-populated Isilon we ran into
the space allocation problem.

When backing up to tape, TSM assumes you have unlimited storage available
and is able to run VFS backups.  We use Virtual File Space Mapping (VFS)
and back up to tape.

Refer to EMC SR#55554646, TSM PMR 23808,122,000.

Jim Schneider
United Stationers

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU
<ADSM-L AT VM.MARIST DOT EDU>] On Behalf Of Plair, Ricky
Sent: Tuesday, July 15, 2014 1:21 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Question about NDMP and TSM.

I have been asked to look into backing up our EMC Isilon using our TSM
server.

Everything I read,  seems to point to backing this NDMP device to tape.

Problem is, we do not use tape to backup production.

I have researched and found a few articles about backing the NDMP device
to tape but, there seem to be more cons than pros.

Is there anybody backing up a NDMP device to disk that can give me some
pros and,  how they are using disk for this task.


I appreciate your time!



_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ CONFIDENTIALITY NOTICE: This email message, including any attachments, is
for the sole use of the intended recipient(s) and may contain confidential
and privileged information and/or Protected Health Information (PHI)
subject to protection under the law, including the Health Insurance
Portability and Accountability Act of 1996, as amended (HIPAA). If you are
not the intended recipient or the person responsible for delivering the
email to the intended recipient, be advised that you have received this
email in error and that any use, disclosure, distribution, forwarding,
printing, or copying of this email is strictly prohibited. If you have
received this email in error, please notify the sender immediately and
destroy all copies of the original message.

**********************************************************************
Information contained in this e-mail message and in any attachments
thereto is confidential. If you are not the intended recipient, please
destroy this message, delete any copies held on your systems, notify the
sender immediately, and refrain from using or disclosing all or any part of
its content to any other person.