On May 23, 2012, at 10:32 PM, "ad^2" wrote:
> Correct. As I mentioned in the original post.
>
> The volume had about 1TB of other data. A block level copy would have
> taken to long.
I can't argue with the "too long" part: if your requirement was that the
data copy over in milliseconds, nothin
On 05/24 12:35 , Adam Goryachev wrote:
> I suspect that the time taken to do a block level copy (including the
> additional 1TB) and then deleting the 1TB of data would still be quicker
> than any other solution (unless the backuppc data was exceptionally small).
I agree with Adam, I have had simi
On 24/05/12 12:29, ad^2 wrote:
> Correct. As I mentioned in the original post.
>
> The volume had about 1TB of other data. A block level copy would have
> taken to long.
>
I suspect that the time taken to do a block level copy (including the
additional 1TB) and then deleting the 1TB of data would s
Correct. As I mentioned in the original post.
The volume had about 1TB of other data. A block level copy would have
taken to long.
On Wed, May 23, 2012 at 9:18 PM, Trey Dockendorf wrote:
>
>
> On Wed, May 23, 2012 at 1:25 PM, Timothy J Massey
> wrote:
>>
>>
>>
>> On May 23, 2012, at 11:58 AM,
On Wed, May 23, 2012 at 1:25 PM, Timothy J Massey wrote:
>
>
> On May 23, 2012, at 11:58 AM, "Carl Wilhelm Soderstrom"
> wrote:
>
> > On 05/22 08:18 , ad^2 wrote:
> > > >From what I have read even though tar supports a hardlink option it
> > > will not do the trick with BackupPC. Have you use tar
On May 23, 2012, at 11:58 AM, "Carl Wilhelm Soderstrom"
wrote:
> On 05/22 08:18 , ad^2 wrote:
> > >From what I have read even though tar supports a hardlink option it
> > will not do the trick with BackupPC. Have you use tar to copy the
> > __TOPDIR__/pc directory?
>
> Yes. Works fine using 'cd
I can confirm this works now. I tested it last night between two volumes.
The issue was the path in the config file. My mistake was updating the
path to the new location then running the script. I reverted to the
original path, ran the script to move the files then put the new path
back. It worked
We have them on the old machine. We shutdown the service and will
retain the old information as long as we need to.
I would have preferred to migrate it but the BackupPC_tarPCCopy script
was not supported on the OS the old system was running on.
The BackupPC_tarPCCopy scripts works fine on the ne
On 05/22 08:18 , ad^2 wrote:
> >From what I have read even though tar supports a hardlink option it
> will not do the trick with BackupPC. Have you use tar to copy the
> __TOPDIR__/pc directory?
Yes. Works fine using 'cd /var/lib/backuppc/; tar cpf - | nc
targethost.domain.tld ' (and obviously
On Wed, May 23, 2012 at 10:32 AM, Trey Dockendorf wrote:
>
>
> On Tue, May 22, 2012 at 8:21 PM, ad^2 wrote:
>
>> Now that I have the system updated with the latest version I decided
>> to test the script on the same system. It still does not work and
>> produces the same error.
>>
>> Argument "to
On Tue, May 22, 2012 at 8:21 PM, ad^2 wrote:
> Now that I have the system updated with the latest version I decided
> to test the script on the same system. It still does not work and
> produces the same error.
>
> Argument "topdir/pc" must be an absolute path starting with "topdir"
> tar: This d
So you didn't keep your old backups. You just let it start making new ones.
Correct?
Regards,
Tyler
On 2012-05-23 15:28, ad^2 wrote:
> This was the path I chose.
>
> * Migrate the system configurations (/etc/BackupPC)
> * Let the pool build on its own. Rebuilding (in this case creating a
> new p
This was the path I chose.
* Migrate the system configurations (/etc/BackupPC)
* Let the pool build on its own. Rebuilding (in this case creating a
new pool) the pool is done by the BackupPC process. Just let the
system run backups and do what it was intended for.
Thx
On Wed, May 23, 2012 at 4:
On 2012-05-23 01:18, ad^2 wrote:
> Anyway, I went with the rebuild and let BackupPC recreate the pool
> option. I copied the configuration files to retain all the previous
> system's settings. It worked and it was fast to set up.
What is this option? I assume it means "Copy the pc directory withou
Now that I have the system updated with the latest version I decided
to test the script on the same system. It still does not work and
produces the same error.
Argument "topdir/pc" must be an absolute path starting with "topdir"
tar: This does not look like a tar archive
tar: Exiting with failure
Hello,
>From what I have read even though tar supports a hardlink option it
will not do the trick with BackupPC. Have you use tar to copy the
__TOPDIR__/pc directory?
Anyway, I went with the rebuild and let BackupPC recreate the pool
option. I copied the configuration files to retain all the prev
On 05/22 11:46 , ad^2 wrote:
> I have a BackupPC server running an older unsupported version of
> Fedora. I have new server with more disk space and an up to date
> operating system. The goal is to migrate all the information over to
> the new server
>
> DD is not an option because the device on t
Hello,
I read a bug about this issue and was hoping someone here had a work around.
I have a BackupPC server running an older unsupported version of
Fedora. I have new server with more disk space and an up to date
operating system. The goal is to migrate all the information over to
the new server
18 matches
Mail list logo
