11-16-2026, 11:18 AM
One PC is moving from one house to another, and vice versa, from time to time.
In each house, the HBS backups are scheduled to each local NAS.
For that, I have created two different Hasleo backup Tasks, one for each house. They are identical (Differential) except that the Destination is different.
Obviously, when in house A, the Task for House B fails with non-existing Destination or I click Pause to disable it to avoid unnecessary errors. And vice versa.
My question is whether this is the correct strategy. I mean, is the history of files backed-up kept different on each task without an interference? I.e. a file modified and already backed up in House A, when moving to House B it will be backed-up again in House B, because it is a different history chain backup. No information of backup is kept on Windows NTFS filesystem but is maintained in the Hasleo database of each different Task. ¿Am I right?
regards,
Alberto
In each house, the HBS backups are scheduled to each local NAS.
For that, I have created two different Hasleo backup Tasks, one for each house. They are identical (Differential) except that the Destination is different.
Obviously, when in house A, the Task for House B fails with non-existing Destination or I click Pause to disable it to avoid unnecessary errors. And vice versa.
My question is whether this is the correct strategy. I mean, is the history of files backed-up kept different on each task without an interference? I.e. a file modified and already backed up in House A, when moving to House B it will be backed-up again in House B, because it is a different history chain backup. No information of backup is kept on Windows NTFS filesystem but is maintained in the Hasleo database of each different Task. ¿Am I right?
regards,
Alberto

