Hi All..

First be gentle... I am on the sales guy..
I am new to open-e and would like to put it in my solution database for future customers...

The only chage to this EO is tat I want to Drop on of the x3650's and Use Acronis to push the image of their existing hp server to the new x3650 and use the HP as a cold backup. I am also thinking of dropping the asaptec nas for a Open-e Nas that is goin to be built on one of their exisitng free ntel dual-core workstations...


here is an Engineering Order I have to work with:


Project Description
Presently **** Distribution operates a single Microsoft Windows 2003 Small Business Server (SBS) that serves the roles of Domain Authentication, Network File Shares (SMB), Microsoft Exchange Server, and Microsoft SQL Server 2000. The primary application being used on this machine is Microsoft SQL Server 2000. This project will implement pseudo-high availability and rapid server/system recovery into the routine daily operation of **** Distribution’s primary server.
This project will be implemented in two phases. Phase one will migrate the current running production server onto a a new IBM x3650 server running as a non-virtualized system. This server will be configured with 3GB of RAM. The IBM x3650 server will have a total of 73GB’s of local storage space. This storage will be configured with two (2) 73GB 10K RPM SAS HDD’s in an accelerated RAID-1 array. Microsoft Windows Server 2003 Standard Edition will be utilized as the base operating system on this machine. All currently running services will migrate onto the base operating system of this new machine. Additional iSCSI-based storage will be added to migrate critical data storage off of the base operating system and onto a Network Attached Storage (NAS) device. An IBM iSCSI adapter card will be installed into this server and configured to mount storage made available by an Adaptec SNAP 520 server to be used as primary application storage. The SNAP device will be configured with 1TB of raw storage space partitioned into a total of 500GB usable in several RAID-1 arrays. A total of 6 arrays will be created according to the following schedule:
• Array0: SQL Data: 100GB: RAID1
• Array1: SQL TxLogs: 50GB: RAID1
• Array2: Exchange Data: 80GB: RAID1
• Array3: Exchange Logs: 50GB: RAID1
• Array4: User (NAS/SMB) Data: 70GB: RAID1
Arrays 0-3 will be created as unique iSCSI targets
Array 4 will be created as an SMB file sharing mount point for direct SMB connections.

At the completion of Phase one the current production environment for **** Distributing will exist on a new, highly reliable, IBM x3650 server with 3GB of RAM and 73GB of local storage space. All Microsoft Exchange database files will exist on E: (Array2), Microsoft Exchange transaction log files on F: (Array3), SQL Server database files on G: (Array0), and SQL Server transaction logs on H: (Array1). No movement of user data will be performed during this project scope, and therefore will not be migrated onto Array4.
A second identical IBM x3650 will be implemented as a hot-standby server that will permit rapid restoration of services using application data present on the SNAP server through the iSCSI network. This second server will hold a complete live image of the primary server. A semi-automated image capture/restore process will serve to capture the onging configuration of the primary x3650 server.

Phase Two will implement data protection and migrate system backups onto the new SNAP device. During Phase Two, a new LTO3 tape backup unit will be installed to be directly connected to the SNAP server and will utilize BakBone NetVault Workgroup Edition locally installed to the SNAP server to perform backups of data stored on the SNAP server. Once this backup process is fully functioning and tested the old server that has been running production will be migrated to a image server. This installation will automatically capture live running images of the production server and store those images locally on dual 300GB SATA HDD’s configured in a RAID-1 mirror. The standby server will be connected to the SNAP server via a new iSCSI card and will be ready for immediate manual deployment of the most recent image of the primary server in the event of a catastrophic failure.

At the completion of Phase two all production backups will be performed by the SNAP server to a new LTO3 drive that is directly connected via SCSI-3/LVD. A series of Disk-to-Disk-to-Tape (D2D2T) backup processes will be established to backup databases and transaction logs. Minimal nightly shutdown of database and email infrastructure will be required to ensure adequate binary backups are obtained.


Other Comments Concerning Scope of Work

Substantial network configuration will be performed as part of this project series. A separate iSCSI-only network will be established for the exclusive use of High-Speed iSCSI data transfers. No other devices should be connected to this network system.

Significant periods of system downtime will be required for phase one to be completed properly. These intervals should not endure beyond 1.5 hours in length but actual downtime lengths may vary based on existing systems performance.

CIT estimates the total time to recovery (TTR) for this solution taking into account a catastrophic failure of one (1) IBM x3650 server would be 2-2.5h. This solution does not account for catastrophic failure of the SNAP 520 NAS, it accounts solely for the failure of an IBM x3650 server.

CIT would recommend implementing a fully redundant Ethernet (LAN) network and fully redundant iSCSI network to further increase the fault tolerance of this solution. This would entail implementing one (1) additional iSCSI card in each IBM x3650 server and an additional two (2) LAN Switches. One LAN Switch would be utilized for iSCSI connectivity (10/100/1000 Ethernet) and the second would be utilized for Ethernet connectivity.

As part of a routine maintenance process for this solution, CIT recommends performing manual image updates to the standby server on a minimum of a monthly basis or immediately prior-to and following any substantial changes to the primary production server.


Questions:
Can Open-e replace the Adaptec NAS 520 server for less $$$?
Can Open-e utilize a tape backup and another source of recover?

All comments welcome...