Jump to content
XPEnology Community

Time Backup incremental backups problem after real DS upg


Kybla
 Share

Recommended Posts

Hi,

 

I have been using XPEnology on real HW (ASUS C60M1-I) as a Time Backup target from my real DS (1512+) for a year and everything was working fine. I had block backup enabled, only changes were copied and every new backup (once a day) was an incremental one, so the occupied space on the backup DS was not expanding much. I had DSM 4.2 both on the real DS and backup DS (Trantor)

 

But after the upgrade of the real DS (to DSM 5.0-4458 Update 1), the incremental backups to XPEnology as a target are not working properly anymore. Every time, the backup takes all the space of the data on the backup DS. I did a test and set a Time Backup to another real DS (712+), and then it works - only the first backup takes all the space, and every subsequent backup takes only the space of changed files. I also tried DSM 4.3 (Trantor) and DSM 5.0-4458 Update 1 (gnoBoot 10.4 alpha) on the backup DS, but still the same.

 

As my explanation may be little confusing, I will explain it in steps. Legend:

DS1 = main real DS1512+, DSM 5.0-4458 Update 1.

DS2 = another real DS712+, DSM 5.0-4458 Update 1.

DS3 = backup DS with XPEnology DSM 5.0-4458 Update 1 (gnoBoot 10.4 alpha).

 

1. I set Time Backup on DS1 with DS2 as a target to backup cca 10 GB of data, block level enabled. First run - 6 minutes, 10GB taken on DS2. Second run (immediately after), 2 minutes, additional 0.01 GB taken on DS2, totalling on 10.01 GB taken. Everything works fine.

 

2. I set Time Backup on DS1 with DS3 as a target with the same parameters and data as before. First run - 7 minutes, 10GB taken on DS3. Second run (immediately after), 4 minutes, additional 10 GB taken on DS3, totalling on 20 GB taken. Whoops :sad:.

 

It seems that the subsequent backup is an "incremental" one, but on XPEnology, whole files are copied to the new backup location, instead of making only links as on the real DS. I've tried to compare logs from both DS2 and DS3, but I see nothing clear there:

 

iscsi.log on DS2:

Apr  1 12:57:50 Sedmdesatka kernel: [435172.212424] iSCSI: iSCSI: Discovery session from [127.0.0.1]
Apr  1 12:57:51 Sedmdesatka kernel: [435172.569701] iSCSI: iSCSI: Login - I[iqn.2005-03.org.open-iscsi:637059b34c3c][127.0.0.1], T[iqn.2000-01.com.synology:timebkp-target-jakub_00113215FA9A-vol1-snap0][127.0.0.1:12345]
Apr  1 12:57:52 Sedmdesatka kernel: [435174.256099] iSCSI: iSCSI: Close - I[iqn.2005-03.org.open-iscsi:637059b34c3c][127.0.0.1], T[(null)]
Apr  1 13:02:45 Sedmdesatka kernel: [435467.397406] iSCSI: iSCSI: Logout- I[iqn.2005-03.org.open-iscsi:637059b34c3c][127.0.0.1], T[iqn.2000-01.com.synology:timebkp-target-jakub_00113215FA9A-vol1-snap0]
Apr  1 13:02:45 Sedmdesatka kernel: [435467.412483] iSCSI: iSCSI: Close - I[iqn.2005-03.org.open-iscsi:637059b34c3c][127.0.0.1], T[iqn.2000-01.com.synology:timebkp-target-jakub_00113215FA9A-vol1-snap0]
Apr  1 13:03:59 Sedmdesatka kernel: [435541.483492] iSCSI: iSCSI: Discovery session from [127.0.0.1]
Apr  1 13:04:00 Sedmdesatka kernel: [435541.799758] iSCSI: iSCSI: Login - I[iqn.2005-03.org.open-iscsi:637059b34c3c][127.0.0.1], T[iqn.2000-01.com.synology:timebkp-target-jakub_00113215FA9A-vol1-snap0][127.0.0.1:12345]
Apr  1 13:04:01 Sedmdesatka kernel: [435543.526056] iSCSI: iSCSI: Close - I[iqn.2005-03.org.open-iscsi:637059b34c3c][127.0.0.1], T[(null)]
Apr  1 13:04:36 Sedmdesatka kernel: [435578.058400] iSCSI: iSCSI: Logout- I[iqn.2005-03.org.open-iscsi:637059b34c3c][127.0.0.1], T[iqn.2000-01.com.synology:timebkp-target-jakub_00113215FA9A-vol1-snap0]
Apr  1 13:04:36 Sedmdesatka kernel: [435578.073135] iSCSI: iSCSI: Close - I[iqn.2005-03.org.open-iscsi:637059b34c3c][127.0.0.1], T[iqn.2000-01.com.synology:timebkp-target-jakub_00113215FA9A-vol1-snap0]

 

