Backing up with Laravel (laracon)

A1b4b398630bbd32b77a82cbc37fae9a?s=47 Freek Van der Herten
August 24, 2016

Backing up with Laravel (laracon)


Freek Van der Herten

August 24, 2016


  1. 2.

    About me Freek Van der Herten Partner & developer at

    SPATIE @freekmurze
  2. 4.

    Since 2003 Websites, applications and webshops Team 4 developers, 1

    manager Specialization Laravel development
  3. 6.

    Open source software We use a lot of it Nginx,

    Laravel, Ubuntu, Elasticsearch, Memcached, Redis, Beanstalkd, MySQL, Composer, Glide, Homestead, Flysystem, Fractal, Carbon, PHPUnit, NPM, React, jQuery, Java, SSH, Sequel Pro, BackupPC … Basically everything listed in composer.json and package.json
  4. 7.

    ± 80 packages on Packagist + 800 000 downloads A

    lot of benefits: learning, forced to write documentation and tests, showing the quality of our work, eat our own dogfood We create a lot of it Open source software
  5. 9.

    Associate users with roles and permissions Laravel Permission $role =

    Role::create(['name' => 'writer']);
 $role->givePermissionTo('edit articles');
 $user->can('edit articles’);
  6. 11.

    Speed up your application 
 by caching the entire response

    Laravel Responsecache RESPONSE CACHE REQUESTS APP 1 2
  7. 12.

    Associate files with Eloquent Models Laravel Medialibrary $newsItem->addMedia($file) ->toCollection('images'); 

 $newsItem->addMedia($bigFile) ->toCollectionOnDisk('downloads', 's3');
  8. 13.

    Transformation layer for complex output Fractal $manager = new Manager();

    $resource = new Collection($books, new BookTransformer());
  9. 14.

    Easy integration with Fractal in Laravel Laravel Fractal fractal()

    ->transformWith(new BookTransformer())
  10. 16.
  11. 21.

    Small sites Shared hosting Backups by hosting provider Did not

    do anything regarding backups ourselves Hosting Up until a few year ago
  12. 22.

    Bigger applications Learned basic server management through resources like

    Digital Ocean Forge / Ansible Hosting How we are currently doing it
  13. 24.

    Horror Story #1 Earlier today, our Cloud Operations team was

    alerted to some performance issues affecting the physical server that hosts your droplet. … The damage was serious enough that this droplet was lost and not able to be restored. One fine morning I got this mail from Digital Ocean Full story:
  14. 25.

    Horror Story #2 This message is a follow-up to our

    previous emails. Despite the very best efforts of our engineering and datacenter operations teams, unfortunately the host machine that your cloud server resides on was not able to be recovered. At this point, there is complete data loss on the server. Horror can occur everywhere. A mail from Rackspace: Source:
  15. 29.

    Relying on DO backups 
 is not enough! Only weekly

    snapshots Potentially a lot of data could get lost All the backups in the same datacenter If Digital Ocean is down backups can’t be accessed
  16. 30.
  17. 31.

    DIY: A bash script Hosted service: Open source: BackupPC,

    Bacula Solutions Do not put your eggs in one basket
  18. 32. interface Dumps the database with mysqldump Uploads dump +

    files using was cli tool to S3 Use cron to frequently run script Downside: no notifications when something goes wrong
 A bash script
  19. 33.

    Backups as a service Not free Install Ottomatik Server Agent

    on every server Easy to use interface Bring your own storage
  20. 34.

    Open source software Installed onto a control server SSH’s into

    servers to be backed up Uses hard links to save disk space Some system administration knowledge is required to setup up BackupPC SERVERS BackupPC SSH
  21. 36.

    Backup files and databases to one or more filesystems Cleanup

    old backups Sending notifications Easily installed into any Laravel application Laravel Backup
  22. 37.
  23. 39.

    Backups use a lot of storage Artisan task to clean

    up old backups Fully configurable Will never delete the youngest backup Grandfather-father-son rotation scheme Cleanup old backups
  24. 40.

    Grandfather-father-son rotation scheme FEW TIMES A DAY DAILY (16) WEEKLY

    (8) MONTHLY (4) YEARLY(2) KEEP
  25. 41.

    Detects when no backups were made in a certain amount

    of days Detects if there is too much storage used Fully configurable Monitor backups
  26. 42.

    On (un)successful events (backup failed, youngest backup is too old,

    backup uses too much storage …) Mail, Slack, Telegram, Pushover Fully configurable Easy to extend Sending notifications
  27. 43.
  28. 44.

    Your Laravel app may break Server may be down Install

    the package in a Laravel app on a separate server Monitor the backups of all your apps from there Monitoring best practices
  29. 46.

    Install a Laravel app on the same server Point the

    configuration the the database/directories you which to backup Profit! Backing up a non Laravel app
  30. 47.

    Backup to multiple filesystems Get notified when something goes wrong

    Cleans up older backups Easy installation Cost: one postcard Benefits
  31. 48.

    Drawbacks Only use this for small to medium sized apps

    Can consume quite a bit a of disk space while backing up Application has credentials to access the backups No restore options
  32. 50.

    Make Laravel 5.3 compatible Use Laravel 5.3’s native notification capabilities

    Easier passing of arguments to the db dumpers PHP 7 Future plans
  33. 51.

    Do not rely solely on backups of your service provider

    Take care of backups yourself as well Many options available both free and paid Laravel Backup can help you out (cost: one postcard) Summary