You are here
Conph1g - Mon, 2011/11/21 - 19:38
The backup is made in the root not mnt drive and it only just fits
- How do I redirect backup away from the 9Gb root drive
- If I use a symbolic link, does (ephemeral) /mnt survive a restart or reboot? or will I have to attach an EBS and fstab it? Would either of these restore?
- Will I need to reconfigure Duplicity /tmp as in Restoring from a large (7GB+) backup fails
Thanks
Forum:
We deployed a tweak for this a while ago...
We deployed a tweak for this a while ago, which mount binds /tmp to /mnt/tmp so you can take advantage of the ephemeral storage.
The tweak is applied to all newly deployed servers, but if you need to apply it manually to a running server then it should be something like this:
Ephemeral storage should survive a reboot, but not a start-stop (ebs backed).
If you would like the mount binding to happen automatically on reboot / start-stop, the following should help (note that you don't need to do this on newly launched instances:
FIRSTBOOT_MNTTMP=/usr/lib/inithooks/firstboot.d/26ec2-mnttmp EVERYBOOT_MNTTMP=/usr/lib/inithooks/everyboot.d/26ec2-mnttmp cat > $FIRSTBOOT_MNTTMP <<EOF #!/bin/bash -e # mount bind /mnt/tmp (ephemeral storage) on /tmp is_mounted() { mount | grep -q "^\$1 on \$2 " return \$? } # skip if already mounted is_mounted /mnt/tmp /tmp && exit 0 mkdir -p /mnt/tmp chmod 777 /mnt/tmp/ chmod o+t /mnt/tmp/ cp -ar /tmp/* /mnt/tmp/ >/dev/null 2>&1 || true mount --bind /mnt/tmp /tmp EOF chmod +x $FIRSTBOOT_MNTTMP cp $FIRSTBOOT_MNTTMP $EVERYBOOT_MNTTMPI hope the above helps...
I think that covers it and
I think that covers it and goes the extra mile too. I'll also add a couple of paranoia options for overbackup
-- thanks for being comprehensive, responsive and......
awesome
Add new comment