Magento2: [2.1.1] Backup tool, issue with symlinked media folder.

Created on 2 Sep 2016  路  6Comments  路  Source: magento/magento2

Symlinked media folder is often used for high availability clustered setups where mounting the shared resources (such as pub/media) amongst multiple physical machines.

Preconditions

  1. Install Magento 2.1.1 CE
  2. Env: PHP 7, Nginx, Varnish, Production mode
  3. Using media storage default (file system).

    Steps to reproduce

  4. Create /mediastorage folder.

  5. Symlink pub/media to . /mediastorage.
  6. Create a backup in the admin panel ("Database and Media Backup")
  7. Download the backup tar file
  8. Unzip and go into the pub directory of the tar archive.

    Expected result

  9. media folder should not be a simple file. The backup routine should acknowledge the media folder as a folder and zip the actual folder.

    Actual result

  10. Media folder is a file ( and not a folder ).

  11. As a result. No media files is backed up!

image

needs update bug report

Most helpful comment

I Agree for the "System Backup" - which essentially should copy the installation from the root folder. However, I used "Database and Media Backup" and expected that the contents of the media folder would be backed up.

All 6 comments

I think this is how the 'System Backup' is supposed to work. When you put it back your symlink is there again.
Now for the 'Database and Media Backup' you might have a point.

I Agree for the "System Backup" - which essentially should copy the installation from the root folder. However, I used "Database and Media Backup" and expected that the contents of the media folder would be backed up.

This is quite important issue. The "Database and Media Backup" does not work atm. It seems just like a "System backup".

Yeah, we have this issue as well. It would be great to have the option to "Follow Symlinks"

@peec Hello, can you check your problem on the latest version Magento 2? I can`t reproduce it

According to contributor guide, tickets without response for two weeks should be closed.
If this issue still reproducible please feel free to create the new one: format new issue according to the Issue reporting guidelines: with steps to reproduce, actual result and expected result and specify Magento version.

Was this page helpful?
0 / 5 - 0 ratings