Re: [Duplicity-team] [Question #150801]: BucketAlreadyOwnedByYou
Question #150801 on Duplicity changed: https://answers.launchpad.net/duplicity/+question/150801 Brandon Keszler proposed the following answer: Max, I just came across this same issue this evening. I see the thread hasn't been updated in a while but wanted to post for anyone else that may be frustrated with this. You can force duplicity to use the Northern California buckets (even existing ones) by editing 'connection.py' in the python modules folder (for me: /usr/lib/pymodules/python2.6/boto/s3). There are only two lines that need to be changed (-) as follows: --- connection.py:91 DefaultHost = 's3.amazonaws.com' - DefaultHost = 's3-us-west-1.amazonaws.com' connection.py:214 url = '%s://%s.s3.amazonaws.com/' % (http_method, bucket_name) - url = '%s://%s.s3-us-west-1.amazonaws.com/' % (http_method, bucket_name) --- If you need to use other regions (i.e. Tokyo), simply substitute with the region specific endpoints per the AWS documentation http://aws.amazon.com/articles/3912#s3 -- You received this question notification because you are a member of duplicity-team, which is an answer contact for Duplicity. ___ Mailing list: https://launchpad.net/~duplicity-team Post to : duplicity-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~duplicity-team More help : https://help.launchpad.net/ListHelp
Re: [Duplicity-team] [Question #150801]: BucketAlreadyOwnedByYou
Question #150801 on Duplicity changed: https://answers.launchpad.net/duplicity/+question/150801 Status: Answered = Open Max is still having a problem: Hi, Thanks for your message. I'm little bit confused. Why all this happens only when I try to make a backup in Northern California bucket (empty...created by me only for this test) ? Why all is OK when I try to make a backup in US Standard bucket (also this empty... created by me only for this test) ? What shall I do now ? Shall I forget forever to have a backup in Northern California bucket (with Duplicity) ? If so. I'm forced to use only US Standard backup. Thanks Max -- You received this question notification because you are a member of duplicity-team, which is an answer contact for Duplicity. ___ Mailing list: https://launchpad.net/~duplicity-team Post to : duplicity-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~duplicity-team More help : https://help.launchpad.net/ListHelp
Re: [Duplicity-team] [Question #150801]: BucketAlreadyOwnedByYou
Question #150801 on Duplicity changed: https://answers.launchpad.net/duplicity/+question/150801 Status: Open = Answered Kenneth Loafman proposed the following answer: Max, If you will remove the OO_backup.py from backends, this will allow duplicity to use the patched version which uses the existing bucket and should not try to create a new one. As to Northern California bucket, I don't know that such a thing exists, or how to specify it. Currently boto does not have this capability, and duplicity is dependent on boto for S3. ...Ken On Fri, Apr 1, 2011 at 4:49 AM, Max question150...@answers.launchpad.netwrote: Question #150801 on Duplicity changed: https://answers.launchpad.net/duplicity/+question/150801 Status: Answered = Open Max is still having a problem: Hi, Thanks for your message. I'm little bit confused. Why all this happens only when I try to make a backup in Northern California bucket (empty...created by me only for this test) ? Why all is OK when I try to make a backup in US Standard bucket (also this empty... created by me only for this test) ? What shall I do now ? Shall I forget forever to have a backup in Northern California bucket (with Duplicity) ? If so. I'm forced to use only US Standard backup. Thanks Max -- You received this question notification because you are a member of duplicity-team, which is an answer contact for Duplicity. ___ Mailing list: https://launchpad.net/~duplicity-team Post to : duplicity-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~duplicity-team More help : https://help.launchpad.net/ListHelp -- You received this question notification because you are a member of duplicity-team, which is an answer contact for Duplicity. ___ Mailing list: https://launchpad.net/~duplicity-team Post to : duplicity-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~duplicity-team More help : https://help.launchpad.net/ListHelp
Re: [Duplicity-team] [Question #150801]: BucketAlreadyOwnedByYou
Question #150801 on Duplicity changed: https://answers.launchpad.net/duplicity/+question/150801 Status: Needs information = Open Max gave more information on the question: Hi, Here are the first 126 lines. and the error message. The error message is repeated continuously since I stop it. There is also the output displayed after I stop it. Local and Remote metadata are synchronized, no sync needed. Last full backup date: Wed Mar 30 23:26:26 2011 No old backup sets found, nothing deleted. Using archive dir: /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74 Using backup name: 7afa849886f0198cad6b2b4e2dd37c74 Import of duplicity.backends.cloudfilesbackend Succeeded Import of duplicity.backends.rsyncbackend Succeeded Import of duplicity.backends.hsibackend Succeeded Import of duplicity.backends.OO__botobackend Succeeded Import of duplicity.backends.botobackend Failed: the scheme s3 already has a backend associated with it Import of duplicity.backends.sshbackend Succeeded Import of duplicity.backends.ftpbackend Succeeded Import of duplicity.backends.webdavbackend Succeeded Import of duplicity.backends.imapbackend Succeeded Import of duplicity.backends.localbackend Succeeded Import of duplicity.backends.giobackend Failed: No module named gio Import of duplicity.backends.tahoebackend Succeeded Main action: inc duplicity 0.6.12 (March 08, 2011) Args: /usr/bin/duplicity -v9 --full-if-older-than 1M --encrypt-key=3F277453 --sign-key=517F93A7 --volsize=250 --include=/bin --include=/boot --include=/etc --include=/home --exclude=/home/b44b/vps_backups --exclude=/** / s3+http://cmsbk Linux cmserver.cmserver.com 2.6.18-194.el5xen #1 SMP Fri Apr 2 15:34:40 EDT 2010 x86_64 x86_64 /usr/bin/python 2.4.3 (#1, Nov 11 2010, 13:30:19) [GCC 4.1.2 20080704 (Red Hat 4.1.2-48)] Using temporary directory /tmp/duplicity-dNSAP7-tempdir Registering (mkstemp) temporary file /tmp/duplicity-dNSAP7-tempdir/mkstemp-hnvwwa-1 Temp has 22347845632 available, backup will use approx 340787200. Local and Remote metadata are synchronized, no sync needed. 0 files exist on backend 2 files exist in cache Extracting backup chains from list of files: ['duplicity-full.20110331T062626Z.manifest.part', 'duplicity-full-signatures.20110331T062626Z.sigtar.part'] File duplicity-full.20110331T062626Z.manifest.part is not part of a known set; creating new set File duplicity-full-signatures.20110331T062626Z.sigtar.part is not part of a known set; creating new set Ignoring file (rejected by backup set) 'duplicity-full-signatures.20110331T062626Z.sigtar.part' Found backup chain [Wed Mar 30 23:26:26 2011]-[Wed Mar 30 23:26:26 2011] Last full backup left a partial set, restarting. Last full backup date: Wed Mar 30 23:26:26 2011 Collection Status - Connecting with backend: BotoBackend Archive dir: /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74 Found 0 secondary backup chains. Found primary backup chain with matching signature chain: - Chain start time: Wed Mar 30 23:26:26 2011 Chain end time: Wed Mar 30 23:26:26 2011 Number of contained backup sets: 1 Total number of contained volumes: 0 Type of backup set:Time: Num volumes: - No orphaned or incomplete backup sets found. RESTART: The first volume failed to upload before termination. Restart is impossible...starting backup from beginning. BackupSet.delete: missing ['duplicity-full.20110331T062626Z.manifest.part'] Deleting /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74/duplicity-full.20110331T062626Z.manifest.part Deleting /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74/duplicity-full-signatures.20110331T062626Z.sigtar.part Using archive dir: /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74 Using backup name: 7afa849886f0198cad6b2b4e2dd37c74 Import of duplicity.backends.cloudfilesbackend Succeeded Import of duplicity.backends.rsyncbackend Succeeded Import of duplicity.backends.hsibackend Succeeded Import of duplicity.backends.OO__botobackend Succeeded Import of duplicity.backends.botobackend Failed: the scheme s3 already has a backend associated with it Import of duplicity.backends.sshbackend Succeeded Import of duplicity.backends.ftpbackend Succeeded Import of duplicity.backends.webdavbackend Succeeded Import of duplicity.backends.imapbackend Succeeded Import of duplicity.backends.localbackend Succeeded Import of duplicity.backends.giobackend Failed: No module named gio Import of duplicity.backends.tahoebackend Succeeded Main action: inc duplicity 0.6.12 (March 08, 2011) Args: /usr/bin/duplicity -v9 --full-if-older-than 1M --encrypt-key=3F277453 --sign-key=517F93A7 --volsize=250
Re: [Duplicity-team] [Question #150801]: BucketAlreadyOwnedByYou
Question #150801 on Duplicity changed: https://answers.launchpad.net/duplicity/+question/150801 Status: Open = Answered Kenneth Loafman proposed the following answer: This may be your problem... ... Import of duplicity.backends.OO__botobackend Succeeded Import of duplicity.backends.botobackend Failed: the scheme s3 already has a backend associated with it ... If OO__botobackend is the old backend, it got imported before botobackend, as used for S3. ...Ken On Thu, Mar 31, 2011 at 1:54 AM, Max question150...@answers.launchpad.netwrote: Question #150801 on Duplicity changed: https://answers.launchpad.net/duplicity/+question/150801 Status: Needs information = Open Max gave more information on the question: Hi, Here are the first 126 lines. and the error message. The error message is repeated continuously since I stop it. There is also the output displayed after I stop it. Local and Remote metadata are synchronized, no sync needed. Last full backup date: Wed Mar 30 23:26:26 2011 No old backup sets found, nothing deleted. Using archive dir: /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74 Using backup name: 7afa849886f0198cad6b2b4e2dd37c74 Import of duplicity.backends.cloudfilesbackend Succeeded Import of duplicity.backends.rsyncbackend Succeeded Import of duplicity.backends.hsibackend Succeeded Import of duplicity.backends.OO__botobackend Succeeded Import of duplicity.backends.botobackend Failed: the scheme s3 already has a backend associated with it Import of duplicity.backends.sshbackend Succeeded Import of duplicity.backends.ftpbackend Succeeded Import of duplicity.backends.webdavbackend Succeeded Import of duplicity.backends.imapbackend Succeeded Import of duplicity.backends.localbackend Succeeded Import of duplicity.backends.giobackend Failed: No module named gio Import of duplicity.backends.tahoebackend Succeeded Main action: inc duplicity 0.6.12 (March 08, 2011) Args: /usr/bin/duplicity -v9 --full-if-older-than 1M --encrypt-key=3F277453 --sign-key=517F93A7 --volsize=250 --include=/bin --include=/boot --include=/etc --include=/home --exclude=/home/b44b/vps_backups --exclude=/** / s3+http://cmsbk Linux cmserver.cmserver.com 2.6.18-194.el5xen #1 SMP Fri Apr 2 15:34:40 EDT 2010 x86_64 x86_64 /usr/bin/python 2.4.3 (#1, Nov 11 2010, 13:30:19) [GCC 4.1.2 20080704 (Red Hat 4.1.2-48)] Using temporary directory /tmp/duplicity-dNSAP7-tempdir Registering (mkstemp) temporary file /tmp/duplicity-dNSAP7-tempdir/mkstemp-hnvwwa-1 Temp has 22347845632 available, backup will use approx 340787200. Local and Remote metadata are synchronized, no sync needed. 0 files exist on backend 2 files exist in cache Extracting backup chains from list of files: ['duplicity-full.20110331T062626Z.manifest.part', 'duplicity-full-signatures.20110331T062626Z.sigtar.part'] File duplicity-full.20110331T062626Z.manifest.part is not part of a known set; creating new set File duplicity-full-signatures.20110331T062626Z.sigtar.part is not part of a known set; creating new set Ignoring file (rejected by backup set) 'duplicity-full-signatures.20110331T062626Z.sigtar.part' Found backup chain [Wed Mar 30 23:26:26 2011]-[Wed Mar 30 23:26:26 2011] Last full backup left a partial set, restarting. Last full backup date: Wed Mar 30 23:26:26 2011 Collection Status - Connecting with backend: BotoBackend Archive dir: /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74 Found 0 secondary backup chains. Found primary backup chain with matching signature chain: - Chain start time: Wed Mar 30 23:26:26 2011 Chain end time: Wed Mar 30 23:26:26 2011 Number of contained backup sets: 1 Total number of contained volumes: 0 Type of backup set:Time: Num volumes: - No orphaned or incomplete backup sets found. RESTART: The first volume failed to upload before termination. Restart is impossible...starting backup from beginning. BackupSet.delete: missing ['duplicity-full.20110331T062626Z.manifest.part'] Deleting /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74/duplicity-full.20110331T062626Z.manifest.part Deleting /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74/duplicity-full-signatures.20110331T062626Z.sigtar.part Using archive dir: /home/b44b/.cache/duplicity/7afa849886f0198cad6b2b4e2dd37c74 Using backup name: 7afa849886f0198cad6b2b4e2dd37c74 Import of duplicity.backends.cloudfilesbackend Succeeded Import of duplicity.backends.rsyncbackend Succeeded Import of duplicity.backends.hsibackend Succeeded Import of duplicity.backends.OO__botobackend Succeeded Import of duplicity.backends.botobackend Failed: the scheme s3 already has a backend associated with
Re: [Duplicity-team] [Question #150801]: BucketAlreadyOwnedByYou
Question #150801 on Duplicity changed: https://answers.launchpad.net/duplicity/+question/150801 Status: Open = Needs information Kenneth Loafman requested for more information: In version 1.9b there are only two settings, DEFAULT and EU. from boto.s3.connection import Location dir(Location) ['DEFAULT', 'EU', '__doc__', '__module__'] Duplicity will choose EU if --s3-european-buckets is set, otherwise DEFAULT, which is US. There is no option for Northern California that I can see. The patch I supplied should not have tried to create a new bucket at all. Please add -v9 to the duplicity command line and capture the log to a file, then paste the first 100 lines or so into your answer. Maybe that will help me see what's going on. -- You received this question notification because you are a member of duplicity-team, which is an answer contact for Duplicity. ___ Mailing list: https://launchpad.net/~duplicity-team Post to : duplicity-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~duplicity-team More help : https://help.launchpad.net/ListHelp
Re: [Duplicity-team] [Question #150801]: BucketAlreadyOwnedByYou
Question #150801 on Duplicity changed: https://answers.launchpad.net/duplicity/+question/150801 Status: Open = Answered edso proposed the following answer: wait for the bugfix from ken and try it. my bet is even though you think it is a US Basket it ended up in Europe. any reason not to use the freshly created bucket to till then? ede Max question150...@answers.launchpad.net schrieb: Question #150801 on Duplicity changed: https://answers.launchpad.net/duplicity/+question/150801 Status: Answered = Open Max is still having a problem: Hi, @edso Thanks I already knew this thread I checked it again but it still doesn't help unfortunately. In addition to that I want to say that my bucket is in Northern California. @Ken I had already done what you suggest. Before installing duplicity 0.6.12 tarball I uninstalled the yum version. But the problem was still there. I connect directly to Amazon in this way: DEST=s3+http://mybucket; or s3+http://mybucket/mydir;. I also checked the link you gave. but as I say above my bucket is in Northern California. If duplicity creates a new bucket (in US Standard) it seems to work well. But if I want to make backup in existing Northern California bucket it gives the error message I described. Hope I have clearly explained. What shall I do now ? Thanks Max -- You received this question notification because you are a member of duplicity-team, which is an answer contact for Duplicity._ Mailing list: https://launchpad.net/~duplicity-team Post to : duplicity-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~duplicity-team More help : https://help.launchpad.net/ListHelp You received this question notification because you are a member of duplicity-team, which is an answer contact for Duplicity. ___ Mailing list: https://launchpad.net/~duplicity-team Post to : duplicity-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~duplicity-team More help : https://help.launchpad.net/ListHelp
