I'm trying to backup and restore an EBS volume on EC2.
I want to clear up some confusion and clarify understanding on EC2 instances being EBS backed.
If you start an AMI from a community image, configure your server as you want it configured, then use the "create image" option from the EC2 dashboard to create a snapshot, that snapshot (image) can be used to create more servers with your configuration and is considered EBS-backed, yes?
If you create
imaging a situation where your vCentre is so locked down that the only thing you can do is: mount iso's and stop/start VMs.
This is what i have. What i dont have, is a method of backing up my VMs. The options that i see are available as I see it, following a catastrophic failure of the VM e.g rm -rf / whatever, are:
1.
Our mysql ibdata1 file was deleted earlier today. This wasn't noticed until mysqld was restarted and there was no data in the tables. The machine is a CentOs VM in Xenserver. At this point a snapshot was taken. Then the mysql database was dropped and restored from a backup.
I'd like to backup my XEN VMs by copying-rsyncing a LVM snapshot.
I’m trying to mount a snapshot that contains a XEN guest’s virtual disk (ext4).
Below are all the steps I follow.
There's a command in the AWS EC2 API called ec2-register or ec2reg which has an argument -s for snapshot ID. You are able to create an image from a snapshot. I'd like to be able to do this in Python (currently using boto), but it doesn't look like it's built in functionality within boto yet. Is there still a way using boto to create an image from a snapshot id?
after creating a VSS snapshot I'd like to be able to query the USN journal.
I have a EC2 Ubuntu server on Amazon cloud and I'm trying to clone an instance "X" by creating a snapshot of the instance and creating an AMI from that snapshot.
The problem is: When creating the AMI, the Kernel used in the instance "X" is not available and if I choose another one, the server isn't booting correctly.
Steps that I've done
-Kernel ID of instance "X" is aki-825ea7eb
-The default ker
I'm using reprepro to maintain a Private Package Archive of internal packages. There is no straightforward way to keep multiple version of a package available using reprepro (see here), but it does have a snapshot facility that sort of works.
But only sort of. I don't see a good way to go back to a snapshot version.