[prev in list] [next in list] [prev in thread] [next in thread] 

List:       adsm-l
Subject:    Re: TSM RHEL7 Linux server and EMC Isilon
From:       Shawn DREW <shawn.drew () US ! BNPPARIBAS ! COM>
Date:       2016-03-28 22:13:09
Message-ID: 325B6C803BB3564AA3A4CBB1A5673EDE70905864 () NYCS00072004 ! mercury ! intra
[Download RAW message or body]

We use NFS for large (>500TB) device classes. (on Data Domain, not isilon though) 
File device class is the way to go.  Just review the NFS performance settings and get \
the best practice stuff from EMC for your implementation  (i.e. trunked 10gb \
connections might have different settings than 1gb)

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan \
                Forray
Sent: Monday, March 28, 2016 11:02 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] TSM RHEL7 Linux server and EMC Isilon

We are working on a project to beef up offsite backups using an EMC Isilon
box attached to a RHEL TSM server.

Anybody doing this kind of configuration?  I have concerns since it will be
connecting >300TB via NFS mount to use for the TSM storage. I am assuming
it will be best to define the stgpool as a FILE format?


--
*Zoltan Forray*
TSM Software & Hardware Administrator
Xymon Monitor Administrator
VMware Administrator (in training)
Virginia Commonwealth University
UCC/Office of Technology Services
www.ucc.vcu.edu
zforray@vcu.edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html

This message and any attachments (the "message") is intended solely for the \
addressees and is confidential. If you receive this message in error, please delete \
it and immediately notify the sender. Any use not in accord with its purpose, any \
dissemination or disclosure, either whole or partial, is prohibited except formal \
approval. The internet can not guarantee the integrity of this message. BNP PARIBAS \
(and its subsidiaries) shall (will) not therefore be liable for the message if \
modified. Please note that certain functions and services for BNP Paribas may be \
performed by BNP Paribas RCC, Inc.


Unless otherwise provided above, this message was sent by BNP Paribas, or one of its \
affiliates in Canada, having an office at 1981 McGill College Avenue, Montreal, QC, \
H3A 2W8, Canada. To the extent this message is being sent from or to Canada, you may \
unsubscribe from receiving commercial electronic messages by using this link: \
www.bnpparibas.ca/en/unsubscribe/ <http://www.bnpparibas.ca/en/unsubscribe/>. See \
www.bnpparibas.ca <http://www.bnpparibas.ca> for more information on BNP Paribas, in \
Canada.


[prev in list] [next in list] [prev in thread] [next in thread]