EXPORT/IMPORT Preempt if NOPREEMPT is set?

2014-07-15 Thread Stackwick, Stephen
Can EXPORT/IMPORT preempt if NOPREEMPT is set? I see two opinions:

http://www-01.ibm.com/support/knowledgecenter/SSGSG7_6.3.4/com.ibm.itsm.srv.doc/r_srv_mng_process_preempt_opts_mount_point.html?lang=en

claims that:

To disable preemption, specify NOPREEMPT in the server options file. If you 
specify this option, the BACKUP DB command and the export and import commands 
are the only operations that can preempt other operations.


But the 7.1 admin reference says:

-
The server allows certain operations to preempt other operations for access to
volumes and devices. You can specify the NOPREEMPT option to disable
preemption. When preemption is disabled, no operation can preempt another for
access to a volume, and only a database backup operation can preempt another
operation for access to a device.
-

I have no idea why an EXPORT would be considered important enough to preempt 
other activities...

STEPHEN STACKWICK | Senior Consultant | 301.518.6352 (m) | 
stephen.stackw...@icfi.commailto:sstackw...@icfi.com | 
icfi.comhttp://www.icfi.com/
ICF INTERNATIONAL | 7125 Thomas Edison Dr, Suite 100, Columbia, Md 21046 | 
443-573-0524, 443-718-4900 (o)


Re: APARs fixed in TSM 7.1.0.100

2014-07-15 Thread Rick Adamson
Ingrida, 
How does this addresses the lack of any readme in patch directories? Of course 
I am assuming that if there is a patch posted there was a reason for it. It 
seems counterproductive to search one location for a patch that potentially 
addresses your issue then having to search a different location to try and 
determine what the patch addresses.



Rick Adamson
   

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Liudyte Baker
Sent: Monday, July 14, 2014 4:21 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] APARs fixed in TSM 7.1.0.100

Thank you for your comments about the recent Tivoli Storage Manager patch 
release. The 7.1.0.100 patch release that is currently available is intended 
only to update the Operations Center V7.1.0 on Linux so that it can run on an 
IBM Power Systems server. A 7.1.0.100 patch release for the Tivoli Storage 
Manager server is planned, and might be released in the coming months. This is 
subject to the sole discretion of IBM.

We would also like to address the related comment about APAR lists. When APAR 
updates are included in a patch release, the readme file includes a link to an 
APAR list that is published in the IBM Support portal, as shown in this example:

http://www-01.ibm.com/support/docview.wss?uid=swg21639086

The APAR list includes dynamic links that provide more information about each 
APAR. The reason for publishing the APAR list in the IBM Support portal is that 
minor changes might be required in the list after publication. In those cases, 
we update the list.

We are grateful for your feedback, and we hope that we answered your questions. 
Let us know if we can be of further assistance.

Ingrida Cazers
Information Development
Tivoli Storage Manager Server Team


Question about NDMP and TSM.

2014-07-15 Thread Plair, Ricky
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.


TSM for ERP - RMAN backup apparently succeeds, BRBACKUP gives up

2014-07-15 Thread Stackwick, Stephen
Using RMAN to backup a 10.2 Oracle SAP database with TSM for ERP 6.3. It seems 
when TSM preempts a drive, it kills the corresponding RMAN channel. Sounds 
reasonable, but apparently RMAN continues with the remaining channel(s) to 
finish the backup, obviously taking a little longer. But the TSM for ERP 
program BRBACKUP, doesn't seem able to deal with that and falls over:

First, RMAN:
RMAN-03009: failure of backup command on sbt_1 channel at 07/14/2014 22:19:05
ORA-27192: skgfcls: sbtclose2 returned error - failed to close file
ORA-19511: Error received from media manager layer, error text:
   BKI9309E: Operation terminated due to an explicit abort request.
