[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: accelerate archive recovery

To: Kevin Gilpin <kevin.gilpin@praxeon.com>
Subject: Re: accelerate archive recovery
From: Chris Webb <chris@arachsys.com>
Date: Fri, 3 Jun 2011 09:34:01 +0100
Cc: tarsnap-users@tarsnap.com
In-reply-to: <BANLkTimbZbH=WQkXYBJYazZrgxVYvHpkpg@mail.gmail.com>
Mailing-list: contact tarsnap-users-help@tarsnap.com; run by ezmlm
References: <20110602084129.GF22747@arachsys.com> <BANLkTimbZbH=WQkXYBJYazZrgxVYvHpkpg@mail.gmail.com>

Kevin Gilpin <kevin.gilpin@praxeon.com> writes:

> Is there anything I can do to make the -x operation go faster? Tarsnap is
> only using about 10% of my CPU, I am restoring an EC2 instance so it should
> have a very fast pipe to tarsnap. It is taking a couple of hours to restore
> 10GB; I need it to be faster than that because the archive size will
> ultimately be up to 100GB and I can't wait 20 hours for a recovery.

Interesting. Sounds like my guess yesterday that my performance problems
were due to latency from the UK might be completely incorrect!

Cheers,

Chris.

Follow-Ups:
- Re: accelerate archive recovery
  - From: Colin Percival <cperciva@tarsnap.com>
- Re: accelerate archive recovery
  - From: Tim Bishop <tim@bishnet.net>

References:
- Reading and deleting archives painfully slow
  - From: Chris Webb <chris@arachsys.com>
- accelerate archive recovery
  - From: Kevin Gilpin <kevin.gilpin@praxeon.com>

Prev by Date: Re: sequence number mismatch
Next by Date: Re: sequence number mismatch
Previous by thread: accelerate archive recovery
Next by thread: Re: accelerate archive recovery
Index(es):
- Date
- Thread