3

Can't mount after EBS snapshot and restore on Ubuntu 12.04

view full story
linux-howto

http://serverfault.com – I'm trying to backup and restore an EBS volume on EC2. So this is what I'm doing: ec2-create-snapshot <ebs volume> -d <snapshot name> ec2-create-volume --snapshot <snapshot code> -z us-east-1a ec2-run-instances ami-82fa58eb -n 1 -g default -k <keypair> -t m1.large -z us-east-1a (That is an instance of ubuntu 12.04) ec2-attach-volume <restored volume code> -i <instance code> -d /dev/sdf sudo mkdir /mongo (the directory that the volume was mounted on the original instance) sudo mount /dev/xvdf /mongo -t ext4 -o defaults,auto,noatime,noexec I get the followi (HowTos)

dayu's picture
Submitted by dayu on 07/30/2012 – Made popular on 07/30/2012

Stories similar to Can't mount after EBS snapshot and restore on Ubuntu 12.04

I will admit that my understanding of the following is a little hazy, however, it seems that if I create a new logical volume as follows

Code: sudo lvcreate -L1G -s -n livesnapshots /dev/kvm-server/vm-storage It creates successfully. I then mount this to /mnt/snapshots and sure enough I can see the file system as existing in the original volume.

I've recently tried to migrate our instance-store EC2 server to an EBS-backed version, but things are going wrong.

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

We've been using Win2008R2's AD Snapshot feature to perform a nightly backup of our AD domain. I'm trying to figure out the steps that I need to run through to use one of these nightly backups to restore our AD domain on a 2nd server.

These are the commands we used to backup the AD DOM:

1.

I'm looking through this guide for how to add an EBS volume to an Amazon EC2 instance, and I've found this little part of instructions hard to follow:

Create an XFS file system on the EBS volume and mount it as /vol

grep -q xfs /proc/filesystems || sudo modprobe xfs sudo mkfs.xfs /dev/sdh

echo "/dev/sdh /vol xfs noatime 0 0" | sudo tee -a /etc/fstab sudo mkdir -m 000 /vol sudo mount /vol

after creating a VSS snapshot I'd like to be able to query the USN journal.

I use Proxmox 2.2 for making OpenVZ containers.

It ships with a tool called vzdump that can create backups of OpenVZ containers on the fly. It uses snapshot functionality of LVM to create temporary "fork" of filesystem for backup purposes.

Unfortunately it sometimes crashes with one container that performs a lot of disk operations.

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.

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