The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Not quite sure where to apportion blame here. Got the Dropbox module working, and this one certainly works when doing this manually...
I have a files and a DB scheduled backup, using the same profile, in BAM, to Dropbox and NS. The Dropbox one works ok, I see two files from the backup processes. I get an email as below each morning from my site saying the backups to NS were successful but on checking in the NS interface, I only see one, the latter of the two that were sent...(?)
Apache ✆ 9:45 AM (9 hours ago)
Default Database backed up successfully to mysite-20111115T044523 in destinat...Apache ✆ postmaster@mysite.com
9:45 AM (9 hours ago)Files Directory backed up successfully to mysite-20111115T044529 in destination NodeSquirrel in 21876.78 ms.
Comments
Comment #1
niklp commentedI'm now working with all the latest dev versions of everything and this still occurs. My notification emails tell me the backups were successful. However, there is still only one file present in the NS interface, out of two that are supposed to be there. This is a critical failure surely? Very surprised this issue is not being pursued...
Comment #2
niklp commentedRonan. I can't think of any more information to give you, in honesty.
The backups work via Dropbox, I get two files. In NS I only get the last one that executed, which was the last one in the schedule list. That's the same info, and it's all I can find or think of! :/
Comment #3
niklp commentedThis is the only other thing I've got. Was investigating further but NS site is hobbling today sadly :(
Comment #4
niklp commentedI now have two daily backups from my site as before (files, sql) and an additional two from the same site as I'm experimenting with Pantheon hosting. Files are seemingly getting wiped as they're written. Out of four backups today, only one file exists, which as per above is the last one to be written to the NS system.
Not quite sure how this is not getting more attention, this is completely a critical bug as far as I can make out? :/
Comment #5
ronan commentedOk I think I've figured this out. That screenshot was actually super helpful.
You've run into a fundamental issue with schedules in backup and migrate 2. Because schedules have no way of identifying their own files, when you have multiple schedules pointing to the same destination with a 'keep only' number then the different schedules will each delete the other's files. This means that the schedule you have set to keep 1 backup is deleting all the other files in the destination. This will be fixed in Backup and Migrate 3 which is in progress because that version has the ability to save metadata with backup files identifying (amongst other things) which schedule created the file.
The solution for now is to up the 'keep' number on all of your schedules or remove it altogether. Once version 3 of B&M is ready for production use you will be able to keep the exact number of each schedule that you want.
Thanks
Ronan
Comment #6
niklp commentedRonan, slightly confused - this doesn't seem to be an issue in Dropbox, only in Node Squirrel? Is that expected? (I realise that "keep" in the context of Dropbox is perhaps different)
Comment #7
ronan commentedOk, maybe I'm misunderstanding then, because this behavior should be the same no matter what the destination is. Although it's possible that Dropbox is ignoring the deletes. I haven't played with dropbox as a backup destination that much. Are you saving both schedules to the same directory in dropbox or to 2 different directories? That would explain the difference.
Does the problem go away when you increase both schedules to keep more than 1? Set both to, say, 4 and see how many you end up with.
Comment #8
dgorton commentedJust wanting to check in - is this still an issue with the latest stable (or dev) versions?
Comment #9
ronan commentedIs this still an issue? If so please reopen.
Comment #10
niklp commentedSorry mate I forgot to test it, I'll report back shortly.
Comment #11
niklp commentedActually I can't tell what's going on here now. I have two sites on there at the moment. My files backups are saving properly now which is all good, and the DB backups have always been ok (as per the issue, I think this is based on the order they arrive with you guys).
However, both sites are set up to save 3 of each of files and DB backups. My business site has 6 total backups, which is correct - this was dozens not long ago, and I didn't delete them, so I assume a module or local update has cleared that problem. The other site, that of a client, has only 4 total backups despite identical settings.
That's my findings, do as you will!! ;)