Merge branch 'master' into blog

content/features/_index.md

@@ -45,7 +45,7 @@ hidePageNav: true
   title="Email notifications" 
   image="/static/lib/logo/features/email-notifications.png" 
   href="/features/email-notifications"
-  text="If something happens and a backup process fails you will get an email notification." >}}
+  text="If something happens and a backup process fails we will send you an email notification." >}}
 {{< featureCard 
   title="GitHub organizations" 
   image="/static/lib/logo/features/organizations.png" 

content/features/bulk-operations.md

@@ -1,10 +1,40 @@
 ---
-title: "[TBD] Bulk Operations"
+title: "Bulk Operations"
 weight: 10
 ---
 
 # Bulk Operations
 
-This page is under development. Please come back later.
+If you have a large number of repositories it is not comfortable to manage their settings using Cloudback Dashboard with the card-based user interface. Cloudback offers the `Bulk Operations` dialog instead. The dialog allows you to apply settings to many repositories with a single click.
 
+<img src="/static/features/bulk-operations.png" alt="Bulk Operations"/>
 
+## Repository name pattern
+
+Repository name pattern accepts [wildcard](https://en.wikipedia.org/wiki/Wildcard_character) characters and a comma character to join multiple queries:
+
+Wildcard characters:<br>
+`*` - zero or more characters <br>
+`?` - exactly one character<br>
+`,` - specify multiple queries separated by a comma<br>
+
+Samples:
+
+For the account `cristobal-martinez` with 4 repositories `awesome`, `awesome-repos`, `books` and `static-website-example`:
+
+* `*` - matches all repositories
+* `awe*` - matches `awesome` and `awesome-repos`<br>
+* `awe*,book` - matches `awesome`, `awesome-repos` and `book`<br>
+* `*b*` - matches `book` and `static-website-example`<br>
+
+## Settings that can be applied
+
+* `Schedule` - an hour for a daily backup trigger
+* `Retention` - backup archive retention policy, how many days we store an archive before we delete it
+* `Storage` - storage for backup archives, could be `Cloudback` or created by a user
+* `State` - schedule / unschedule, or enable / disable automated daily backups
+
+## Learn more
+
+- [What is inside of a backup?](/features/metadata)
+- [What is a backup storage?](/features/various-backup-storages)

content/features/email-notifications.md

@@ -1,8 +1,51 @@
 ---
-title: "[TBD] Email Notifications"
+title: "Email Notifications"
 weight: 7
 ---
 
 # Email Notifications
 
-This page is under development. Please come back later.
+If something goes wrong and a backup process fails we will send you an email notification. We send notifications daily at 22:00 UTC with all failures in the previous 24 hours. 
+
+Once backup is failed our Support Team gets notification as well. Is the issue is not related to [storage](/features/email-notifications/#1-storage-issue), the team starts investigation as soon as possible and reports you their findings by email.
+
+<img src="/static/features/email-failure-notification.png" alt="Email notification"/>
+
+## Why can a backup fail?
+
+A backup can fail for various reasons, almost all of them fall into four categories: 
+
+### 1. Storage issue
+
+The issue related to storage is the most frequent cause of backup failures. Usually, Cloudback loses access to your storage and is unable to upload an archive. Below are typical situations:
+- An `access token` or `shared signature` has expired
+- Storage configuration has been changed, but Cloudback config was not updated
+- Storage provider went offline
+
+In order to troubleshoot a storage issue please verify your storage settings in the repository card using the `Edit storage` button:
+
+<img src="/static/features/edit-storage.png" alt="Edit storage" width=500/>
+
+### 2. GitHub outage
+
+GitHub itself may go offline, sometimes it happens and may last a few hours. Cloudback will try to backup 6 times in 6 hours. If nothing works a backup will fail. There is a [GitHub Status](https://www.githubstatus.com/) page where you can check the `API Requests` operational status.
+
+### 3. GitHub account issue
+
+There may be two types of issues related to your GitHub account:
+- [Cloudback App](github.com/apps/cloudback) installation may be suspended or uninstalled from your account. If the application is uninstalled, Cloudback cannot access your data so backup fails.
+- Repository may be deleted or inaccessible to Cloudback App
+- Your GitHub account may be locked or suspended. It is rare but happens. Please check your account is accessible.
+
+### 4. Cloudback issue 
+
+Sometimes backup software itself can fail. It happens and our Cloudback Support Team is in charge to recover the backup, analyze a root cause and implement all necessary changes to prevent it from happening in the future.
+
+## Notifications on a successful backup
+
+As for now, we support failure notifications only. Please let us know if you need daily notifications of all your successful backups and we will consider implementing this feature.
+
+## Learn more
+
+- [What is inside of a backup?](/features/metadata)
+- [What is a backup storage?](/features/various-backup-storages)