Backups from different machines/profiles stored in same folder are used as base for incremental snapshots
Bug #606759 reported by
Andreas Tarp
This bug affects 4 people
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| nssbackup |
Won't Fix
|
Undecided
|
Unassigned | |||
| sbackup | Status tracked in Trunk | |||||
| 0.10 |
Won't Fix
|
Undecided
|
Unassigned | |||
| 0.11 |
Won't Fix
|
Undecided
|
Unassigned | |||
| Trunk |
Confirmed
|
Wishlist
|
Unassigned | |||
Bug Description
Hi,
nssbackup uses backup from different machine as base for incremental backup if both machines are storing backups into the same folder. The problem occurred for me using nssbackup version 0.2.1 (installed on Kubuntu 10.4 from ppa onto an external usb drive.
After finishing backup of a second machine in the same backup folder on an external drive I had the following result in my backup folder afterwards:
<timestamp1>
<timestamp2>
instead of something like this:
<timestamp1>
<timestamp2>
So in my point of view nssbackup should only use a previous backup as base for an incremental backup if the old backup has the same hostname as the machine running the backup.
Cheers, Andreas
| Changed in nssbackup: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| summary: |
- nssbackup uses backup from different machine as base for incremental - backup + ackup from different machine as base for incremental backup |
| summary: |
- ackup from different machine as base for incremental backup + Backups from different machines/profiles stored in same folder are used + as base for incremental snapshots |
| Changed in sbackup: | |
| importance: | Undecided → Low |
| Changed in nssbackup: | |
| importance: | Medium → Low |
| Changed in sbackup: | |
| status: | New → Incomplete |
| status: | Incomplete → Confirmed |
| Changed in nssbackup: | |
| status: | Confirmed → Won't Fix |
| importance: | Low → Undecided |
Revision history for this message
| Jean-Peer Lorenz (peer.loz) wrote | #1 |
To post a comment you must log in.
Somehow related bug: https:/