Summary When performing a large incremental
backup to an FTP destination, it may take a lot of time for the first backup to complete (because the first backup is a full backup
so all files will be included in it). If you have physical access to the FTP destination server, it takes less time to run the first backup locally, move the backup file to the FTP, and after that continue doing the incremental backups directly to the FTP destination. This article will explain how to perform this backup. On this page: Make a full backup locally and subsequent incremental backups to FTP Details The .bkc catalog file is stored in two locations: in the destination folder and locally in the catalog folder . If the local catalog is used, when the user changes the destination of the backup the local catalog is deleted, and a full backup to the new destination will be made. The backup strategy is:
Make a full backup locally and subsequent incremental backups to FTP
Steps to follow for Backup4all 4: Steps to follow for Backup4all 3:
Applies to: All Backup4all versions. |
|
24 Jun, 2010
| Adi
|
|
After changing the destination, you can enable the option to use local catalog. This feature makes much shorter the catalog loading time. |
|
22 Jun, 2010
| Bill
|
|
Is it ever safe to turn the local catalog back on after changing the destination? Or, will doing so at any time erase the backup? I assume the purpose of the local catalog is to improve performance - is that correct? |

