I had problems with drush update backups in the past.
Those problems can be caused by different reasons. Mostly because of folder permissions.
A lot of issues about this are created in Drush's issue queue (like #1877324) and the solution is usually simple... just use "--no-backup" option when executing drush update.

Well this is an issue with a patch which can help ("try first, read documentation later") users by printing an extended Note when doing the drush update.
Full note looks like this:
Note: A backup of your project will be stored to backups directory if it is not managed by a supported version control system. (Run drush update with "--no-backup" option to skip backups.)

CommentFileSizeAuthor
#1 drush_update_note_extended-1976730-1.patch974 bytesalesr

Comments

alesr’s picture

Status: Active » Needs review
StatusFileSize
new974 bytes

Here is a small patch.

greg.1.anderson’s picture

Version: 7.x-5.x-dev » 8.x-6.x-dev
Status: Needs review » Closed (won't fix)
Issue tags: +Needs migration

This issue was marked closed (won't fix) because Drush has moved to Github.

If desired, you may copy this task to our Github project and then post a link here to the new issue. Please also change the status of this issue to closed (duplicate).

Please ask support questions on Drupal Answers.