user469

Can agree with you that 2 year on a 1.000 euro laser printer or a 10.000 euro server are not a bad investement , but 2 year on a 100.000 euro storage sure they are .

The over-reaction its due to the short lifetime of the product of just two years , usually customer buy product and expect to use it for at least five years . ( but in recent time its best not to use it more than three years , to keep up with innovation ) Apart form Oracle motivation i see only many disappointed customer

7x20 and bad news. Oracle array users skid off 7410 road map EOL procedure leaves array users boxed in A European Oracle 7410 array user has been told no more upgrades are possible after the end of the month - despite the fact that he only bought the 7410 this year. Oracle upgraded its 7000 open unified storage line last month. The products use ZFS. The existing 7110, 7310 and 7410 products were replaced by 7120, 7320 and 7420 ZFS Storage Appliance products. Oracle array users skid off 7410 road map ? Channel Register

Yes but windows 2003 compatibility lacks of mpio and sra/srm .

Phil, i do work for an ITSP and i am a technical designer specialist , 30 year experience in the computer field , modem and router , lan , wan , server , voip and storage . Regards, Alex

Phil, This is exactly the best practice to follow , start with a tray with 2 x LogZillas and then add same type of tray up to the fourth tray. I would recomend 1 x LogZillas every 11 disks . If someone needs massive IOPS its better to start with a tray with 4 x LogZillas and then add same type of tray up to the fourth tray. Regards, Alex

Phil, what i'm trying to figure out how performance will wary with a given number of LogZilla SSD using 1 to 4 jbod trays , or 5 to 8 trays , or 9 to 12 trays , because i will add more disks but SSD will remaing the same because of the limitation . Regards, Alex

We are using Bacula to backup some linux system to lto tape.

Phil, the problem is people still need compatibilty with Win 2003 not only with Win 2008 . Alex

The above applies only to clustered config , for single unit the limit is 6 LogZilla SSDs per system. Phil, this is the real problem my consideration if I start with 1 or 4 logzilla/tray : 1 logzilla with trays 1-4 i will have 74 data disks , 18 spares , 4 logzilla 0 logzilla with trays 5-8 i will have 151 data disks , 37 spares , 4 logzilla 0 logzilla with trays 9-12 i will have 228 data disks , 56 spares , 4 logzilla worst case performance disk/ssd ratio for 2 pools is 37/2 , 75/2 and 114/2 for 4 pools is 18/1 , 37/1 and 57/1 4 logzilla with trays 1-4 i will have 64 data disks , 16 spares , 16 logzilla 0 logzilla with trays 5-8 i will have 141 data disks , 35 spares , 16 logzilla 0 logzilla with trays 9-12 i will have 218 data disks , 54 spares , 16 logzilla best case performance disk/ssd ratio for 2 pools is 32/8 , 70/8 and 109/8 for 4 pools is 16/4 , 35/4 and 54/4 for 16 pools is 4/1 , 9/1 and 14/1 This is only theoretical because after 8 jbods you have to add another sas hba so instead of having two column of 6 trays you have three column of 4 trays. Question is where i should put the fourth jbod with SSD ? My personal answer is better to avoid configuration that will grow up with more than 8 jbods for now if looking for performace . In the future we will see ... Alex

Phil, which document contains the informations ? Also how many pools can you create with 12 jbods ? Regards, Alex

Hello, does still has a limitation on number of logzilla ? Should have been 12 for a cluster , 6 on each node , and 18 for a single unit. Regards, Alex