Just one in a while an invention comes along that just changes the rules. This is it, "3do" is a shock impact absorbing goo that modifies it'w own structure on impact. Soft and bendable most of the time but locks rigid under impact. This will change clothing in key ways just like "Velco" fastener did in the past.
Lets hope that this product of long hard work brings rewards to the inventor Richard Palmer as well as the exploiters. An example use is for Ipod protection with this goo can be see on Tech21 website.
Gannett
Monday, 31 August 2009
Thursday, 20 August 2009
Advice about data corruption events
Detection – The following items should be seen as warning signs of possible data corruption
• Unexpected exits from normally stable work jobs; any process or database abnormalities should be cause for concern.
• Failure of routine process that scan or search data volumes and file systems ( e.g.: Fsck, backups, catalog processes )
• Hardware I/O errors regardless of whether they are recoverable or not. Especially San, i/o paths and memory
Awareness – these activities are seen as high risk activities for any storage environments
• Frequent reconfiguration or replacement of storage objects.
• Microcode/firmware upgrades ( HBA, switch, array )
• San, Switch and Storage reconfigurations.
Prevention – These activities can help early detection of corruption problems
• Perform test restores of backups, check restored data integrity is sane.
• Scheduled execution of file system metadata and database integrity checks.
• Have spare reliable, tested storage available for immediate deployment, for use in a crisis.
• Maintain records of all i/o path and system device configurations, ( e.g. San, network diagrams and configuration detail)
Investigation – Review these points in the event of a data corruption investigation.
• Retain all log files. Do not let normal daily roll over wipe the evidence (e.g. syslog, alert log, engine log, san switch logs)
• Facilitate early engagement between vendors of all interconnect components.
• Retain or capture copies of corrupted storage objects, the content, size and location of corruption will be used to form theories during investigations.
• Be proactive around scanning the wider estate for similar issues.
The above is very general high level advice. If you wish to obtain specific implementation advice on a per-platform, per-process, per-product or target environment basis please contact your technical support provider.
• Unexpected exits from normally stable work jobs; any process or database abnormalities should be cause for concern.
• Failure of routine process that scan or search data volumes and file systems ( e.g.: Fsck, backups, catalog processes )
• Hardware I/O errors regardless of whether they are recoverable or not. Especially San, i/o paths and memory
Awareness – these activities are seen as high risk activities for any storage environments
• Frequent reconfiguration or replacement of storage objects.
• Microcode/firmware upgrades ( HBA, switch, array )
• San, Switch and Storage reconfigurations.
Prevention – These activities can help early detection of corruption problems
• Perform test restores of backups, check restored data integrity is sane.
• Scheduled execution of file system metadata and database integrity checks.
• Have spare reliable, tested storage available for immediate deployment, for use in a crisis.
• Maintain records of all i/o path and system device configurations, ( e.g. San, network diagrams and configuration detail)
Investigation – Review these points in the event of a data corruption investigation.
• Retain all log files. Do not let normal daily roll over wipe the evidence (e.g. syslog, alert log, engine log, san switch logs)
• Facilitate early engagement between vendors of all interconnect components.
• Retain or capture copies of corrupted storage objects, the content, size and location of corruption will be used to form theories during investigations.
• Be proactive around scanning the wider estate for similar issues.
The above is very general high level advice. If you wish to obtain specific implementation advice on a per-platform, per-process, per-product or target environment basis please contact your technical support provider.
Tuesday, 18 August 2009
My Mac G4 moves data at 3,335,443.25 T.Byte a second
My Mac G4 can move huge a amounts of data in a flash. It says so right here in the activity monitor .. Wow, no faking no photo shop honest that what it says.
Gannett
Subscribe to:
Posts (Atom)