Hello I have two turnkey machines that seem to be trying to access the same Amazon Backup service.

Machine One

turnkey-mediawiki-11.1-lucid-x86

Machine Two

turnkey-mediawiki-12.1-squeeze-amd64

Both these machines are virtual machines on the same server running VMWare ESXi or similar.

A long time ago I created an account through hub.turnkeylinux.org that accessed the Amazon S3 servers.  I had to cancel things when Amazon/Turnkey decided to start charging $10/month minimum last year.

However, I've now decided the tklbam storage could be quite useful and so I recently configured Machine Two to back up to the Turnkey/Amazon solution.  All worked well.

I would now like to backup Machine One.  However, I suspect that a few year ago I entered my user initialization string (API-Key) into the machine.  Complicating matters is that I may have entered a different  API-Key on the basis of prompt from an Amazon popup.

If I run tklbam-status I get

Machine One

TKLBAM: Backup ID #3, Updated Thu 2014-06-05 11:03

Machine Two

TKLBAM: Backup ID #1, Updated Thu 2014-06-05 10:52 (I'm happy with this one)

The difficultly for me is that have no idea where machine one is backed up too.  Coupled with the fact that the /etc/.git/ directory has simple exploded sending disk useage to 100%. The screenshots show machine two happily backed up.

Is there any tidy way I can start again with the backups on machine One and remove the bloated /etc/.git directory?

Edit:

The backup just took a very long time. About 22hrs to do 13G.  It eventually appeared on the account that I expected it to.  I've got no idea why it was 13G though. It just a proxy server and limited the cache from the backup.