A diagram of an 'air wand' indicating the location of cooling vents in wand, a key feature of a patent application by Google data center engineers:
It's nice to see that Google is dedicating not only significant engineering but also legal resources, towards patenting innovative data center cooling techniques. Hopefully, this will lead to an affordable, reusable solution that can help organizations similarly optimize their cooling. As has been documented, cooling typically contributes to up to 50% of a data center's total energy costs (e.g. see for example The Greening of IT: How Companies Can Make a Difference for the Environment by John Lamb, p. 136), so of course cooling innovations can be quite significant towards reducing both carbon footprint and operating costs..
"Google Patent Reveals Data Center Innovations
November 30th, 2009 : Rich Miller
Google has revealed some of the secret technology inside its mighty data centers, but its engineers are busy cooking up new secrets.
An example: Google is seeking to patent an advanced data center cooling system that provides precision cooling inside racks of servers, automatically adjusting to temperature changes while dramatically reducing the energy required to run chillers.
The cooling design, which could help Google slash the power bill for its servers, reinforces Google’s focus on its data centers as a competitive advantage in its battle with Microsoft and other rivals for leadership in cloud computing. The company has customized much of the operation of its data centers, which serve as the engines powering its massive Internet business. Google builds its own servers and networking switches, and now appears to be customizing the racks that hold them.
Precision Cooling via ‘Air Wands’
The innovative rack cooling design features an adjustable piping system, including “air wands” that provide small amounts of cold air to components within a server tray. The chilled air enters the top of a rack through two vertical standpipes, which branch off into air wands – long, thin pipes lined with vents that release cold air.
The air wands can pivot to target cold air on specific components, or be swung to one side to allow equipment to be removed from the rack. Dampers on each standpipe can open and close to regulate the volume of air flowing into the pipe and air wands, while the vents on each individual air wand can be adjusted to point up or down, allowing for a highly configurable system..."
Full Article from Data Center Knowledge: http://www.datacenterknowledge.com/archives/2009/11/30/google-patent-reveals-data-center-innovations/
Musings on personal and enterprise technology (of potential interest to professional technoids and others)
Monday, November 30, 2009
Google Patent for Data Center Cooling Innovations - Data Center Knowledge
Posted by
dgftest
at
11:46 AM
0
comments
Labels: environment, Google, green-computing, Infrastructure, TCO
Friday, September 25, 2009
Measurement + Monitoring of Data Centre Energy Use Immature Through 2011: Gartner
As previously posted, "cheap" servers really aren't cheap at all (Infoworld 5/2008), since recurring server operational costs are often as large or larger than the initial hardware capital investment. Below is a related update from Gartner, reminding us that "you can't manage what you can't measure". Here is Gartner's explanation of the importance of metrics for reducing data-center energy consumption [emphasis mine]:
Gartner Says Measurement and Monitoring of Data Centre Energy Use Will Remain Immature Through 2011:
“...when asked which energy management metrics they will use in the next 18 months, 48 per cent of respondents have not even considered the issue of metrics. However, without metrics it is impossible to get accurate data, which is essential to evaluating basic costs, proportioning these costs to different users and setting policies for improvement.
'These metrics form the bedrock for internal cost and efficiency programmes and will become increasingly important for external use', said Mr Kumar. 'Organisations that want to publicise their carbon usage through green accounting principles will need to have their basic energy use continuously monitored.'
Mr Kumar also urged organisations not to rely on internal metrics saying that evaluating server energy needs to be done in an open and transparent manner...”
hat tip / source: http://twitter.com/Gartner_inc/statuses/4339604501
Posted by
dgftest
at
1:20 PM
1 comments
Labels: Enterprise-Architecture, green-computing, Infrastructure, monitoring, policies, TCO
Tuesday, September 1, 2009
Gmail outage resolved thanks to flexible technical architecture [Official Gmail Blog]
Google's Site Reliability Czar: A clear explanation of today's gmail outage, as quoted below.
IMHO, as painful and widespread as the outage was (a side-effect of "routine upgrades"), urgent and ultimately successful action was taken towards resolution. And of course, the true "secret sauce" that enabled this resolution, is the underlying foundation of the "flexible capacity" which "is one of the advantages of Google's architecture".
Here is the full Official Gmail Blog post:
Official Gmail Blog: More on today's Gmail issue: Tuesday, September 01, 2009 6:59 PM
Posted by Ben Treynor, VP Engineering and Site Reliability Czar
"Gmail's web interface had a widespread outage earlier today, lasting about 100 minutes. We know how many people rely on Gmail for personal and professional communications, and we take it very seriously when there's a problem with the service. Thus, right up front, I'd like to apologize to all of you — today's outage was a Big Deal, and we're treating it as such. We've already thoroughly investigated what happened, and we're currently compiling a list of things we intend to fix or improve as a result of the investigation.
Here's what happened: This morning (Pacific Time) we took a small fraction of Gmail's servers offline to perform routine upgrades. This isn't in itself a problem — we do this all the time, and Gmail's web interface runs in many locations and just sends traffic to other locations when one is offline.
However, as we now know, we had slightly underestimated the load which some recent changes (ironically, some designed to improve service availability) placed on the request routers — servers which direct web queries to the appropriate Gmail server for response. At about 12:30 pm Pacific a few of the request routers became overloaded and in effect told the rest of the system 'stop sending us traffic, we're too slow!'. This transferred the load onto the remaining request routers, causing a few more of them to also become overloaded, and within minutes nearly all of the request routers were overloaded. As a result, people couldn't access Gmail via the web interface because their requests couldn't be routed to a Gmail server. IMAP/POP access and mail processing continued to work normally because these requests don't use the same routers.
The Gmail engineering team was alerted to the failures within seconds (we take monitoring very seriously). After establishing that the core problem was insufficient available capacity, the team brought a LOT of additional request routers online (flexible capacity is one of the advantages of Google's architecture), distributed the traffic across the request routers, and the Gmail web interface came back online.
What's next: We've turned our full attention to helping ensure this kind of event doesn't happen again. Some of the actions are straightforward and are already done — for example, increasing request router capacity well beyond peak demand to provide headroom. Some of the actions are more subtle — for example, we have concluded that request routers don't have sufficient failure isolation (i.e. if there's a problem in one datacenter, it shouldn't affect servers in another datacenter) and do not degrade gracefully (e.g. if many request routers are overloaded simultaneously, they all should just get slower instead of refusing to accept traffic and shifting their load). We'll be hard at work over the next few weeks implementing these and other Gmail reliability improvements — Gmail remains more than 99.9% available to all users, and we're committed to keeping events like today's notable for their rarity."
Posted by
dgftest
at
10:40 PM
0
comments
Labels: Change-Management, Enterprise-Architecture, Google, Infrastructure, ITSM, monitoring
Tuesday, July 7, 2009
35 Green IT Resources - IT Management
35 Green IT Resources - IT Management: "A number of IT vendors — from PC providers to software manufacturers — are now offering products and services to support environmentally sustainable business operations for companies of all sizes. Below is a roundup of the 35 most accessible, effective and promising green IT resources now available..."
This nice list from Lea Hartog of ITManagement.com provides helpful links related to Green IT information related to:
- Consulting Services (eco-consultants)
- Green PCs
- Eco-Loving Laptops
- Addtional Hardware (including info re: the HP Photosmart D5463 Printer and the SPARKLE Calibre P960 Green Power graphics card )
- Sustainable Software Solutions (such as GreenPrint )
- Recycling and Reuse
Posted by
dgftest
at
6:46 PM
1 comments
Labels: green-computing, Infrastructure, mobile-computing
Tuesday, June 30, 2009
Data Center Overload, Tom Vanderbilt, NYTimes 8-Jun-2009
For those of us already keenly aware of the various business-related and environment-related benefits of reducing datacenter and related power consumption, Tom Vanderbilt's article is a must-read. Published in the recent New York Times Sunday magazine's Architecture Issue, Vanderbilt presents a refreshing and enlightening review of why we should continue to care deeply about these issues, and follow through with practical energy-reducing measures in managing technology and other infrastructure. This is one of the overall best articles on this topic seen by technosurfer in quite some time :)
The Architecture Issue - Data Center Overload - NYTimes.com: "...Much of the daily material of our lives is now dematerialized and outsourced to a far-flung, unseen network. The stack of letters becomes the e-mail database on the computer, which gives way to Hotmail or Gmail. The clipping sent to a friend becomes the attached PDF file, which becomes a set of shared bookmarks, hosted offsite. The photos in a box are replaced by JPEGs on a hard drive, then a hosted sharing service like Snapfish. The tilting CD tower gives way to the MP3-laden hard drive which itself yields to a service like Pandora, music that is always “there,” waiting to be heard.
But where is “there,” and what does it look like?"
“There” is nowadays likely to be increasingly large, powerful, energy-intensive, always-on and essentially out-of-sight data centers. These centers run enormously scaled software applications with millions of users. To appreciate the scope of this phenomenon, and its crushing demands on storage capacity, let me sketch just the iceberg’s tip of one average individual digital presence: my own. I have photos on Flickr (which is owned by Yahoo, so they reside in a Yahoo data center, probably the one in Wenatchee, Wash.); the Wikipedia entry about me dwells on a database in Tampa, Fla.; the video on YouTube of a talk I delivered at Google’s headquarters might dwell in any one of Google’s data centers, from The Dalles in Oregon to Lenoir, N.C.; my LinkedIn profile most likely sits in an Equinix-run data center in Elk Grove Village, Ill.; and my blog lives at Modwest’s headquarters in Missoula, Mont. If one of these sites happened to be down, I might have Twittered a complaint, my tweet paying a virtual visit to (most likely) NTT America’s data center in Sterling, Va. And in each of these cases, there would be at least one mirror data center somewhere else — the built-environment equivalent of an external hard drive, backing things up.
Small wonder that this vast, dispersed network of interdependent data systems has lately come to be referred to by an appropriately atmospheric — and vaporous — metaphor: the cloud. Trying to chart the cloud’s geography can be daunting, a task that is further complicated by security concerns. “It’s like ‘Fight Club,’ ” says Rich Miller, whose Web site, Data Center Knowledge, tracks the industry. “The first rule of data centers is: Don’t talk about data centers.”
Yet as data centers increasingly become the nerve centers of business and society — even the storehouses of our fleeting cultural memory (that dancing cockatoo on YouTube!) — the demand for bigger and better ones increases: there is a growing need to produce the most computing power per square foot at the lowest possible cost in energy and resources. All of which is bringing a new level of attention, and challenges, to a once rather hidden phenomenon. Call it the architecture of search: the tens of thousands of square feet of machinery, humming away 24/7, 365 days a year — often built on, say, a former bean field — that lie behind your Internet queries.
[etc...] As James Hamilton of Amazon Web Services observed recently at a Google-hosted data-center-efficiency summit, there is no Moore’s Law for power — while servers become progressively more powerful (and cheaper to deploy) and software boosts server productivity, the cost of energy (as well as water, needed for cooling) stays constant or rises. Uptime’s Brill notes that while it once took 30 to 50 years for electricity costs to match the cost of the server itself, the electricity on a low-end server will now exceed the server cost itself in less than four years — which is why the geography of the cloud has migrated to lower-rate areas.
The huge power draws have spurred innovation in the form factor of the data center itself. For its Chicago center, Microsoft is outfitting half the building with shipping containers packed with servers. “Imagine a data center that’s about 30 megawatts, with standard industry average density numbers you can probably fit 25,000 to 30,000 servers in a facility like that,” says Microsoft’s Chrapaty. “You can do 10 times that in a container-based facility, because the containers offer power density numbers that are very hard to realize in a standard rack-mount environment.”
The containers — which are pre-equipped with racks of servers and thus are essentially what is known in the trade as plug-and-play — are shipped by truck direct from the original equipment manufacturer and attached to a central spine. “You can literally walk into that building on the first floor and you’d be hard pressed to tell that building apart from a truck-logistics depot,” says Manos, who has since left Microsoft to join Digital Realty Trust. “Once the containers get on site, we plug in power, water, network connectivity, and the boxes inside wake up, figure out which property group they belong to and start imaging themselves. There’s very little need for people.”
“Our perspective long term is: It’s not a building, it’s a piece of equipment,” says Daniel Costello, Microsoft’s director of data-center research, “and the enclosure is not there to protect human occupancy; it’s there to protect the equipment.”
From here, it is easy to imagine gradually doing away with the building itself, and its cooling requirements, which is, in part, what Microsoft is doing next, with its Gen 4 data center in Dublin. One section of the facility consists of a series of containers, essentially parked and stacked amid other modular equipment — with no roof or walls. It will use outside air for cooling. On our drive to Tukwila, Manos gestured to an electrical substation, a collection of transformers grouped behind a chain-link fence. “We’re at the beginning of the information utility,” he said. “The past is big monolithic buildings. The future looks more like a substation — the data center represents the information substation of tomorrow.”
Tom Vanderbilt is the author of “Traffic: Why We Drive the Way We Do (and What It Says About Us).”
Posted by
dgftest
at
8:43 PM
0
comments
Labels: DRP, green-computing, ILM, Infrastructure, storage, Web 2.0
Sunday, April 5, 2009
Is There a Sub-Subnotebook in Your Future?, NYTimes, 12/1992 :)
Dell's tiny-footprint Netbooks seem to be selling nicely... This, despite concerns as to whether a full set of traditional corporate standard software (including anti-virus, anti-malware etc.) can run and be managed efficiently on a relatively modestly powered machine. Some say the Netbook's success to date, is partially due to the current economic situation ( see for example, CNet's "Faltering economy boosting Netbooks" ). Hopefully for Dell, the success of the Netbook will continue regardless of the economy.
In case there was any doubt however, this is definitely not the first attempt at making a popular "Sub-Subnotebook"... One example was written up nicely by Peter H. Lewis of the New York Times in December of 1992:
Is There a Sub-Subnotebook in Your Future?:
"... Taking advantage of recent advances in miniaturization, computer makers are creating portable computation and communications devices that can easily be carried in one hand or tucked into a coat pocket. But at some point the usefulness of small systems comes into question: Most information is still entered by typing, and no one has yet managed to miniaturize executive fingers.
That hasn't stopped some companies... from creating personal computers that are about the size of a calculator..."
Posted by
dgftest
at
10:54 PM
0
comments
Labels: Infrastructure, mobile-computing, security, TCO, Upgrade-Treadmill
Wednesday, May 21, 2008
Green IT numbers don't lie - Sustainable IT, Ted Samson, InfoWorld 2008.05.15
Some interesting metrics on server operational costs... Indeed, the TCO is way higher (e.g. several hundred percent over a 3-year lifespan), than the hardware invoice ;-)
And the dollar figures, if they tend to follow gasoline, are only going up
Green IT numbers don't lie , May 15, 2008, Ted Samson, Sustainable IT, InfoWorld: "...$1,870 - The annual operating expense for powering and cooling a single midtier ($2,500) server in a tier III datacenter. The number is $1,320 for a tier II datacenter, and it reaches $2,020 in a tier IV datacenter. According to the report, 'servers are often housed in a higher tier datacenter than necessary, further driving facility costs.' The point, of course, is that 'cheap' servers really aren't cheap at all, so the 'throwing hardware at the problem' approach isn't particularly sustainable..."
Posted by
dgftest
at
4:41 PM
0
comments
Labels: green-computing, Infrastructure, TCO
Thursday, April 10, 2008
Turning off can be a business turn on - Backbone Magazine, Mar-Apr/2008
Interesting ideas from Backbone Magazine for personal computer power supply unit efficiencies in desktops, laptops, as per the article below (it will be interesting to learn in addition, what if anything has been done about this recently by Dell,HP,Lenovo,Toshiba,Gateway etc.)....
You can also watch Urs Hoelzle describe and present these and related ideas via
YouTube - Urs Hoelzle, Google Goes Carbon Neutral at Press Day Paris ).
Here is a blurb from that Backbone Magazine article by Jim Harris:
Backbone Magazine - Turning off can be a business turn on: "...as Google pointed out in a recent report, the PC industry could save 40 billion kilowatt-hours of electricity over three years — or more than US$5 billion in power at current California electricity rates — at “virtually no cost” by simply updating the design of power supply units used in computers.
Urs Hoelzle and Bill Weihl of Google point out typical PC power supplies use 65 to 80 per cent more power than necessary because the power supply units (PSUs) provide multiple output voltages, even though modern computer components no longer require this. Multiple voltages are a legacy of computing requirements from 25 years ago. By moving to a super-efficient 12-volt standard, power supply makers would also cut their production costs, as mono-voltage PSUs are simpler and less expensive to manufacture.
The Google findings were presented in a white paper titled “High-efficiency power supplies for home computers and servers” at the Intel Developer Forum in September 2006.
Also, that 40 billion kWh savings figure is based on only updating PSUs in 100 million PCs. Given that estimates place the worldwide number of PCs at one billion by the end of 2008, simple solutions such as turning computers off at night and efficient PSUs will save billions of kilowatt hours of electricity, save billions of dollars, reduce billions of tons of carbon globally — and all at a profit. So what are we waiting for? Perhaps it is only when a carbon tax is imposed on businesses — either voluntarily as in the case of HSBC or nationally as the Conference Board of Canada recommended in a January report entitled Use Green Taxes and Market Instruments to Reduce Greenhouse Gas Emissions — that we will really begin to appreciate that green saves money."
Posted by
dgftest
at
9:25 AM
0
comments
Labels: environment, Google, green-computing, Infrastructure
Monday, March 17, 2008
VoIP gets handle on protection - Financial Post 13-Mar-2008
An interesting taxonomy of VOIP security threats (standard view; print-formatted: VoIP gets handle on protection ):
"...VoIPshield Systems Inc., an Ottawa-based software firm that develops products to secure voice communications on IP networks, warns that attacks on VoIP systems can fall into one or more of five categories.
These include privacy intrusion (call eavesdropping, call recording and voice mail tampering); availability (denial of service attacks, buffer overflow attacks and malware); authenticity (registration hijacking, caller ID spoofing and sound insertion; theft (toll fraud/service theft) and data theft through masquerading data as voice and data network crossover attacks; and voice spam, known as SPIT, which includes unsolicited calling, voice mailbox stuffing, and something called vishing (voice phishing)..."
Posted by
dgftest
at
9:20 PM
0
comments
Labels: authentication, Infrastructure, monitoring, privacy, security, VOIP, wireless
Sunday, January 20, 2008
A Pragmatist's Guide to Structuring IT Asset Data, Scott Parkin, eWeek, 2008-01-18
A nice article describing the real-world ILM challenges for IT asset management. The ITSM benefits of of linking the asset's service-incident history to the incident-management system, including hard and soft costs per outage, seem significant. However, this does not seem common among the vast majority of the COTS helpdesk systems I have seen over the years, and certainly not among the Service Management modules of major ERP systems, let alone with integrated continuous auto-discovery/maintenance of all hardware and software assets found on the network... sigh....
Here is a snippet from the full eWeek article :
"... Track initial acquisition costs, including asset purchase, required peripheral or supporting devices, operating system and software (as needed), and service contracts:
Most of this data will come from purchase orders; some will need to be calculated as a pro-rata share of a bulk purchase or license agreement.
For new purchases, update your purchasing process to include calculating and tracking this data in your asset record; for existing assets you will need to create a project to go back and aggregate/calculate this information and add it to your asset records.
Track ongoing maintenance costs, including annual service contracts, upgrade or replacement parts and the costs associated with Service Desk incidents for each device.
Ideally, this information is collected at the time of purchase or service and is immediately attached to the asset's service history record as a function of your established process. You should update your Incident management process to support this, whether you update the asset record manually or through automated technology.
This can be the single most daunting task in the mix; extracting and aggregating historical data for existing assets is a gargantuan task. Many organizations choose to simply start tracking this data as of a specific date and leave existing data unstructured. This is a good method for those organizations that are resource-constrained and willing to wait for highly qualified data.
Identify replacement costs for hardware, software and infrastructure elements. Remember to include both disposal costs for existing assets and install/deployment costs for new assets.
For commodity items such as end-user hardware (desktop, laptop) and software, these costs should be predictable within a range and will tend to be updated once a year as new contracts are negotiated.
For high-impact or high-value items, the cost of purchase may only be a small part of the total costs, and those costs may be difficult to estimate. This data is intended for planning purposes and should be reviewed at the time of planning, so supply a best estimate with supporting documentation to be used as a starting point for further research, not as an authoritative declaration.
The key benefit here is being able to quickly view approximate costs for individual assets, to aggregate that data by department or cost center and to use that data in research and planning efforts...."
Posted by
dgftest
at
1:03 PM
0
comments
Labels: ERP, ILM, Infrastructure, ITIL, ITSM, Service-Management, TCO, Workflow
Tuesday, December 18, 2007
Re: "New Cooling Technologies Tackle Data Center Heat", InformationWeek 9/06
As is well known, for all their benefits, blades introduce major additional heat into your server rack... And although cooling requirements can be addressed in a number of ways, not everyone is keen on the idea of introducing water into a mission-critical data-center :-)
"...Georgia Institute of Technology is using new technology that moves cooling systems closer to the source of the heat to save about $160,000 annually in utility bills. Jeffrey Skolnick, director for the university's Center for the Study of Systems Biology, oversaw the installation of an $8.5 million supercomputer where space and power considerations were crucial. It includes a 1,000-node cluster of servers in 12 racks using IBM's BladeCenter system; IBM's rear-door heat eXchanger, which places chilled water directly behind servers, does the cooling.
IBM's eXchanger, introduced last year, solves several problems in the 1,300-square-foot center. It needed only half the air conditioning expected--80 tons instead of 160 tons--and reduced airflow lowered noise. With four more racks to fill in the coming months, Skolnick is looking at chip-level cooling to cut power costs further. 'At the time, [the heat eXchanger] was the most viable technology,' he says. 'Every time you do an upgrade, the rules change, and you have to look and see what's available.'
The idea of introducing water or other liquids into a data center scares some IT managers because water can damage computer components and cause short circuits. Imagine a burst water pipe or a liquid sprayer gone awry. But there may not be a good alternative, says Leonard Ruff, an associate principal at Callison, a data center design firm. Callison, which has been testing the SprayCool M-Series, thinks direct chip cooling is so effective that a business can double the amount of electricity used to power computers and boost the number of servers in a rack without overheating a data center, resulting in a 285% increase in processing capability. Callison now markets the system to its customers.
More companies will adopt water-cooled technology even though there is "an almost unreasonable" resistance to water among data center managers, predicts Gartner analyst Carl Claunch. He recommends that businesses include infrastructure for water cooling when building new data centers even if there are no immediate plans for implementing such equipment. They'll eventually need to pipe in water because it's so efficient at cooling, he reasons...."
Posted by
dgftest
at
6:12 PM
0
comments
Labels: environment, green-computing, Infrastructure
Wednesday, December 12, 2007
software? hardware? TRAINING! "Securing the Laptop: Mission Impossible?" eWeek 11/07
Some relevant vendor products listed here, to help prevent data and/or hardware loss or theft:
Securing the Laptop: Mission Impossible?: Page 2: "...make the USB drive itself the trusted device. RedCannon's KeyPoint Alchemy, for example, encrypts USB devices and implements policy management rules for their use. Similarly, VMware's ACE 2 implements a virtual PC, with security policies, on a USB drive. 'The USB drive is a manageable asset,' Gartner's Girard said. 'It will cost you some money, but you can do it.' The epidemic of laptop thefts has spurred other, more novel approaches. Absolute Software's Computrace LoJack for Laptops works much the same as the LoJack automobile anti-theft device. When a stolen system is connected to the Internet, it sends out a signal that enables it to be traced. The signaling works even if the hard drive is removed and installed in another system..."
However, the huge grain of salt is that "user education and training is a not-to-be-neglected component of any laptop security program.
A recent study by the Computing Technology Industry Association found that only 42 percent of companies had either completed or planned a mobile computing user security education program. Perhaps that reticence has something to do with the difficulty of implementing an effective program.
'How do you communicate to businesspeople in a manner they can understand and relate to?' said Eric Litt, chief information security officer at General Motors. 'That's the skill. It may be more art than science. You have to build credibility.'"
NOTE: A somewhat old but still IMHO highly relevant resource from the US National Institute of Standards and Technology, including suggested topics for security awareness training:
Building an Information Technology Security Awareness and Training Program
Posted by
dgftest
at
12:26 AM
0
comments
Labels: Infrastructure, mobile-storage, policies, security, training
Thursday, November 15, 2007
Managed Backup Strategy: "Cotton Companies Walks the Walk", eWeek 8oct2007
An interesting approach to centralized backup strategy (apparently no mention however, of required network bandwidth required for those distributed sites)- for a company specializing in disaster-recovery -:)
Cotton Companies Walks the Walk: "...Asigra's Televaulting is the first agentless solution to deliver bare-metal restoration capabilities across distributed or multisite networks, said Colesante. Agentless means there is no need to install client software on target machines, while bare metal means the software restores servers without the need to load applications or files. Televaulting has two main components—a client, which resides at a customer site, and a server, which resides at a WAN-connected data center. Televaulting's technology performs a full backup followed by incremental, minor backups..."
Posted by
dgftest
at
9:45 PM
0
comments
Labels: Infrastructure, security, storage
Saturday, May 19, 2007
File Replicating / Synchronization - RedDot CMS Users | Google Groups
File Replicating / Synchronization - RedDot CMS Users | Google Groups
From the Google group for RedDot CMS Users (seems like a very practical suggestion from an excellent source :-)
"CMS publishing is the single most intensive process relating to
pretty much all aspect of the system, processor speed, disk speed and
network speeds are all heavily used. The thing to remember when
dealing with publishing is that, while you may only be setting up one
publishing job, if you are publishing to muliple servers, the job is
repeated each time for each server.
If you have multiple web servers and are using a load balancer, I
generally recommend that you set the CMS server up to publish to a
staging machine (an older, phased peice of hardware that is just
sitting around since so many company's seem to have them lately, and
then do exactly what everyone else has said and use something that
will monitor the folder and push the staging publish out to the web
servers, Cute FTP pro works really well for this and is only $69.00
(usd)
This actually serves two purposes. First, it cuts the publication time
down so that only one publishing job is involved and secondly, it
ensures uniformity throughout your live web servers.
I am currently running some benchmark tests relative to publishing and
should have that information in the next week or so.
Andrew Salik, Project Manager
RedDot Solutions, NA"
Posted by
dgftest
at
10:52 PM
0
comments
Labels: CMS, Infrastructure, RedDot
