Awesome! Also glad to hear your rate of success can be quantified as a 700% improvement. Amazing! :)<div><br></div><div>Best,<br>Enis<br><div><br><div class="gmail_quote">On Wed, Mar 28, 2012 at 2:57 PM, Greg Edwards <span dir="ltr">&lt;<a href="mailto:gedwards2@gmail.com" target="_blank">gedwards2@gmail.com</a>&gt;</span> wrote:<br>


<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_quote"><div>Enis,</div><div>Thanks, your instructions below worked ok and I have reduced my 700GB to 1 GB.</div>


<div>No doubt a pile of genome tools don&#39;t work now but I don&#39;t need them.</div><div>

I see this is described in the Wiki as well, but it was more concise below, thanks.</div><div>cp -r was fine for copying the remnants of /mnt/galaxyIndices. </div><div>Cheers,</div><div>Greg E</div><div><div><br>
</div><div> </div>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_quote"><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">




<div><div></div><div>2. The vast majority of the storage costs are fro the Gemome databases in the 700GB /mnt/galaxyIndices, which I don&#39;t need. Can this be reduced to the bare essentials ?</div>

</div></blockquote><div><br></div></div><div>You can do this manually: </div><div>1. Start a new Galaxy cluster (ie, one you can easily delete later)</div><div>2. ssh into the master instance and delete whatever genomes you don&#39;t need/want (these are all located under /mnt/galaxyIndices)</div>






<div>3. Create a new EBS volume of size that&#39;ll fit whatever&#39;s left on the original volume, attach it and mount it</div><div>4. Copy over the data from the original volume to the new one while keeping the directory structure the same (rsync is probably the best tool for this)</div>






<div>5. Unmount &amp; detach the new volume; create a snapshot from it</div><div>6. For the cluster you want to keep around (while it is terminated), edit persistent_data.yaml in it&#39;s bucket on S3 and replace the existing snap ID for the galaxyIndices with the snapshot ID you got in the previous step</div>






<div>7. Start that cluster and you should have a file system from the new snapshot mounted.</div><div>8. Terminate &amp; delete the cluster you created in step 1</div><div><br></div><div>If you don&#39;t want to have to do this the first time around on your custom cluster, you can first try it with another temporary cluster and make sure it all works as expected and then move on to the real cluster.</div>






<div><br></div><div>Best,</div><div>Enis</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>

<div><br></div><div><br></div></div></div></blockquote></div></blockquote><div><br></div><div> </div></div></div>
</blockquote></div><br></div></div>