Last backup was in the future - how to ignore the last backup?

Foiler · December 27, 2018, 9:38am

I accidentally set my computer clock forward one year and the backup ran with the new date. Now after resetting the date I get this error:

The previous backup has time 17/12/2019 5:22:23 p.m., but this backup has time 27/12/2018 10:35:41 p.m… Something is wrong with the clock.

Is there any advanced setting to ignore the time of the last backup?

ts678 · December 27, 2018, 12:46pm

The time test looks unavoidable (even if one looks in code before this):

github.com

duplicati/duplicati/blob/0306b3dd531c3644a4cb2524a22d76b715504b80/Duplicati/Library/Main/Operation/BackupHandler.cs#L451-L454


      
          // Grab the previous backup ID, if any

          var prevfileset = m_database.FilesetTimes.FirstOrDefault();

          if (prevfileset.Value.ToUniversalTime() > m_database.OperationTimestamp.ToUniversalTime())

              throw new Exception(string.Format("The previous backup has time {0}, but this backup has time {1}. Something is wrong with the clock.", prevfileset.Value.ToLocalTime(), m_database.OperationTimestamp.ToLocalTime()));

You might have to use the delete command to remove that version. Easiest way is by Commandline in GUI, adjusting things as necessary. Compared to backup, the main format difference is the lack of source paths. You’d also want to specify a –version (probably 0, but you can look at Restore from dropdown) or similar. Adding and checking –dry-run on a test run of delete will add confidence the 2019 version will be deleted.

Did it actually make one that you can restore from? I’d have thought the time issue would have blocked that, however if there’s really a 2018-2019-2018 sequence in Restore from, directions above need changing…

Foiler · December 27, 2018, 7:10pm

Thank you the Delete command worked perfectly.

There was only one future dated backup to delete (–version=0), so to answer your question, no the current real date backup had failed without creating a backup.