You will need VIOS and it is supported with v6.1.1 or higher. There is some I/O concerns with XIV but with only three drives today, I would assume that XIV should be able to handle your workload. Also, I prefer the non-rack Power hardware to blades. This is because of the limitation of a single VIOS instance on a blade but since you have a blade chassis today, you could possibly look at two blades for redundancy.
Sirius Computer Solutions
Patrick Bingham | Principal Power Systems Engineer, Team Lead | 402-965-2381 | Cell: 402-212-2944
Fax: 402-965-2410 | E-mail: Patrick.Bingham@xxxxxxxxxxxxx
14301 FNB Pkwy, Suite 400, Omaha, NE 68154
National Technology Solutions Provider
www.siriuscom.com
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Denis Robitaille
Sent: Monday, March 28, 2011 9:10 AM
To: 'midrange-l@xxxxxxxxxxxx'
Subject: Rép. : Question of a Newbie to iSeries
2 - Our preferred storage for the task is the XIV. Anyone with experience with it ?
I understand that a virtual I/O server is required for it. Any comments on this ?
Here, we connect our Iseries to a DS8700. when you say "virtual I/O server", you mean using VIOS. This is an AIX partition on the same physical machine that will provide the connectivity between the Iseries partition and your SAN.
Denis Robitaille
Directeur Service technique TI
CASCADES INC.
412 Marie Victorin
Kingsey falls(Québec) Canada J0A 1B0
T : 819 363-6130
F : 819 363-6155
Mauricio Kanter <mkanter@xxxxxxxxxxxxxx> 2011-03-28 09:36 >>>
Good morning list.
I'm a newbie to iSeries ... My experience is with zSeries machines ... The company I work for acquired another company and my boss tasked me to check the gathering of info for a new AS/400 ... I apologize if some parts of my question are nonsense ... I just do not know the machine ... I will appreciate also answers to questions that I did not ask but I should have asked :-) Thank you in advance for your help.
The current situation is:
The AS/400 is a Desk Side 8203 - E4A machine running SS1 version 5.4. It has 8 GB memory and a 5364 processor. The processor is a 1Core 4.2GHz Power 6, Capacity CPW 4300/4300. It contains 3 disks of 140 GB - Which are RAID-1 mirrored totalling 420GB effective. It is backed up by an internal 800/1600 LTO4.
The data center landscape follows:
Our data center is based mostly on zSeries (z/OS and zLinux) and xSeries (virtualized blades running mostly ESX/Windoze and a few Linuxes). The blades are IBM BladeCenter Model H. There are MDSes to connect to the SAN fabric. Currently the Windows+Linux Storage is an XIV and the mainframe storage in a DS8700.
The window-linux backups nowadays are done using TSM with 3592 drives on an IBM-3494. They are going to be soon on a Netbackup solution using Clarion disks and two quantum 7000 robots with LTO5 drives. The new solution will be accesed via the SAN fabric.
The z/OS backups are executed today with a 7720 VTL (dasd-only) and a 3953 library manager and a TS3500 robot with 3592 drives. The VTL and the Library manager are accesed via the SAN fabric over FICON links.
Now the problems:
1 - We must upgrade it ASAP due to capacity and other issues.
We are considering either a blade center based PS700 or a rack mounted 8202-04B. Sounds good ?
2 - Our preferred storage for the task is the XIV. Anyone with experience with it ?
I understand that a virtual I/O server is required for it. Any comments on this ?
3 - Any possibility you see how we can backup using our current above mentioned backup equipment ? Any experience backing up the iSeries disks from a different machine ?
4 - Anyone with experience backing up with a TS3100 ? We are short of MDS ports at this time ... Any comments on how to connect a tape drive directly or library directly to a blade center not via the SAN fabric ?
5 - Any good resource for self-education on iSeries ? Links that it is worthwhile to look at ?
6 - Any comments on the migration to the new machine ?
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
This message (including any attachments) is intended only for
the use of the individual or entity to which it is addressed and
may contain information that is non-public, proprietary,
privileged, confidential, and exempt from disclosure under
applicable law or may constitute as attorney work product.
If you are not the intended recipient, you are hereby notified
that any use, dissemination, distribution, or copying of this
communication is strictly prohibited. If you have received this
communication in error, notify us immediately by telephone and
(i) destroy this message if a facsimile or (ii) delete this message
immediately if this is an electronic communication.
Thank you.
midrange.com
