In this article:
Adding new plan
To create a new backup plan click on Add Plan button on the top bar in Plans tab.
After clicking on it new panel will be displayed in Xopero web-console. First step is to define a name for the task in Backup plan name field. After that select one of four available backup types.
This type of plan lets you protect individual files or directories. Granular recovery of data protected using this type guaranties fast recovery in many different scenarios.
For in-depth guide for this type of plan see: File-level Backup
Creating an image of your devices lets you in fast and easy way protect whole devices. This type of backup is stored in .RAW format and depending on settings allows users to restore their systems for example in case of drive failure.
For in-depth guide for this type of plan see: Image-level Backup
This type of plan lets you protect Mailboxes, OneDrive, Contacts and Calendars from your Microsoft 365 organization.
For in-depth guide for this type of plan see: Microsoft 365
Lets you protect your repositories from platforms such as GitHub or BitBucket.
For in-depth guide for this type of plan see: Git Backup
What shows under Resources section of plan creation is highly dependent on what type of plan has been chosen.
In File-level and Image-level plans Resources will be replaced by Devices.
Microsoft 365 replaces Resources with Users.
More about selecting resources for protection is written in articles regarding their respective types.
Data to protect
Data available for protection differs between File-level/Image-level and Microsoft 365.
While in first one you can choose between using global rules and selecting directly from the device, Microsoft 365 has predefined resources (Messages/OneDrive/Contacts/Calendars) that can be protected.
Data storage is the location where the backups are stored. Xopero One allows users to customize their backup policies with storage locations on per project basis.
Currently there are five types of storages that you can choose from:
- Local directory,
- Network location (SMB Share),
- Amazon Web Service storage,
- S3 compatible,
- Xopero Cloud.
To learn more about storage management see: Storage management
The last part of creating a new backup plan is to define its schedule. Start by selecting suitable policy type.
- Basic - is the simplest type of schedule offering high amount of versions compared to used storage space.
Basic is using two backup cycles for:
- Full copy - made every month by default,
- Incremental - commonly made daily.
- GFS (Grandfather-Father-Son) - policy dedicated for long-term archiving. It provides a possibility to store data over extended period of time while keeping a small amount of versions.
GFS is a multi-level scheme using multiple backup cycles for different time periods:
- Full copy ("Grandfather") - made with greatest time interval (least often - monthly by default),
- Differential ("Father") - performed more often than full copy (weekly),
- Incremental ("Son") - most common with the smallest interval (daily).
Other schedule settings
Backup window - time frame during which specific backup plan can operate. If the policy exceeds allowed timeslot, it will be automatically terminated.
Start delay - defines for how long GitProtect must wait before starting backup of the next repository / device in the list.
Don't suspend while performing a backup - prevents your device from going into suspended mode.
Last part of schedule section is to define data retention policy. You can set one of three rules to decide for how long you want to store your data.
Keep infinitely - versions won't be removed,
By time - choose different retention periods for each kind of copy,
By numer of copies - total number of versions to store.
Run cleanup - decides when to enforce retention policy:
- After the backup - cleanup will only run when new version is ready and saved in the storage,
- Before the backup - outdated versions will be removed when new backup starts.