On 5/6/2010 8:19 AM, Boniforti Flavio wrote:
>
>> On slow connections it will help to add the -C (compress)
>> option to the ssh command.  Be sure you exclude any areas or
>> big files you don't need to back up (like the slocate db on
>> linux boxes, etc.).  If you do several remote backups, don't
>> do too many concurrently and try to get the start times and
>> full runs skewed.
>
> OK, for SSH, I'm already using -C switch...
>
> Things I don't need to back up are excluded...
>
> I'm actually doing 8 remote backups, which are starting alltogether at
> 21 PM... Until now, I didn't have too many troubles with bandwidth/time,
> but I'll re-evaluate if it will come to a bottleneck.

If your end has plenty of bandwidth and you are going to different 
remote locations, running several at once is probably OK.

> So, in the end: is there any way to optimise my backups? Would the
> application of more levels of incrementals, be helpful?

Incremental levels will help, but if you are completing in the available 
time window I wouldn't worry that much about it.

-- 
   Les Mikesell
    lesmikesell AT gmail DOT com

------------------------------------------------------------------------------
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/