


So I complacently put it all down to being a nuisance rather than a show-stopping issue. Reassuringly, whenever I checked the backed-up data after a daily backup, everything seemed 100% up to date. I could not see any alternative to letting my daily backup take whatever time it wanted to take and leaving my system alone to complete the job each time. Because the backup device is a USB-connected external drive, this inevitably caused a "Removal vetoed" response - and, in any event, it didn't solve the underlying problem. I found and followed advice about this issue in your forum and added a "conf.src_eject_device 1" command as an. Instead of being completed in minutes, with Bvckup 2 addressing only the handful of files I had used during the day, the backup ran on and on for ages and reported repeated instances of "destination snapshot is out of synch". From the second backup onwards it became obvious that something significant had changed. As far as I recall, the only setting I changed this time was for 'When to backup', where I opted for 'When manually started'.Īs usual the first backup I ran was, in effect, a straightforward direct copy of all my data.
Bvckup 2 setfile time failed with 87 archive#
My plan was to leave most of the settings as Bvckup 2's defaults: Use destination snapshot, Use delta copying, Archive backup copies of deleted items, etc etc. I made my destination (to an external hard drive) a new folder so as to keep data backed up from the old SSD separate from data backed up from my new drive.

Consequently I had to restore and re-create everything from scratch, including setting up a new backup regime.Įxactly as before I made my source c:\Users\\OneDrive\Documents. Very recently my solid-state drive unexpectedly failed after only 11 months and was replaced under warranty. I have been using your great app for years with immense satisfaction and have always found it relatively straightforward to set up and manage. Feb 08, 2022Hello, something very wrong is occurring with my reinstated Bvckup 2.