ORA-19502: write error on file ECP_beohkssf.27102_1, block number 13010401 
(block size=8192)
ORA-27030: skgfwrt: sbtwrite2 returned error
ORA-19511: Error received from media manager layer, error text:
   BKI5008E: Tivoli Storage Manager Error.
channel sbt_1 disabled, job failed on it will be run on another channel
channel sbt_2: finished piece 1 at 14-JUL-14
:
:
Finished backup at 15-JUL-14

released channel: sbt_1
released channel: sbt_2
RMAN-00571: ===
RMAN-00569: === ERROR MESSAGE STACK FOLLOWS ===
RMAN-00571: ===
RMAN-03002: failure of release command at 07/15/2014 04:04:46
RMAN-06012: channel: sbt_1 not allocated

RMAN

List of Backup Sets
===

RMAN proceeds to list all the backupsets and, indeed, they are all there and 
backed up. But, apparently, because of the RMAN-03002 error, BRBACKUP 
concludes there was a failure and ends the backup, reporting failure:

Recovery Manager complete.
BR0280I BRBACKUP time stamp: 2014-07-15 04.04.55
BR0279E Return code from 'SHELL=/bin/sh /oracle/ECP/112_64/bin/rman nocatalog': 
1
BR0522E 112 of 108 files / save sets processed by RMAN
BR0536E RMAN call for database instance ECP failed
BR0200I BR_TRACE: location BrRmanCall-56, commands for RMAN in: 
/oracle/ECP/sapbackup/.beohkssf.cmd
@/oracle/ECP/sapbackup/..beohkssf..cmd
host '/usr/sap/ECP/SYS/exe/run/brtools -f delete 
/oracle/ECP/sapbackup/..beohkssf..cmd';
run { allocate channel sbt_1 device type 'SBT_TAPE'
parms 
'ENV=(XINT_PROFILE=/oracle/ECP/112_64/dbs/initECP.utl,PROLE_PORT=57323,BR_CALLER=BRBACKUP,BR_BACKUP=FULL,BR_REQUEST=NEW,BR_RUN=beohkssf.fnr)';
allocate channel sbt_2 device type 'SBT_TAPE'
parms 
'ENV=(XINT_PROFILE=/oracle/ECP/112_64/dbs/initECP.utl,PROLE_PORT=57323,BR_CALLER=BRBACKUP,BR_BACKUP=FULL,BR_REQUEST=NEW,BR_RUN=beohkssf.fnr)';
backup incremental level 0 tag beohkssf format 'ECP_beohkssf.%s_%p' filesperset 
4
database;
release channel sbt_1;
release channel sbt_2; }
list backup of database tag beohkssf;
exit;

BR0280I BRBACKUP time stamp: 2014-07-15 04.04.55
BR0506E Full database backup (level 0) using RMAN failed

BR0056I End of database backup: beohkssf.fnr 2014-07-15 04.04.55
BR0280I BRBACKUP time stamp: 2014-07-15 04.04.57
BR0054I BRBACKUP terminated with errors

Doesn't seem right to me. Is there a workaround (I know, I know, have enough 
tape drives), or is this PMR territory?

Steve Stackwick

STEPHEN STACKWICK | Senior Consultant | 301.518.6352 (m) | 
stephen.stackw...@icfi.commailto:sstackw...@icfi.com | 
icfi.comhttp://www.icfi.com/
ICF INTERNATIONAL | 7125 Thomas Edison Dr, Suite 100, Columbia, Md 21046 | 
443-573-0524, 443-718-4900 (o)


Re: Question about NDMP and TSM.

2014-07-15 Thread Schneider, Jim
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#4646, TSM PMR 23808,122,000.

Jim Schneider
United Stationers
 
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Plair, 
Ricky
Sent: Tuesday, July 15, 2014 1:21 PM
To: ADSM-L@VM.MARIST.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.


Re: Question about NDMP and TSM.

2014-07-15 Thread Ron Delaware
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.delaw...@us.ibm.com
Storage Services Offerings


 



