Bug #3174
Incremental backup fails after domain change
Status: | CLOSED | Start date: | ||
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 100% | |
Category: | nethserver-backup-data | |||
Target version: | v6.6 | |||
Security class: | Resolution: | |||
Affected version: | v6.6 | NEEDINFO: | No |
Description
After changing the domain name of the server, the backup-data fails with an error:
Fatal Error: Backup source host has changed. Current hostname: server.olddomain Previous hostname: server.newdomain Aborting because you may have accidentally tried to backup two different data sets to the same remote location, or using the same archive directory. If this is not a mistake, use the --allow-source-mismatch switch to avoid seeing this message
Note that if the hostname changes, the backup will succeed.
Associated revisions
backup-data: add --allow-source-mismatch option to duplicity. Refs #3174
History
#1 Updated by Filippo Carletti about 6 years ago
- Subject changed from Backup fails after domain change to Incremenatl backup fails after domain change
#2 Updated by Filippo Carletti about 6 years ago
- Subject changed from Incremenatl backup fails after domain change to Incremental backup fails after domain change
#3 Updated by Filippo Carletti about 6 years ago
- Status changed from NEW to TRIAGED
- % Done changed from 0 to 20
Tested fix:
-my $opts = ''; +my $opts = '--allow-source-mismatch';
#4 Updated by Filippo Carletti about 6 years ago
Since a full backup doesn't have the problem, a workaround is to delete the existing backup, forcing the system to create a full instead of an incremental.
#5 Updated by Filippo Carletti about 6 years ago
- Target version set to v6.6
#6 Updated by Filippo Carletti about 6 years ago
- Status changed from TRIAGED to ON_DEV
- Assignee set to Filippo Carletti
- % Done changed from 20 to 30
#7 Updated by Filippo Carletti about 6 years ago
- Status changed from ON_DEV to MODIFIED
- Assignee deleted (
Filippo Carletti) - % Done changed from 30 to 60
#8 Updated by Filippo Carletti about 6 years ago
- Status changed from MODIFIED to ON_QA
- % Done changed from 60 to 70
Fixed in nethserver-backup-data-1.1.3-1.2.g2ae25bb.ns6.noarch.rpm
Test case
backup-data
change hostname
run again backup-data and see the error
update package
run again backup-data
#9 Updated by dz0 0te about 6 years ago
- Assignee set to dz0 0te
#10 Updated by dz0 0te about 6 years ago
- Status changed from ON_QA to VERIFIED
- Assignee deleted (
dz0 0te) - % Done changed from 70 to 90
System and Package Version installed
VM KVM - Clean installation of Nethserver 6.6 fully update
Package Installed: nethserver-backup-data-1.1.3-1.ns6.noarch
Other Package installed: Backup, Email,File server,MySQL server,POP3 connector,Web server
Test Original Problem
Backup config over cifs (sorry, no way to test over nfs/usb), incremental
$ backup-data
changed domain (as per description of the bug and not as suggested in test case, probably a typo error)
$ backup-data
error:
Fatal Error: Backup source host has changed. Current hostname: danceofdeath.testdom.com Previous hostname: danceofdeath.domain.com
Install Updated Package
yum --enablerepo=nethserver-testing update nethserver-backup-data-1.1.3-1.2.g2ae25bb.ns6
Test Results after update
backup-data
Backup ok with no errors
Note
...
#11 Updated by Giacomo Sanchietti about 6 years ago
- Status changed from VERIFIED to CLOSED
- % Done changed from 90 to 100
- nethserver-backup-data-1.1.4-1.ns6.noarch.rpm