| | |
| Software and Support |
| OS on Server |
Windows Server 2000 2003, 2008 |
| |
Linux RH AS 3 (32 and 64 bit) |
| OS on Client |
Windows XP, 2000, 2003, 2008 |
| Software Components |
FDA and Optima Storage Manager (including Access Control) |
| |
FDA and Optima Dynamic Snap Volume (license) |
| Storage Supported |
| |
FDA1400, FDA1500 |
| |
FDA2400, FDA2500 |
| |
FDA2800, FDA2900 |
| |
Optima1500, 3000 and 5000 |
| | |
| Application Server |
| OS Supported |
Windows Server 2000, 2003, 2008 |
| |
Windows Server 2003 (64 bit) |
| |
Linux AS 3, AS4 (32 bit) |
| |
Linux SLES (32 bit) |
| |
Linux AS 3, AS4 (64 bit) |
| |
Linux SLeS (64 bit) |
| |
Solaris 8,9 |
| |
HP-UX 11i, 11i V2 |
| |
AIX 5.1, 5.2, 5.3 (32/64 bit) |
| Software Components |
FDA and Optima Dynamic Snap Volume including Storage SnapControl CLI CD |
| |
Storage ReplicationControl SQL Option (special request) |
| | |
| Functions |
| Snapshot Operations |
| | • Snapshot Create
Snapshot is created instantaneously from Master volume.
• Snapshot Delete
Recovery of snapshot disk area through the deletion of old snapshots.
• Snapshot Restore
Master volume is restored instantaneously from the any generation of snapshot. |
| Link Volume |
| | One of the best features is the Link volume to give indirect access to an application with a snap. The created volume is accessing in writing the snap and as well the Master Volume, limited to test purpose (the Master Volume is obviously not updated). |
| Snapshot Configuration rules |
| | The snapshot reserved area is only available on RAID6.
Snap area zone should be allocated according to Master volume size. Example: MV is 2 TB, for 8 generations, allow 20% for snap reserved area.
Business application and back-up application should be located in different servers.
Master Volume and Replication Volume can be located on all types of RAID and pool. But note that dynamic pools are exclusively RAID6 |
| |
I 
International [
