I gladly, and knowingly pay the $10 a month rental. I have a closet full of old hardware (anyone want a V.Everything modem?). And if there is a problem they can get into it remotely. A new cable modem with 16x4 and GigE will run about $180 for a new modem with router. That means I will spend about $60 more on my 2 year contract. And when I get done I will not have yet another piece of hardware to put in the closet.
So if you go strictly by the view rate, 13 million. That extra cost for a $1,000,000 advertisement would be a whole 7 cents. Since most adds are well under $1M it would be even less.
That big dark cloud, at least the dark part, is called soot. It is simply carbon. As emissions go the fact you can see it is by far the least of your worries. Worse are things like sulfates, which you can not see. And is why all diesel sold on the US for vehicles is low sulfur.
As for the emissions of a gasoline engine. Those emissions are much higher, and much more deadly. And comes mainly not from the gasoline, but its additives. This is why we regulate gasoline engines so much.
The issue is we can only tell when one is about a day out. Many times we can only see them as they are leaving, not aproaching. It is actually a fairly common occorance. You can see them at http://www.spaceweather.com/. Since the begniing of the year there have been 5 that have come close enough to actually be of note.
What the author fails to realize is that the limiting factor on a SAN is most often the host itself, not the disk. A single disk my not have the IO, but an array most certainly does (depends on array). A standard, 33 MHz PCI bus can only transfer 133Mb/s (theoretical max). Even faster buses still do not match the I/O speed or throughput of a SAN.
The limiting factor on a PC is that southbridge chip, not the storage. The vast majority of the systems typically connected simply can not push the I/O fast enough out of its ports. It is not waiting on disk, it is waiting on the IO of its bridge chip and bus. Of course putting it on a ram disk is faster. RAM sits off the north bridge and therefore has better throughput to the CPU.
This is more a limit of bridge chips and PC architecture then the speed of a SAN.
I demand, any PowerPoint slide I created that was later re-used, a cut of the quota profit sales received. I demand, any spreadsheet I have made as a work for hire, a royalty anytime it is updated.
Does anyone here build houses? Make cars? Build anything that was sold to someone?
Living in Texas, with oil and gas, wells I can personally attest to damage done by service trucks to our road. This is due to to constant need to move the product to market, or service the water that comes from the wells (yes gas and oil wells produce water too).
I have seen these trucks that carry the crude oil from gas wells get into accidents. I have seen bridges totally destroyed from burning oil under them (concrete breaks down under the extreme heat).
Do we write about the millions of dollars in damage our oil trucks create yearly? Or do we single out a few accidents in trucking, carrying oversize loads instead.
Do we even hear about the oversize building moments that tie up traffic? Do we hear about the daily fatal accidents from truck accidents? Or do we single out a few trucks that just happened to be carrying wind turbine parts?
Hard drives do not write to the *exact* same position all the time. Additionally when they do so they effect more then the precise amount of magnetic medium below the write heads. It is technically feasible (with modification of the firmware on the drive or physically removing platters) to half step the read heads and read the spaces next to where data was written.
Devices that do this generally take one drive and attach another that can hold the recovered data. A simple search in your favorite search engine with "forensic data recovery" will revel companies that can do this and hardware available for the task.
A CFL contains about 5 mg of mercury, about enough to cover the point of a ball point pen. Let's say it breaks in a room that has a volume of about 25 m^3 (which is about a medium sized bedroom). The entire 5 mg of mercury vaporizes immediately (an very unlikely occurrence), resulting in an airborne mercury concentration in this room of 0.2 mg/m^3. This concentration will decrease with time, as air in the room leaves and is replaced by air from outside or from a different room. As a result, concentrations of mercury in the room will likely approach zero after about an hour or so.
Even with these relatively conservative assumptions, this level and duration of mercury exposure is not likely to be dangerous, as it is lower than the US Occupational Safety and Health Administration (OSHA) standard of 0.05 mg/m3 of metallic mercury vapor averaged over *eight* hours. The EPA recommends that (1) you immediately open windows to reduce mercury concentrations inside your home; (2) you do not touch the spilled mercury; (3) you clean up the broken CFL glass carefully and immediately (but not with your hands or a vacuum cleaner), and (4) you wipe the affected area with a paper towel to remove all glass fragments. Please note it is the glass they are worried more about then the mercury.
The issue with mercury in the CFL bulbs is not one of it breaking in your house. It is what happens when we put millions into landfills.
Yes, quite allot actually as I do storage for a living.
First off raid6 failures protect against hard drives that were all made at the same time and installed. This is true if your bought the array, as an array, from a vendor. But if you made it yourself from multiple disks the changes of parallel failure is negligible. And as far as raid6 goes I spend a considerable amount of time converting 6+2 raid 6 arrays into 7+1 raid 5 arrays. In these cases 12TB would be very small.
I also have my own disk arrays at home. Less for enterprise storage and more for those HD ATSC recordings my myth box makes. In it is a 4TB 5x1TB SATA array with a hardware raid card (really it is driver assisted). Aside from the slow write performance (it is expected with raid5) they run fine.
Reading the posting I wonder to myself if he has every watched a raid array rebuild. For that matter has even watched a SAN attached array work. Yes it takes time to rebuild (depends on the size of the disk). But other then slow access time that array when it is rebuilding it is rather transparent to the hosts using the array (not to mention it is pretty hard to saturate and enterprise raid array).
Why someone would mirror a set of mirrors (1+1 or 11) is beyond my understanding. Many of my customers use raid 1+0 (for speed). I have even seen customers use raid 5+1, but we tend to call that "paranoid raid".
I tend to agree. Take for the example of "Self Healing". It sounds nice, but it is not the SAN it heals its just the array. And more often the SAN itself has problems then the arrays. This would be a mis-configured SAN, with single attached hosts and hosts without multipathing software. Or an array mis-attached to the SAN.
Disk drives fail, and fail more often in batches by lot then by mistaken identity. When your drive tells you it is going bad it is so that you can get the data off safely, before it dies. Not mark one platter bad and use the rest. So do you really want your disks to lie about problems?
But no, wait, we will add some flashy lights and guauges. They are about as useful as the oil light on your dash. Without context and without knowing overall trends they are useless.
Use a few technical terms, well mis-use them. To this add falsely what is the bane of SAN admins (no it is not "No Fault Found"), and you have a marketing release about an array.
Make an array that can tell me "look idiot you plugged both HBAs into the same switch". Oh wait, that is called SRM software.
In my experience I have great demand not for 100Gbps Ethernet, but Fibre Channel. It is a common problem is replicating data between data centers. The high end approach to this is to get two DWDM switches and dark fiber (if you can afford it).
The main problem with transporting large data segments over Ethernet is quite simple. Data is read off disk (typically) at 8KB chunks, then converted to 1.5Kb Ethernet packets. This "fragmenting" and additional overhead is what causes allot of the resultant lag.
I fly as much as you, but I seem to have a distinctly different idea of what is "difficult".
1) You will NOT catch anything from the floor if you take your shoes off. No not even if you take off your socks. Why? becase the floor is not wet, nor is it warm. The TSA actually did a study about this and to paraphrase what it said, it is "extremely small to remote" to contract athlete's foot.
2) I check my bag, carry on my two laptops. Yes sometimes I get asked why I have two laptops. I tell them one is personal, one is for business. That is all it takes.
3) Yes I put my shoes in a bin. Yes I have been told to take them out. Yes at the same airport. Was it really that hard to do it, no.
4) No I do not bring things to drink though security. But do you really need to get something before that plane takes off? They will give you something on the plane anyway.
About the only thing I agree with is that the TSA is not really providing security. But then again if they REALLY wanted to be secure most Americans would be denied access to airplanes. And I am sure many more would complain about just how intrusive a detailed background check really is.
If you are getting your TV from an ATSC, DVB-S or DVB-C card you can probably (I say probably because I have not tried every combination), use EIT. In fact I use EIT on my ATSC cards to ensure Zap2It (it is really DiataDirect), is correct.
The grid itslef is comprised ov V20Z servers. Depending on which datacenter you are talking about they are either dual 2.0Ghz or dual 2.2Ghz, each with 4G of RAM. They have no disks and are booted via PXE.
The racks themselves have 32 systems, 4 racks make a pod (there was some discussion to call 2 rakcs a podlet). Depending on which datacenter you are talking about there are up to 3 pods.
There are also some management servers that are really not worth mentioning. They serve as the infrastructure to boot the pods etc.
One thing that is not put out on Sun's site is the pods will (and do) run Linux. You do not *have* to use Sol10 it is just that there are no Linux Infiniband drivers for the Infiniband (and yes thats about 2 tons of infinband cable connecting them, well ok in one data center).
If you would read the WHOLE blog you would find out they have 2 OC3 circuits. And Bell did loose them when they were down to a single T1.
They also noted when Bell went to their building to fix it (yes they can see the building where they get the OC3 so it is not a long haul). As for Bell yes they too have generators sand as someone already posted a nice set of batteries.
Yes the DishPVR runs Linux. It is a 2.4 kernel and they use XFS.
1) Take its drive out and put it in a Linux box 2) Mount the partitions of the hard drive (its formatted with XFS)/dev/hdc1/mnt/DN/download xfs defaults,noatime,nodiratime 0 0/dev/hdc5/mnt/DN/root xfs defaults,noatime,nodiratime 1 1/dev/hdc6/mnt/DN?next_root xfs defaults,noatime,nodiratime 0 0/dev/hdc8/mnt/DN?video xfs defaults,noatime,nodiratime 0 0
Yes like the TiVo boxes a Dishnet PVR used pivot root (hdc5 and hdc6). Most of the hack stuff is in python. Go mount, play, hack, whatever you want.
Look up
pythonshell.py: A telnet shell for the box ( command line python). telnetd-wrapper.py: The telnet server (runs bash, It really just stripes out CR, but hey it works). python-bash.py: Your bash shell
(Obvious links to hacked software omitted intentionally).
Some notes about the aritcle
on
Basics of RAID
·
· Score: 1
In the article a few things are omitted that would be important to note if you were building your own array.
1) The article notes raid 0+1. Raid 0+1 is VERY dangerous. You want 1+0 not 0+1. The main reason is loss of any disk from a 0+1 will immediately degrade your array. Also keep in mind vendors call this 1/0, 1+0, and 10. Also keep in mind vendors LIE about 1+0 vs 0+1
2) The alternative to 1+0 is raid 5. Raid 5 had some significant drawbacks to its use. These are read-modify-write and the calculation of checksums. In fact, unless you get higher end raid controllers, it is incredibly slow. Software raid 5 is even worse. So be careful here too.
Since none of this is new groundbreaking material by all means go look up whatever storage solution you decide on implementing. Learn how each solution works and your normal utilization.
Actually the amount of traffic a tracker gets is substantial. It is directly related to how many users there are in the cloud. The way the tracker works is to track the meta-data from the clients (what parts they have) so it can broadcast it back out.
It is not nearly as large as the amount of bandwidth needed to distribute your data but it is still quite significant. Don't take my word for it, set one up and try it yourself.
First they are not dumb ternimals, far from it. It is called a SunRay. If you want to know more about them, try http://www.sun.com/products/sunray/.
Amongst other things you can take your SunRay card, pull it from your terminal and go put it in another. As long as the SunRay is on the same system you get your exact desktop back. With SunRay you also dont waste the vast amount of computing resources in your workplace. Don't take my word for it, go ask distribted.net. And that is just for wasted CPU cycles.
Second it is called Flexable Field Office. This means that you do NOT have to go into to the office to work. It is BECAUSE of this meany of the Sun workers were NOT in the World Trade Center Last September 11. You also do not have to be in your home town to go to an office to do work. Where it made sense, some employes kept their offices.
Ever wish you could telecommute?
Yes Sun even pays for its workers home office equipment and Internet access so they can work.
First you are talking about a very large storage
system. Of course, you are talking about alot of storage. It does not, however, need to be all one type. If you use a product such as SAMFS you can get the benefit of extending that to other media. As mentioned before, silo's would be a good adjunct to this system.
Calling SAMFS HSM software short changes it. It
is far more then that. With it you can have multiple systems read the same volume. It has HSM parts wich will migrate data from one stoage medium to the next leaving a part of it on the original media (as set by an admin). It also makes backups of those archives making it also a backup product.
It has the added benefit of using QFS as its file system. It stores the metadata seperately. Meaning that you can restore the entire system if you have one of its archive copies and a copy of its metadata file. The metadata file is of course much smaller then the data tislef so you can effectivly restore the system in a matter of minutes where it normaly would have taken hours and days.
SAMFS is also one of the few procuts (maybe even the only one) that can realy drive the storage media at drive rated speeds. Ask anyone what they realy get off their drives and you will find it is usualy about 2/3 of its throughput.
Finaly keep in mind you can use things other then tape. You could put it on optical storage as a longer term solution.
Finaly, while you will get some good information from slashdot you realy should enguage a storage specialist for this. Many of the storage companies have them. If you have any doubts about doing this, then get help. Because what you set in your data center today will come back to you in the future. It is much easier to impliment then to migrate.
Slashdot Mirror
I gladly, and knowingly pay the $10 a month rental. I have a closet full of old hardware (anyone want a V.Everything modem?). And if there is a problem they can get into it remotely. A new cable modem with 16x4 and GigE will run about $180 for a new modem with router. That means I will spend about $60 more on my 2 year contract. And when I get done I will not have yet another piece of hardware to put in the closet.
From one of many Hulu's own case studies, 13 million views, 106K total votes
http://www.hulu.com/advertising/case-studies/oscars
So if you go strictly by the view rate, 13 million. That extra cost for a $1,000,000 advertisement would be a whole 7 cents. Since most adds are well under $1M it would be even less.
That big dark cloud, at least the dark part, is called soot. It is simply carbon. As emissions go the fact you can see it is by far the least of your worries. Worse are things like sulfates, which you can not see. And is why all diesel sold on the US for vehicles is low sulfur.
As for the emissions of a gasoline engine. Those emissions are much higher, and much more deadly. And comes mainly not from the gasoline, but its additives. This is why we regulate gasoline engines so much.
The issue is we can only tell when one is about a day out. Many times we can only see them as they are leaving, not aproaching. It is actually a fairly common occorance. You can see them at http://www.spaceweather.com/. Since the begniing of the year there have been 5 that have come close enough to actually be of note.
What the author fails to realize is that the limiting factor on a SAN is most often the host itself, not the disk. A single disk my not have the IO, but an array most certainly does (depends on array). A standard, 33 MHz PCI bus can only transfer 133Mb/s (theoretical max). Even faster buses still do not match the I/O speed or throughput of a SAN.
The limiting factor on a PC is that southbridge chip, not the storage. The vast majority of the systems typically connected simply can not push the I/O fast enough out of its ports. It is not waiting on disk, it is waiting on the IO of its bridge chip and bus. Of course putting it on a ram disk is faster. RAM sits off the north bridge and therefore has better throughput to the CPU.
This is more a limit of bridge chips and PC architecture then the speed of a SAN.
Lets see how far we can take this.
I demand, any PowerPoint slide I created that was later re-used, a cut of the quota profit sales received.
I demand, any spreadsheet I have made as a work for hire, a royalty anytime it is updated.
Does anyone here build houses? Make cars? Build anything that was sold to someone?
Living in Texas, with oil and gas, wells I can personally attest to damage done by service trucks to our road. This is due to to constant need to move the product to market, or service the water that comes from the wells (yes gas and oil wells produce water too).
I have seen these trucks that carry the crude oil from gas wells get into accidents. I have seen bridges totally destroyed from burning oil under them (concrete breaks down under the extreme heat).
Do we write about the millions of dollars in damage our oil trucks create yearly? Or do we single out a few accidents in trucking, carrying oversize loads instead.
Do we even hear about the oversize building moments that tie up traffic? Do we hear about the daily fatal accidents from truck accidents? Or do we single out a few trucks that just happened to be carrying wind turbine parts?
Hard drives do not write to the *exact* same position all the time. Additionally when they do so they effect more then the precise amount of magnetic medium below the write heads. It is technically feasible (with modification of the firmware on the drive or physically removing platters) to half step the read heads and read the spaces next to where data was written.
Devices that do this generally take one drive and attach another that can hold the recovered data. A simple search in your favorite search engine with "forensic data recovery" will revel companies that can do this and hardware available for the task.
A CFL contains about 5 mg of mercury, about enough to cover the point of a ball point pen. Let's say it breaks in a room that has a volume of about 25 m^3 (which is about a medium sized bedroom). The entire 5 mg of mercury vaporizes immediately (an very unlikely occurrence), resulting in an airborne mercury concentration in this room of 0.2 mg/m^3. This concentration will decrease with time, as air in the room leaves and is replaced by air from outside or from a different room. As a result, concentrations of mercury in the room will likely approach zero after about an hour or so.
Even with these relatively conservative assumptions, this level and duration of mercury exposure is not likely to be dangerous, as it is lower than the US Occupational Safety and Health Administration (OSHA) standard of 0.05 mg/m3 of metallic mercury vapor averaged over *eight* hours. The EPA recommends that (1) you immediately open windows to reduce mercury concentrations inside your home; (2) you do not touch the spilled mercury; (3) you clean up the broken CFL glass carefully and immediately (but not with your hands or a vacuum cleaner), and (4) you wipe the affected area with a paper towel to remove all glass fragments. Please note it is the glass they are worried more about then the mercury.
The issue with mercury in the CFL bulbs is not one of it breaking in your house. It is what happens when we put millions into landfills.
MacOS 10.5 and 10.5 server are UNIX03 Single UNIX Specification certified. It meets the criteria for UNIX.
It passes POSIX certification. It has a shell environment. And it has base C header definitions.
It is UNIX certified. But UNIX is a certification. And as such so are AIX, HP/UX, SCO, Solaris, Tru64, and z/OS.
Yes, quite allot actually as I do storage for a living.
First off raid6 failures protect against hard drives that were all made at the same time and installed. This is true if your bought the array, as an array, from a vendor. But if you made it yourself from multiple disks the changes of parallel failure is negligible. And as far as raid6 goes I spend a considerable amount of time converting 6+2 raid 6 arrays into 7+1 raid 5 arrays. In these cases 12TB would be very small.
I also have my own disk arrays at home. Less for enterprise storage and more for those HD ATSC recordings my myth box makes. In it is a 4TB 5x1TB SATA array with a hardware raid card (really it is driver assisted). Aside from the slow write performance (it is expected with raid5) they run fine.
Reading the posting I wonder to myself if he has every watched a raid array rebuild. For that matter has even watched a SAN attached array work. Yes it takes time to rebuild (depends on the size of the disk). But other then slow access time that array when it is rebuilding it is rather transparent to the hosts using the array (not to mention it is pretty hard to saturate and enterprise raid array).
Why someone would mirror a set of mirrors (1+1 or 11) is beyond my understanding. Many of my customers use raid 1+0 (for speed). I have even seen customers use raid 5+1, but we tend to call that "paranoid raid".
I tend to agree. Take for the example of "Self Healing". It sounds nice, but it is not the SAN it heals its just the array. And more often the SAN itself has problems then the arrays. This would be a mis-configured SAN, with single attached hosts and hosts without multipathing software. Or an array mis-attached to the SAN.
Disk drives fail, and fail more often in batches by lot then by mistaken identity. When your drive tells you it is going bad it is so that you can get the data off safely, before it dies. Not mark one platter bad and use the rest. So do you really want your disks to lie about problems?
But no, wait, we will add some flashy lights and guauges. They are about as useful as the oil light on your dash. Without context and without knowing overall trends they are useless.
Use a few technical terms, well mis-use them. To this add falsely what is the bane of SAN admins (no it is not "No Fault Found"), and you have a marketing release about an array.
Make an array that can tell me "look idiot you plugged both HBAs into the same switch". Oh wait, that is called SRM software.
In my experience I have great demand not for 100Gbps Ethernet, but Fibre Channel. It is a common problem is replicating data between data centers. The high end approach to this is to get two DWDM switches and dark fiber (if you can afford it).
The main problem with transporting large data segments over Ethernet is quite simple. Data is read off disk (typically) at 8KB chunks, then converted to 1.5Kb Ethernet packets. This "fragmenting" and additional overhead is what causes allot of the resultant lag.
I fly as much as you, but I seem to have a distinctly different idea of what is "difficult".
1) You will NOT catch anything from the floor if you take your shoes off. No not even if you take off your socks. Why? becase the floor is not wet, nor is it warm. The TSA actually did a study about this and to paraphrase what it said, it is "extremely small to remote" to contract athlete's foot.
2) I check my bag, carry on my two laptops. Yes sometimes I get asked why I have two laptops. I tell them one is personal, one is for business. That is all it takes.
3) Yes I put my shoes in a bin. Yes I have been told to take them out. Yes at the same airport. Was it really that hard to do it, no.
4) No I do not bring things to drink though security. But do you really need to get something before that plane takes off? They will give you something on the plane anyway.
About the only thing I agree with is that the TSA is not really providing security. But then again if they REALLY wanted to be secure most Americans would be denied access to airplanes. And I am sure many more would complain about just how intrusive a detailed background check really is.
#4 Use EIT http://www.mythtv.org/wiki/index.php/EIT
If you are getting your TV from an ATSC, DVB-S or DVB-C card you can probably (I say probably because I have not tried every combination), use EIT. In fact I use EIT on my ATSC cards to ensure Zap2It (it is really DiataDirect), is correct.
The grid itslef is comprised ov V20Z servers. Depending on which datacenter you are talking about they are either dual 2.0Ghz or dual 2.2Ghz, each with 4G of RAM. They have no disks and are booted via PXE.
The racks themselves have 32 systems, 4 racks make a pod (there was some discussion to call 2 rakcs a podlet). Depending on which datacenter you are talking about there are up to 3 pods.
There are also some management servers that are really not worth mentioning. They serve as the infrastructure to boot the pods etc.
One thing that is not put out on Sun's site is the pods will (and do) run Linux. You do not *have* to use Sol10 it is just that there are no Linux Infiniband drivers for the Infiniband (and yes thats about 2 tons of infinband cable connecting them, well ok in one data center).
If you would read the WHOLE blog you would find out they have 2 OC3 circuits. And Bell did loose them when they were down to a single T1.
They also noted when Bell went to their building to fix it (yes they can see the building where they get the OC3 so it is not a long haul). As for Bell yes they too have generators sand as someone already posted a nice set of batteries.
Yes the DishPVR runs Linux. It is a 2.4 kernel and they use XFS.
/dev/hdc1 /mnt/DN/download xfs defaults,noatime,nodiratime 0 0 /dev/hdc5 /mnt/DN/root xfs defaults,noatime,nodiratime 1 1 /dev/hdc6 /mnt/DN?next_root xfs defaults,noatime,nodiratime 0 0 /dev/hdc8 /mnt/DN?video xfs defaults,noatime,nodiratime 0 0
1) Take its drive out and put it in a Linux box
2) Mount the partitions of the hard drive (its formatted with XFS)
Yes like the TiVo boxes a Dishnet PVR used pivot root (hdc5 and hdc6). Most of the hack stuff is in python. Go mount, play, hack, whatever you want.
Look up
pythonshell.py: A telnet shell for the box ( command line python).
telnetd-wrapper.py: The telnet server (runs bash, It really just stripes out CR, but hey it works).
python-bash.py: Your bash shell
(Obvious links to hacked software omitted intentionally).
In the article a few things are omitted that would be important to note if you were building your own array.
1) The article notes raid 0+1. Raid 0+1 is VERY dangerous. You want 1+0 not 0+1. The main reason is loss of any disk from a 0+1 will immediately degrade your array. Also keep in mind vendors call this 1/0, 1+0, and 10. Also keep in mind vendors LIE about 1+0 vs 0+1
2) The alternative to 1+0 is raid 5. Raid 5 had some significant drawbacks to its use. These are read-modify-write and the calculation of checksums. In fact, unless you get higher end raid controllers, it is incredibly slow. Software raid 5 is even worse. So be careful here too.
Since none of this is new groundbreaking material by all means go look up whatever storage solution you decide on implementing. Learn how each solution works and your normal utilization.
Actually the amount of traffic a tracker gets is substantial. It is directly related to how many users there are in the cloud. The way the tracker works is to track the meta-data from the clients (what parts they have) so it can broadcast it back out.
It is not nearly as large as the amount of bandwidth needed to distribute your data but it is still quite significant. Don't take my word for it, set one up and try it yourself.
As a military member who suffers from military planners I can assure you we would rather have paper maps.
Without the map you are dead meat. With anything electronic I have to depend upon power, end of statment.
Yes we use technology. Yes it helps us. But when it counts, I want my compass and a map (and that tactical overlay).
: HELLO ."Hello World " ;
First they are not dumb ternimals, far from it. It is called a SunRay. If you want to know more about them, try http://www.sun.com/products/sunray/. Amongst other things you can take your SunRay card, pull it from your terminal and go put it in another. As long as the SunRay is on the same system you get your exact desktop back. With SunRay you also dont waste the vast amount of computing resources in your workplace. Don't take my word for it, go ask distribted.net. And that is just for wasted CPU cycles.
Second it is called Flexable Field Office. This means that you do NOT have to go into to the office to work. It is BECAUSE of this meany of the Sun workers were NOT in the World Trade Center Last September 11. You also do not have to be in your home town to go to an office to do work. Where it made sense, some employes kept their offices.
Ever wish you could telecommute?Yes Sun even pays for its workers home office equipment and Internet access so they can work.
And Sun saved money doing it.
First you are talking about a very large storage
system. Of course, you are talking about alot of storage. It does not, however, need to be all one type. If you use a product such as SAMFS you can get the benefit of extending that to other media. As mentioned before, silo's would be a good adjunct to this system.
Calling SAMFS HSM software short changes it. It
is far more then that. With it you can have multiple systems read the same volume. It has HSM parts wich will migrate data from one stoage medium to the next leaving a part of it on the original media (as set by an admin). It also makes backups of those archives making it also a backup product.
It has the added benefit of using QFS as its file system. It stores the metadata seperately. Meaning that you can restore the entire system if you have one of its archive copies and a copy of its metadata file. The metadata file is of course much smaller then the data tislef so you can effectivly restore the system in a matter of minutes where it normaly would have taken hours and days.
SAMFS is also one of the few procuts (maybe even the only one) that can realy drive the storage media at drive rated speeds. Ask anyone what they realy get off their drives and you will find it is usualy about 2/3 of its throughput.
Finaly keep in mind you can use things other then tape. You could put it on optical storage as a longer term solution.
Finaly, while you will get some good information from slashdot you realy should enguage a storage specialist for this. Many of the storage companies have them. If you have any doubts about doing this, then get help. Because what you set in your data center today will come back to you in the future. It is much easier to impliment then to migrate.
No, of course they don't. But this will
You can edit and save them back to the same
format if you want).
And of course it is free.
Star Office http://www.sun.com/products/staroffice/get.html