Certainly, the heaviest load was during the initial backup; the incremental backups move much less data, and in particular the really big files (ISOs and movies) don't get changed and so don't get copied. However, there was slow down (although much less) during subsequent incremental backups; I believe this comes from other big files, like virtual machine state files and so forth. It's a little hard to tell which file was causing it, since I don't know of a way to tell which file is currently being copied; the notification area icon provides a dialog box but its content isn't updated dynamically. (As an aside, it would be nice if clicking on the notification icon opened a running log of the backup procedure.)
In regard to your second question, I'm not really sure what you mean by schedle per included folder. Is this a configuration option? What effect is it supposed to have? I'm happy to try it and report back to you. -- Backup slows down system, doesn't throttle I/O https://bugs.launchpad.net/bugs/482931 You received this bug notification because you are a member of Back In Time Team, which is subscribed to Back In Time. Status in Back In Time: New Bug description: When BIT is actively copying data, the system is significantly less responsive because of the disk load. BIT should be more polite. It should use ionice to set its I/O to a lower priority and it should use a slow, background copy mechanism to copy files in a way that's less intrusive to foreground processes. _______________________________________________ Mailing list: https://launchpad.net/~bit-team Post to : [email protected] Unsubscribe : https://launchpad.net/~bit-team More help : https://help.launchpad.net/ListHelp
