Hal, StorageTek? You mean SUN don't you?
If you have a preference for SUN DASD, then they have a line of storage that I unreservedly recommend over what once was the StorageTek V Series. (GD&R) If you're replacing PPRC-XD then you must be considering Snap to Primary, which is more like Nanocopy or Metro Mirror. You don't mention your network requirements, but with SUN's PowerPPRC (AFAIK) you can only use ESCON links, which somewhat reduces the technology available for Channel extension if you intend to use a WAN. If you are using Fibre Channel links already with your Shark, then you will have to replace the X-site topology with ESCON. Ron > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Hal Merritt > Sent: Wednesday, 18 January 2006 4:15 AM > To: [email protected] > Subject: StorageTek DASD? > > We are looking at the StorageTek 'V series' DASD as a possible upgrade > path, We are currently one local and one remote 2105-800 Shark > interconnected with PPRC XD. We are heavy PAV and some Flashcopy II. The > other site is currently inactive (BR only), but our strategic direction > is twin sites, each being the other's offsite backup. > > > > Total farm size 2-4 tb. We must have the sub millisecond response time > we now enjoy with the Shark. And the Sharks' reliability/fault tolerance > has been important. > > > > Any thoughts, suggestions, words of wisdom? And experiences you would be > willing to share? > > > > > > Thanks. > > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