iscsi.log on DS3:

Apr  1 17:12:29 Thecology kernel: [ 3302.349385] iSCSI: Discovery session from [127.0.0.1]
Apr  1 17:12:30 Thecology kernel: [ 3302.704290] iSCSI: Login - I[iqn.2005-03.org.open-iscsi:637059b34c3c][127.0.0.1], T[iqn.2000-01.com.synology:timebkp-target-jakub_00113215FA9A-vol1-snap0][127.0.0.1:12345]
Apr  1 17:17:41 Thecology kernel: [ 3614.322366] iSCSI: Logout- I[iqn.2005-03.org.open-iscsi:637059b34c3c][127.0.0.1], T[iqn.2000-01.com.synology:timebkp-target-jakub_00113215FA9A-vol1-snap0]
Apr  1 17:20:07 Thecology kernel: [ 3760.096466] iSCSI: Discovery session from [127.0.0.1]
Apr  1 17:20:08 Thecology kernel: [ 3760.452273] iSCSI: Login - I[iqn.2005-03.org.open-iscsi:637059b34c3c][127.0.0.1], T[iqn.2000-01.com.synology:timebkp-target-jakub_00113215FA9A-vol1-snap0][127.0.0.1:12345]
Apr  1 17:22:44 Thecology kernel: [ 3916.791102] iSCSI: Logout- I[iqn.2005-03.org.open-iscsi:637059b34c3c][127.0.0.1], T[iqn.2000-01.com.synology:timebkp-target-jakub_00113215FA9A-vol1-snap0]

 

messages on DS2:

Apr  1 12:57:51 Sedmdesatka kernel: [435172.837699] iSCSI: TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x85, sending CHECK_CONDITION.
Apr  1 12:57:58 Sedmdesatka entry.cgi_SYNO.Core.Upgrade.Server[1].check[1536]: smallupdate.cpp:413 small fix can't downgrade, org_version[1], new_version[1]
Apr  1 13:04:00 Sedmdesatka kernel: [435542.052721] iSCSI: TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x85, sending CHECK_CONDITION.

 

messages on DS3:

Apr  1 17:12:28 Thecology kernel: [ 3301.163040] EXT_INFO: INIT Extent-Pool
Apr  1 17:12:28 Thecology kernel: [ 3301.259652] RODSP_INFO: RODSPS Start-[50:46:5d:a3:93:07]
Apr  1 17:12:30 Thecology kernel: [ 3302.958424] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x85, sending CHECK_CONDITION.
Apr  1 17:20:08 Thecology kernel: [ 3760.706364] TARGET_CORE[iSCSI]: Unsupported SCSI Opcode 0x85, sending CHECK_CONDITION.

 

I would be glad for any help. Thanks a lot.

And of course I would like to thank Trantor and gnoBoot for their work.

(And, lastly, I would like to apologize for a long post, somehow I am not able to explain things without using many words :smile:)

Link to comment
Share on other sites

 Share

×
×
  • Create New...