Amazon.com Case Study
- Elimination of complex and time-consuming tape capacity planning. Amazon.com is growing larger and more dynamic each year, both organically and as a result of acquisitions. AWS has enabled Amazon.com to keep pace with this rapid expansion, and to do so seamlessly. Historically, Amazon.com business groups have had to write annual backup plans, quantifying the amount of tape storage that they plan to use for the year and the frequency with which they will use the tape resources. These plans are then used to charge each organization for their tape usage, spreading the cost among many teams. With Amazon S3, teams simply pay for what they use, and are billed for their usage as they go. There are virtually no upper limits as to how much data can be stored in Amazon S3, and so there are no worries about running out of resources. For teams adopting Amazon S3 backups, the need for formal planning has been all but eliminated.
- Reduced capital expenditures. Amazon.com no longer needs to acquire tape robots, tape drives, tape inventory, data center space, networking gear, enterprise backup software, or predict future tape consumption. This eliminates the burden of budgeting for capital equipment well in advance as well as the capital expense.
- Immediate availability of data for restoring – no need to locate or retrieve physical tapes. Whenever a DBA needs to restore data from tape, they face delays. The tape backup software needs to read the tape catalog to find the correct files to restore, locate the correct tape, mount the tape, and read the data from it. In almost all cases the data is spread across multiple tapes, resulting in further delays. This, combined with contention for tape drives resulting from multiple users’ tape requests, slows the process down even more. This is especially severe during critical events such as a data center outage, when many databases must be restored simultaneously and as soon as possible. None of these problems occur with Amazon S3. Data restores can begin immediately, with no waiting or tape queuing – and that means the database can be recovered much faster.
- Backing up a database to Amazon S3 can be two to twelve times faster than with tape drives. As one example, in a benchmark test a DBA was able to restore 3.8 terabytes in 2.5 hours over gigabit Ethernet. This amounts to 25 gigabytes per minute, or 422MB per second. In addition, since Amazon.com uses RMAN data compression, the effective restore rate was 3.37 gigabytes per second. This 2.5 hours compares to, conservatively, 10-15 hours that would be required to restore from tape.
- Easy implementation of Oracle RMAN backups to Amazon S3. The DBAs found it easy to start backing up their databases to Amazon S3. Directing Oracle RMAN backups to Amazon S3 requires only a configuration of the Oracle Secure Backup Cloud (SBC) module. The effort required to configure the Oracle SBC module amounted to an hour or less per database. After this one-time setup, the database backups were transparently redirected to Amazon S3.
- Durable data storage provided by Amazon S3, which is designed for 11 nines durability. On occasion, Amazon.com has experienced hardware failures with tape infrastructure – tapes that break, tape drives that fail, and robotic components that fail. Sometimes this happens when a DBA is trying to restore a database, and dramatically increases the mean time to recover (MTTR). With the durability and availability of Amazon S3, these issues are no longer a concern.
- Freeing up valuable human resources. With tape infrastructure, Amazon.com had to seek out engineers who were experienced with very large tape backup installations – a specialized, vendor-specific skill set that is difficult to find. They also needed to hire data center technicians and dedicate them to problem-solving and troubleshooting hardware issues – replacing drives, shuffling tapes around, shipping and tracking tapes, and so on. Amazon S3 allowed them to free up these specialists from day-to-day operations so that they can work on more valuable, business-critical engineering tasks.
- Elimination of physical tape transport to off-site location. Any company that has been storing Oracle backup data offsite should take a hard look at the costs involved in transporting, securing and storing their tapes offsite – these costs can be reduced or possibly eliminated by storing the data in Amazon S3.
相關推薦
Amazon.com Case Study
Elimination of complex and time-consuming tape capacity planning. Amazon.com is growing larger and more dynamic each year, both organically an
Made.com Case Study
Amazon Web Services is Hiring. Amazon Web Services (AWS) is a dynamic, growing business unit within Amazon.com. We are currently hiring So
Edmunds Amazon Macie Case Study
By taking advantage of Macie, Edmunds can better discover, classify, and protect its data, giving administrators actionable information about p
Realtor.com Case Study
Realtor.com can easily scale its environment to support the growth of its Turbo Listings feature. “We are able to take advantage of
Brooks Brothers Amazon Chime Case Study
Amazon Web Services is Hiring. Amazon Web Services (AWS) is a dynamic, growing business unit within Amazon.com. We are currently hiring So
Shaadi.com Case Study
Pleased with the results of its Amazon Redshift adoption, the company decided to move its entire service to AWS. “We want vendors to manage as
Amazon Advertising Case Study
People performing product searches on the Amazon.com website or mobile app represent a very specific—and valuable—category of potential cus
Amazon CloudWatch Case Study
Adopting DynamoDB TTL enabled the CloudWatch team to cut its operational burden, since the team no longer has to manually manage table deletion
Blackboard & Amazon RDS Case Study
Blackboard delivers innovative education technology and services that enable millions of people worldwide to learn in schools, institutions, an
entradas.com Case Study
About a week after migrating to AWS, entradas.com had to deal with one of its biggest ticketing challenges. It was a soccer match that excited
Edmunds.com Case Study
Edmunds.com is significantly reducing its technology costs by running its website on the AWS Cloud. “We expect to save $32 million in the first
Amazon.com Items and Offers Case Study
The move of IMS to DynamoDB delivered all the benefits the team hoped for—and more. Previously, in preparation for peak-load events such as Ama
Amazon Prime Video Case Study
Amazon Prime Video measured the fan viewing experience by using video-stream metrics. “We paid close attention to the reliability of the video
AWS Case Study: SportPursuit.com
When SportPursuit founders Adam Pikett, Victoria Walton, and Rhys Jones first set up the company, they needed a platform that would enable them
Disc Jam Case Study: Supporting a Mission for Fast-Paced Competitive Gameplay with Amazon Gamelift
About High Horse Entertainment Having gained over 20 years’ experience at both Treyarch and Activision, where they worked on succ
AWS Case Study: Oasis.com
The stability and geographic locations of AWS—particularly in Europe and the United States—enabled Oasis.com to move its chat infrastructure eas
Amazon Wallet Service Case Study
Wallet must work all the time—even during a migration. Amazon sought to eliminate any impact on customer transactions, maintain complete data
Amazon Financial Systems Case Study
Across its many business entities, Amazon processes more than 20 billion financial transactions each month, including accounts receivable,
Amazon Web Services (AWS)AWS Case Study: MiHiN
Using AWS, MiHIN can scale without limit to support increasing volumes of patient information from healthcare providers and payers. “We’re that
AWS Case Study: BuildFax & Amazon Machine Learning
The image above shows the machine-learning process used by BuildFax. It feeds known roof age and property characteristic data of buildings into