PROMISEテクノロジー、Amazon S3へのバックアップが可能なNAS/iSCSI装置:ITpro

Media_httpitpronikkei_hbhyy

 バックアップ/リカバリでは、オンラインストレージ「Amazon S3」へ定期的にデータをバックアップ可能。また、遠隔地にあるNSx700シリーズ同士でバックアップや複製を実行するディザスタリカバリ環境を構築できる。バックアップツールとしては、米Acronis社のバックアップソフト「Acronis Backup & Recovey」が付属するほか、Windows Backup UtilityやMac OS XのTime MachineといったOS標準ツールなどを利用できる。

Practical Cloud Computing | Cloud Tips: How to Efficiently Forklift 1 Billion Rows into SimpleDB

SimpleDB Throttling

Now that you have created the requisite number of domains (say 100) that you need, you might think that you can just pump all this data into SimpleDB in a few hours,

Wrong!

Amazon imposes a concept of fairness on all users of the system. If you try to execute too many writes, Amazon starts returning 503 - Service Unavailable fast-fail responses to you. SDB throttles you.

How many put’s can you execute per second per domain?

My experience has been: 70 singleton puts/domain/sec

If you had 100 domains and could achieve 70 singleton puts/domain/sec, how long would it take you to forklift 1 Billion records?  It would take about 1.6 days.

In reality, the single put rate slows down the more full your domains become, so you don’t get this rate throughout.

Earlier this year, Amazon unveiled Batch Put . This gave me a 20x throughput improvement (I was inserting 20 items per batch put call) on nearly-empty domains. I did not trend how the batch put performed as my domains got more full, but my impression was that it was still much faster than the singleton put.

Now, if you have used PutAttributes or BatchPutAttributes, you will know that you can specify “replace=true” or leave the default “replace=false” option on each item. Leaving the default is much, much more efficient. If you know that you are fork-lifting brand new data, then this is the way to go.

■ SimpleDBへの書き込みのパフォーマンスは制限されている。
■ 70 singleton puts/ドメイン/秒
■ 503が返ったらエラー処理をしてリトライするなどする。
■ PutAttribues/BatchPutAttribuesの replaceはデフォルトを使う事。

AWS : rightsclae CentOS のインスタンスの空き容量

rightscale_images/CentOS5_0V4_0_1.img.manifest.xml

2010-01-15_16

[root@ip-10-251-199-223:~] df -H
Filesystem             Size   Used  Avail Use% Mounted on
/dev/sda1               11G   2.4G   7.7G  24% /
/dev/sda2              158G   197M   150G   1% /mnt
none                   892M      0   892M   0% /dev/shm

Cloud Developer Tips: The EC2 Instance Life Cycle

EBS-backed AMIs have a life cycle more similar to that of real computers:

EBS-backed AMI instances begin their lives when launched, spending some time in the "pending" state until the order is fulfilled. When the instances start booting they are "running". From there they can be rebooted or shut down, like S3-backed AMI instances. They can also be "stopped" (such as with the ec2-stop-instances command), from which they can be started again (e.g. with the ec2-start-instances command) or terminated.

http://aws.amazon.com/ec2/ には、On Demand Instanceに関して、「 Pricing is per instance-hour consumed for each instance type, from the time an instance is launched until it is terminated. Each partial instance-hour consumed will be billed as a full hour. 」とあるので微妙なところ。ただし、Reserved Instanceに関しては「Instance-hours are billed for the time that instances are in a running state; if you do not run the instance in an hour, there is zero usage charge.」と書いてある。
Shutting-downになるとコントロール不能なので、多分課金されないのでは。

State of the Cloud – January 2010 :: Jack of all Clouds :: Guy Rosen on Cloud Computing

Trends

The cloud marches forward! The past two months have been slower than usual (4-5% overall growth). On the one hand the cloud may have come in useful to handle the holiday traffic spikes, but on the other hand who wants to rock the boat at the most important time of the year, and just before your staff head out for vacation?

AWS:EBSを/dev/sdbにマウントしてext3でフォーマット

インスタンスとEBSのブロックは同じじゃないとマウントできないよ!


domU-12-31-39-04-30-F1:/# ls /dev/sd*
/dev/sda1  /dev/sda2  /dev/sda3  /dev/sdb

domU-12-31-39-04-30-F1:/# mkfs -t ext3 /dev/sdb
mke2fs 1.41.3 (12-Oct-2008)
/dev/sdb is entire device, not just one partition!
Proceed anyway? (y,n) y
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
13107200 inodes, 52428800 blocks
2621440 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
1600 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
    32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
    4096000, 7962624, 11239424, 20480000, 23887872

Writing inode tables: done                            
Creating journal (32768 blocks):
done
Writing superblocks and filesystem accounting information:
done

This filesystem will be automatically checked every 21 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.

domU-12-31-39-04-30-F1:/# mount -t ext3 /dev/sdb /home

domU-12-31-39-04-30-F1:/# df -H

Filesystem             Size   Used  Avail Use% Mounted on
/dev/sda1               11G   548M   9.5G   6% /
tmpfs                  895M      0   895M   0% /lib/init/rw
udev                   895M   447k   895M   1% /dev
tmpfs                  895M      0   895M   0% /dev/shm
/dev/sda2              158G   197M   150G   1% /mnt
/dev/sdb               212G   197M   201G   1% /home

RightScale Website Edition | Cloud Computing Management Platform by RightScale

Website Edition

The Website Edition has everything you need to run a customer-facing website on the cloud with scalability and reliability.

RightScale Website EditionKey Benefits

  • Everything you need to run scalable websites in the cloud
  • Autoscaling based on hardware and process-specific load metrics
  • Fully customizable and extensible infrastructure
  • Pre-designed ServerTemplates for fast deployment and time to market
  • Deployment level management and automation
  • Total control and transparency
  • Cloud portability and interoperability
  • Easy test and development using the clone environments option

Key Features

  • Web-based Management Dashboard
  • User permissioning
  • Lifecycle Support
  • Cloud-ready ServerTemplates
  • Multi-deployment, multi-server cluster management
  • Dynamic server configuration
  • Autoscaling based on load metrics
  • Load balancing front-ends
  • Redundant database with failover and recovery
  • Advanced graphical monitoring, alerting, and performance statistics
  • Centralized logging
  • Automated error handling and reporting

To find out more about deploying scalable websites with RightScale, visit our Cloud Computing Uses section.

2009-12-20 - 酋長の独り言

実はこのとき、私はもういいやと思ってインスタンスを落としてしまい、一瞬身動きがとれない状態になった。作り直すのも業腹だと思い、しばらく考えて、一度ローカルに落として、ローカルのAMIツールで西海岸にあげなおした。

またデフォルトのイメージはFedoraだが、この中でCentOSなら割と簡単にイメージを作ることができる。アマゾンマニュアルにも掲載されている。

しかし、作られたイメージは、インスタンスでは、そのイメージのカーネルが動くわけではなく、Xenカーネルで動くのでモジュールが何もない状況になってしまう。そこでアマゾンから対応する専用のモジュールダウンロードして、トップディレクトリ解凍してdepmod -aを実行するか再起動する。デベロッパーのサイトで議論されていた。でも、この部分がマニュアルに書かれていないのはなぜだろう。