From:   Schneider, Jim jschnei...@ussco.com
To: ADSM-L@vm.marist.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@vm.marist.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#4646, TSM PMR 23808,122,000.

Jim Schneider
United Stationers
 
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Plair, Ricky
Sent: Tuesday, July 15, 2014 1:21 PM
To: ADSM-L@VM.MARIST.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.





Re: Question about NDMP and TSM.

2014-07-15 Thread Steven Harris
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.delaw...@us.ibm.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.delaw...@us.ibm.com* ron.delaw...@us.ibm.com
 *Storage Services Offerings*
 http://www-01.ibm.com/software/tivoli/services/consulting/offers-storage-optimization.html





 From:Schneider, Jim jschnei...@ussco.com
 To:ADSM-L@vm.marist.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@vm.marist.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#4646, TSM PMR 23808,122,000.

 Jim Schneider
 United Stationers

 -Original Message-
 From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU
 ADSM-L@VM.MARIST.EDU] On Behalf Of Plair, Ricky
 Sent: Tuesday, July 15, 2014 1:21 PM
 To: ADSM-L@VM.MARIST.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 

Lun versus logical volume for DB volumes

2014-07-15 Thread Steven Harris
Hi,

I've specced a design for a new TSM server and as recommended have
specified multiple luns for the database.  The folklore is that DB2 will
start one thread per lun so for a big database you use 8 luns and hence get
8 threads.

My AIX guy is asking whether I really need 8 luns or will 8 AIX logical
volumes have the same effect.

Does anyone know or can tell me where to look?

Thanks

Steve.

Steven Harris
TSM Admin
Canberra Australia


Re: Lun versus logical volume for DB volumes

2014-07-15 Thread Ron Delaware
Steven,

The logical volumes are not dedicated disks in most cases, which means 
that other applications may be using the same disks at the same time. With 
our new TSM Server Blueprint standards, TSM database's over 1TB require 
16 luns.

You can go to this link to find out more

https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Storage%20Manager/page/NEW%20-%20Tivoli%20Storage%20Manager%20Blueprint%20-%20%20Improve%20the%20time-to-value%20of%20your%20deployments


 
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.delaw...@us.ibm.com
Storage Services Offerings


 



From:   Steven Harris st...@stevenharris.info
To: ADSM-L@vm.marist.edu
Date:   07/15/2014 06:55 PM
Subject:[ADSM-L] Lun versus logical volume for DB volumes
Sent by:ADSM: Dist Stor Manager ADSM-L@vm.marist.edu



Hi,

I've specced a design for a new TSM server and as recommended have
specified multiple luns for the database.  The folklore is that DB2 will
start one thread per lun so for a big database you use 8 luns and hence 
get
8 threads.

My AIX guy is asking whether I really need 8 luns or will 8 AIX logical
volumes have the same effect.

Does anyone know or can tell me where to look?

Thanks

Steve.

Steven Harris
TSM Admin
Canberra Australia





Re: Question about NDMP and TSM.

2014-07-15 Thread Gee, Norman
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@VM.MARIST.EDU] On Behalf Of Steven 
Harris
Sent: Tuesday, July 15, 2014 6:48 PM
To: ADSM-L@VM.MARIST.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.delaw...@us.ibm.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.delaw...@us.ibm.com* ron.delaw...@us.ibm.com
 *Storage Services Offerings*
 http://www-01.ibm.com/software/tivoli/services/consulting/offers-storage-optimization.html





 From:Schneider, Jim jschnei...@ussco.com
 To:ADSM-L@vm.marist.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@vm.marist.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#4646, TSM PMR 23808,122,000.

 Jim Schneider
 United Stationers

 -Original Message-
 From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU
 ADSM-L@VM.MARIST.EDU] On Behalf Of Plair, Ricky
 Sent: Tuesday, July 15, 2014 1:21 PM
 To: ADSM-L@VM.MARIST.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