On Sat, Dec 19, 2009 at 6:16 PM, Les Mikesell wrote:
> One way would be to initially set up the new server backup with a
> clientalias
> setting pointing to the local copy. Then after you have a full, remove the
> clientalias or change it to the real target.
>
> But, mv'ing the directories shoul
Kameleon wrote:
> I was able to get a full backup on 3 of the 4 servers. Two of them I was
> able to take the backuppc machine to the location and the third it was
> small enough to be able to complete over the T1. However we have one
> remaining remote location that has approximately 309GB of d
I was able to get a full backup on 3 of the 4 servers. Two of them I was
able to take the backuppc machine to the location and the third it was small
enough to be able to complete over the T1. However we have one remaining
remote location that has approximately 309GB of data that needs backing up.
Kameleon wrote:
> I have a few remote sites I am wanting to backup using backuppc.
> However, two are on slow DSL connections and the other 2 are on T1's.
> I did some math and roughly figured that the DSL connections, having a
> 256k upload, could do approximately 108MB/hour of transfer. With t
I have a few remote sites I am wanting to backup using backuppc. However,
two are on slow DSL connections and the other 2 are on T1's. I did some math
and roughly figured that the DSL connections, having a 256k upload, could do
approximately 108MB/hour of transfer. With these clients having around
