**Schedules**\
eazyBackup can run backup jobs automatically on a schedule. It is recommended to automate your backups on a regular schedule.
Click the "+" button to add a new schedule.
**General Schedule Options**
From the 'General' tab enter a name for the new schedule. You can have multiple schedules for a single protected item, for this reason it helps to give it a name.
When a schedule is due to run, the backup job will run automatically to the selected Storage Vault.
You can also configure advanced backup runtime options, such as the following:
* **Skip if already running**. If this option is enabled, and another backup job is known by the Server to exist for the same Protected Item and Storage Vault in "Running" status, then this backup job will be skipped. Skipping a backup job creates a log entry for the job in "Skipped" status.
* **Cancel if still running after**. If the backup job exceeds this time limit, the backup job would be cancelled.
* **Limit Storage Vault Speed**. This option allows you to limit the total speed to the Storage Vault. The speed limit applies to the total combined read/write bandwidth.
* **Limit backup to use only 1 disk thread**. eazyBackup uses multithreading to improve performance. On some machines, this can impact PC performance. If you are experiencing low system performance while the backup job is running, you can try to enable this option.
**Retention**
"Retention" is the concept of classifying backed-up data, to determine what data should be kept, and what data can be safely removed.
You may choose to keep the last 30 days of backed-up data, or all data from the last 100 backup jobs; but any data older than this is unlikely to be useful and can be safely removed.
**Start your first backup**
Click "Finish" to complete the setup wizard. You can also choose to check the box to run your first backup immediately.
***
[eazyBackup](https://eazybackup.com)
# Creating Protected Items
**Add New Protected Item**
***
* Start by adding a new Protected Item, you can enter a brief name describing what data is being backed up in the "Description" field.
* Select which type of data is to be protected.
\
**Select Items to Backup**
***
Choose items you would like to include in the Protected Item. For file and folder backups, you can use either the quick selection menu or the custom file selection depending on your needs.
**Commands (Protected Item)**
***
You can optionally configure Commands that run before or after the Protected Item is backed up.
The Commands feature on a Protected Item works the same way as for Commands on a Storage Vault or on a Schedule. For more information about the Commands feature, please see the [Commands Article](/documentation/commands) .
{% content-ref url="/pages/L7Q3LJw9lYmaVpKnkEgO" %}
[Commands](/documentation/commands)
{% endcontent-ref %}
The default is no extra commands, only enable this option if you have a specific use case. Please contact support if you would like assistance creating before / after commands.
\
**Schedules**
***
eazyBackup can run backup jobs automatically on a schedule. It is strongly recommended to automate your backups on a regular schedule.
Click the "+" button to add a new schedule and create a friendly name for the schedule.
**General Schedule options**
When a schedule is due to run, the backup job will run automatically to the selected Storage Vault.
You can also configure advanced backup runtime options:
* **Skip if already running**. If this option is enabled, and another backup job is known by the eazyBackup Server to exist for the same Protected Item and Storage Vault in "Running" status, then this backup job will be skipped. Skipping a backup job creates a log entry for the job in "Skipped" status.
* **Cancel if still running after**. You can set a time limit for the backup job. If the backup job exceeds this time limit, the backup job would be cancelled.
* **Limit Storage Vault Speed**. This option allows you to limit the total speed that eazyBackup reads and writes to the Storage Vault. The speed limit applies to the total combined read/write bandwidth.
* **Limit backup to use only 1 disk thread**. When reading multiple files from the local disk for backup, eazyBackup uses multithreading to improve performance. On some machines, this can impact PC performance. If you are experiencing low system performance while the backup job is running, you can try enabling this option to see if it resolves the issue.
**Schedule times**
You can configure the times when this schedule will be executed. You can add multiple times to the same schedule.
The available time-based schedule frequencies are:
* **Hourly**. The schedule would run every hour. You can choose the minutes past the hour.
* **Daily**. The schedule would run every day. You can choose the time of day (hours/minutes). The hours are specified in 24-hour time, from 0 to 23.
* **Weekly**. The schedule would run every week. You can choose the day of the week, and the time of day (hours/minutes). You can choose multiple days of the week.
* **Monthly**. The schedule would run every month.
* **Once only**. The schedule would run only when the specified date and time is reached.
If the device is online, eazyBackup will try to run the backup job. If the device is not online, or the backup job could not be started, a "Missed" job will show in the backup job log.
The available event-based schedule frequencies are:
* **Also run when PC starts**. The schedule would be initiated immediately after the PC boots.
* **Also run when PC starts, if the last job was Missed**. The schedule would be initiated immediately after the PC boots if the last backup job for this Protected Item and Storage Vault pair was in "Missed" status. This allows you to "catch up" missed backups for PCs that are only online at irregular intervals (e.g. laptops).
The time that the "PC starts" is defined as follows: the time that the eazyBackup background service started, if the system uptime is less than 10 minutes. *(This definition is subject to change.)*
**Commands (Schedule)**
You can configure Commands that run before/after this Schedule runs.
The Commands feature on a Schedule works the same way as for Commands on a Protected Item or on a Storage Vault. For more information about the Commands feature, please see the [Commands Article](/documentation/commands).
{% content-ref url="/pages/L7Q3LJw9lYmaVpKnkEgO" %}
[Commands](/documentation/commands)
{% endcontent-ref %}
**Retention (Protected Item)**
***
On the Retention tab, you can configure a retention policy to apply when backing up this Protected Item to a specific Storage Vault. If no policy is configured for a specific Storage Vault, the default retention policy for the Storage Vault will apply.
***
[eazyBackup](https://eazybackup.com)
# How to Backup Windows Network Shares and UNC Paths
eazyBackup can back up Windows network shares (SMB), however, because eazyBackup runs as a background service user, there are some issues with authentication to be aware of.
{% hint style="info" %}
When possible, the best option would be to to install eazyBackup directly on the device rather than backing up over the network.
{% endhint %}
**Network Authentication**On Windows, your logged-on user session may have its own mapped network drives. These mapped drives belong to your logged in user session and are not available to background service accounts. Most UNC shares will require network authentication. If your backup logs show messages like WARNING Lstat: CreateFile \\\\?\UNC\\...: Access is denied., this is likely because the eazyBackup service account is not logged into your network shares. We will show you how to configure the backup with network authentication to avoid these issues. #### Here are the steps: Add a new Protected Item or modify an existing file and folder protected item.
* (Optional) By default, all files are restored. You can use the "Choose files" radio option to select individual files or folders to restore.
{% hint style="info" %}
Note: You need to have purchased a backup plan that includes the Disk Image feature in order to create a Disk Image Protected Item.
{% endhint %}
**Select the disk that will be included in the backup**
{% hint style="info" %}
After creating a Disk Image backup, if any changes are made to the partition table of the selected disk, the disk ID may change and eazyBackup will not recognize the disk. \
\
You will receive a warning that the drive can no longer be found and you will need to reselect the drive and/or partitions.
{% endhint %}
**Advanced Option: Include unused disk sectors for forensic data recovery******
By default unused space from the disk will be excluded from the backup, enabling this option will include any non-indexed and marked-as-deleted files in the free space. This could be used for forensic data recovery, but keep in mind that it will lengthen the backup time.
***
[eazyBackup](https://eazybackup.com)
# Disk Image Backup Restore Guide
Disk Image backup protects a complete disk or individual partitions and allows you to restore the backup to bare metal in the event of a disk failure.
Boot your Workstation / Server with the eazyBackup [USB recovery media](#create-usb-recovery-media) and restore disks or partitions without requiring temporary spool space.
The Disk Image can be restored to dissimilar hardware if needed.
Disk Image Backups can be performed to multiple destinations, such as a local storage device in addition to cloud storage. Having a local, onsite backup will reduce the time needed restore large backups and offers additional redundancy.
#### Disk Image Backup
The demo video shows how a typical Windows PC can be backed up using the Disk Image Protected Item type
{% embed url="
eazyBackup stores the Disk Image files in VMDK format, from which single files can be extracted.
#### Restore to physical device(s)
In order to restore to physical hardware, the target disk or partition should be unmounted (not in use). eazyBackup may be able to do this automatically from within the currently booted OS if no programs are using the target drive (e.g. for a non-boot drive).
* If the goal is to restore to the boot drive, first, reboot the PC into a recovery environment.
* When restoring a smaller partition into a larger one, eazyBackup will automatically extend the restored filesystem to the fill the target partition. eazyBackup does not support restoring a large backed-up partition into a smaller physical partition. The partition must be shrunk using the OS’s partition manager prior to performing the backup.
**Restore from Windows boot environment**
1. Select a backed-up disk or partition to restore, from the left-hand column
2. Select a target disk or partition to write to, from the right-hand column
3. Click the *Add to restore queue* button
4. Repeat steps 1-3 as necessary for other disks and partitions
5. Click the *Restore* button to begin the restore job
{% hint style="info" %}
The *Edit* function can be used to re-partition the local drives using Windows Disk Management. After doing so, the *Refresh* function may be used to refresh the view of the local disks and partitions able to be selected for restore.
{% endhint %}
**Restore from Linux boot environment**
Steps to restore an entire disk, without spooling:
1. Restore just the `disk.vmdk` file (without the data extents), and open it in a text editor in order to read the partition sizes.
2. Recreate partitions to the exact target size
3. Single partitions can be restored without any local spool disk, using the "Program Output" restore option, and selecting only a single partition file for restore: `dd of=/dev/sdx1 bs=8M`
#### Restore Disk Image as virtual disk files
There is one plain text VMDK descriptor file containing metadata about the whole drive, plus separate raw image files for each partition’s extent on the disk. The plain text file is labelled `disk.vmdk` by default.
Partitions of the disk that were not selected for backup are represented as zero extents in the VMDK descriptor file. The effect of this is that the restored disk image will appear to have the full disk size, even if only a small amount of partitions inside it were selected. However, the zero extents will be compressed inside the Storage Vault.
The VMDK disk images may be restored, then, optionally, do one of the following:
* Extract single files from them, or
* Recover to a local virtual machine, or
* Recover to a cloud server
#### Restore files and folders from Disk Image
This feature allows a customer to browse the filesystem in a Disk Image backup and restore files and/or folders without downloading the whole VMDK disk image in advance. Currently this feature is supported for the NTFS.
#### VMware virtual disk
Starting from version 23.9.5, there's a new feature for disk image backup. Now, you can restore your disk image backup as a virtual disk that works with VMware. This means you can use it in VMware without needing to change anything.
#### Create USB Recovery Media
The eazyBackup app supports the creation of USB Recovery Media from the wizard on the Settings screen.
This allows a user to boot from the USB device, type-in the username and password for the backup account, and make a full restoration from backup onto the drive(s) of the connected PC. In this fashion, bare-metal restorations can be achieved.
The following options are available:
* WinRE
* Windows To Go
Create a new "Custom" storage vault.
On the "General" tab, we can give our storage vault a name, enter something that makes it easy to identify later.
From the "Storage" tab, click the drop down box and choose "Local Path". Next, click the browse button and locate the local storage device where you want to store backup data. When you have added the path to your local storage device click "Save".
Now you should have a new item listed under "Storage Vaults".
Now we can create a new Protected Item which will backup data to our local storage device. From the "Backup" tab, select "Add Protected Item".
Here we can give our "Protected Item" a name, enter something that makes it easy to identify later. Click "Next".
Now we need to add some files and folders to this backup job. Click the "+" button to browse your hard drive, place a check mark in the box next to the folders you want included. When you are done, click "Next".
If you want this Protected Item to backup your files on a regular schedule, click the "+" button to create a new schedule.
Here we can give the schedule a friendly name. In the "Storage Vault" selection menu, choose the new Storage Vault you just created from the list.
On the "Time" tab click the "+" button to add a time to run this Protected Item. Click "Save" when finished.
Your "Schedules" page should now look something like the example below. As you can see we have an hourly backup which will store data on our local Storage Vault, which we named "External Drive". You can also configure this Protected Item so that it will backup to multiple locations, for example, your eazyBackup Storage Vault.
If you want to add another destination for this Protected Item click the "+" button.
Again, we can give the schedule a relevant name. In the "Storage Vault" selection menu, choose "eazyBackup". On the "Time" tab click the "+" button to add a time to run this protected item. Click "Save" when finished.
Now we have two hourly backup schedules, one which will store data on our local Storage Vault and a second schedule which will store data in your eazyBackup Storage Vault. Click "Next" when you are ready.
Click "Finish" to save the new Protected Item. You also have the option to run a backup job now.
***
[eazyBackup](https://eazybackup.com)
# Seed Load Walk through
The seed load process allows you to perform your initial backup to a local external hard drive and then courier the external drive to the server administrator.
## What you need up front
* An external disk (USB) with enough free space for the first full backup. Use a filesystem that supports large files (NTFS, exFAT, or ext4).
* The eazyBackup client installed and signed into the correct user account.
{% hint style="info" %}
Using a slow external drive for your seed-load backup will lengthen the import. If speed matters, choose a faster device—ideally a solid-state drive.
{% endhint %}
{% embed url="
Once you have Kroll configured to make a daily backup to the local device, you can configure eazybackup to perform a daily backup of your local files.
#### Step 2. Schedule eazyBackup to backup the Kroll database export
* Open the eazyBackup desktop application
* Click "Add Protected Item"
* Choose Protected Item type "Files and Folder"
* Click the 'Custom' tab
* From the 'Custom file selection' tab, choose the location where you scheduled the daily export of the Kroll database.
* Click "Next" in the Protected Item wizard until you reach the Schedule option. Create a new daily backup schedule for this Protected Item.
* Remember that your Kroll database export must have completed before eazyBackup can start, allow enough time between when the Kroll application exports a copy of your database and when eazyBackup is scheduled to run.
At a minimum you should backup the following locations with the eazyBackup desktop application. After the backup has completed, we recommend you preform a full restore so that you fully understand the process of backup and restoring in the event of an emergency.
`C:/KrollWin/Backup`
`C:/KrollWin/Medis`
`C:/KrollWin/POS`
`C:/KrollWin/BuddyFill`
***
[eazyBackup](https://eazybackup.com)
# How to Backup Dentrix Database to the Cloud
We recommend performing a daily backup of the Dentrix database. Start the backup after business hours to ensure all patient data is included in the daily backup.
We suggest that in addition to the Dentrix common folder, you backup all of the files on your server with our File/ Folder Protected Item. You can also perform a Disk Image backup in the event that you require a bare metal disaster recovery solution. At a minimum it is critical that you back up your Dentrix database files from the Common folder.
#### Step 1. Schedule a daily database export from Dentrix:
Export a copy of your live database either manually or automatically. For this step you will need to use the Dentrix Server Administration Utility. **In order to back up the active Dentrix database files, the database must be exported to a location where the eazyBackup desktop application can back up a copy of your database.**
* Open this Dentrix Server Administration Utility. This is usually located at `C:\Program Files\Dentrix\_ServerAdmin.exe`.
* Click the 'Export/Restore Database' tab
* Under Scheduled Database Exports, select "Enable Scheduled Exports".
* Configure your scheduled export time
* Click "Update Scheduled Status" to save the export schedule.
#### Step 2. Schedule eazyBackup to backup the Dentrix database export
* Open the eazyBackup desktop application
* Click "Add Protected Item"
* Choose "Protected Item type File / Folder Backup"
* Click the 'Custom' tab
* From the 'Custom file selection' tab, choose the location where you scheduled the daily export of the Dentrix database.
* Click "Next" in the Protected Item wizard until you reach the Schedule option. Create a new daily backup schedule for this Protected Item.
* Remember that your Dentrix database export must have completed before eazyBackup can start, allow enough time between when the Dentrix Server Administration Utility exports a copy of your database and when eazyBackup is scheduled to run.
***
[eazyBackup](https://eazybackup.com)
# How to Backup Patterson Eaglesoft Dental Software
We recommend performing a daily backup of the Eaglesoft database. Start the backup after business hours to ensure all patient data is included in the daily backup.
We suggest that in addition to the Eaglesoft data folder, you backup all of the files on your server with our File / Folder Protected Item. You can also perform a Disk Image backup in the event that you require a bare metal disaster recovery solution. At a minimum it is critical that you back up your Eaglesoft database files from the default location of `C:\Eaglesoft\Data\`.
The default Data folder paths are:
* `C:\Eaglesoft\Data\Audio`
* `C:\Eaglesoft\Data\Images`
* `C:\Eaglesoft\Data\Metafile`
* `C:\Eaglesoft\Data\Customdraw types`
* `C:\Eaglesoft\Data\Documents`
* `C:\Eaglesoft\Data\Indicators`
* `C:\Eaglesoft\Data\Data2*`
#### Step 1. Make sure that everyone in the office is logged out of the application to ensure the backup process has exclusive access.
#### Step 2. Schedule the Patterson server engine to stop before the backup is scheduled to start.
* Use windows Task Scheduler to Start and Stop the Server Engine - See this article for detailed instructions: 
#### Step 2. Select Microsoft Hyper-V backup type and give the Protected Item a name:
#### Step 3. Select VMs for backup by clicking the + button:
#### Step 4. Select all Virtual Machines or individual VMs for backup:
#### Step 5. The Item selection window shows you which VMs you have selected for backup - Click Next:
#### Step 6. Create a new schedule, click the + button to create the schedule:
#### Step 7. You can now name the schedule:
#### Step 8. Select the Time tab, click the + button to add scheduled run times:
#### Step 9. Set your start time, then click OK and Next:
#### Step 10. Default retention is 30 Backup Jobs, you can modify the retention settings here to suit your requirements:
#### Step 11. Click Finish to Save the Protected Item:
***
[eazyBackup](https://eazybackup.com)
# Storage Vault Usage Report
{% embed url="
Enable the option for two-factor Authentication (TOTP).
Scan the image with your two-factor authentication app, then enter the six-digit code from the app. Save the settings to enable the feature.
With 2FA enabled, when you log into the web control panel or the backup software, your two-factor code will be required.
### Additional Account Security
{% hint style="info" %}
As of September 1st 2023, the backup application will lock automatically when it is closed. Each time the application is opened, you will be required to enter the backup account username and password.
{% endhint %}
As an additional security measure we recommend automatically locking the backup application when it is closed. If the lock has not been enabled, the software can be opened without the requirement to enter the account password or your TOTP 2FA.
* Open the eazyBackup application, select “**Account**” at the bottom left side menu,
* Select “**change account settings**” button,
* On the Account tab, click the “**Lock…**” button to the right of the Username field.
* If you confirm the confirmation to lock the application, the program immediately locks and closes. Your password (and TOTP if configured) is required to open the application again.
* Each time you login to the application you must lock it again following the steps above.
***
[eazyBackup](https://eazybackup.com)
# Securing your Backup against Ransomware
To better protect your backups against unauthorized access and types of Malware such as Ransomware, we recommend locking the application when not in use.
{% hint style="info" %}
As of September 1st 2023, the backup application will lock automatically when it is closed. Each time the application is opened, you will be required to enter the backup account username and password.
{% endhint %}
* Open the eazyBackup application, select "**Settings**" at the bottom left side menu,
* Select the "**Account**" button
* On the Account tab, click the "**Lock...**" button to the right of the Username field.
* If you confirm, the application will immediately lock and close. Your password is required to open the application again.
* Each time you login to the application, you must lock it again following the steps above.
* Locking the application will not interfere with scheduled backup jobs.
#### Enable 2FA
As an additional layer of security, it is possible to enable Two Factor Authentication for access to the application. Please see this article for steps to [enable 2FA for your backup account](/guides/two-factor-authentication-for-backup-accounts).
{% content-ref url="/pages/BHlJxkMwg0vAcPMqTaxQ" %}
[Two-Factor Authentication for Backup Accounts](/guides/two-factor-authentication-for-backup-accounts)
{% endcontent-ref %}
***
[eazyBackup](https://eazybackup.com)
# How to move your backup to a new computer
If you are replacing a computer and would like to tranfer your backup to the new computer, the guide will explain the process.
#### What You’ll Need
Before we begin, you will need the following:
* The Username of your backup account
* The Password associated with the backup account
* A copy of the eazyBackup software on your new computer
* The **bucket name** you’ll use for backups
1. You can find your account Username(s) on the Dashboard -> Users page.
A prefix to add to all stored blobs. This may be useful to isolate eazyBackup's
data within the bucket if the bucket is being shared with another application.
| Option | Requirement | Description |
| Access key | Mandatory | The access key for the Google Cloud Platform account |
| Secret key | Mandatory | The secret key for the Google Cloud Platform account |
| Bucket | Mandatory | The globally unique name of the storage bucket |
| Subdirectory | Optional | A prefix to add to all stored blobs. This may be useful to isolate eazyBackup's data within the bucket if the bucket is being shared with another application. |
Whether to access the S3-compatible server using the HTTPS protocol.
Data is encrypted and authenticated regardless of whether HTTPS is in use.
The hostname or URL for the Azure Blob Storage realm (usually core.windows.net).
Use a scheme-qualified URI (e.g. http\://) in order to toggle TLS.
Select the "Log in to network share" option from the menu to add your share credentials.
Add the path to your network share, and add network share username and password as shown in example below.
You can also work around this issue in eazyBackup by changing the Windows Service to use a different user account.
* Change service user on the `eazyBackup (delegate service)` service.
* If you are using eazyBackup on a Windows Server machine that is acting as the Domain Controller, you must choose a domain account.
***
[eazyBackup](https://eazybackup.com)
# Browse Job History
Click the "History" button at the top of the application.
### Filter
***
Click the "Filter" icon to toggle displaying the Filter pane. The Filter pane allows you to filter the displayed jobs by status, classification, Protected Item, Storage Vault, and device.
When the filter bar is closed, the data area shows all jobs from the current device. You can use the filter bar to show historic jobs from other devices in the account.
***
[eazyBackup](https://eazybackup.com)
# Cancel a Running Backup Job
You can cancel a running backup job in the backup app, select the Backup tab, click on the Protected Item with the running status icon.
Selecting the running item will reveal the details pane for that job which includes the Cancel button.
### **Procedure to force stop abandoned backup**
If the backup job appears to be in-progress but cannot be stopped and is no longer showing activity, the job may be abandoned. Please use the following procedure to stop the backup process.
Running backup jobs can be cancelled from within the desktop application or from the Control Panel.
### **Cancel Running Backup from Application**
1. First, try the procedure detailed above to cancel the running job from within the application. If there is no response using the Cancel button in the app, please use the Control Panel to cancel the job.
### **Cancel Running Backup from Control Panel**
1. Log-in to the Control Panel: [https://panel.eazybackup.ca/ ](https://panel.eazybackup.ca/)
1. From the main menu, select History -> Job History.
2. You can filter the list to show only running jobs - type Running in the Job History filter field.
3. Click the Report button next to the Running job you want to Cancel
4. On the Report page, click the Cancel button to stop the abandoned job.
5. If the job status does not change to "Cancelled" within a few minutes, please contact support for assistance.
***
[eazyBackup](https://eazybackup.com)
# Commands
You can register additional commands to run before or after any backup job. For maximum flexibility, commands can be registered:
* for a Protected Item (e.g. to dump a database), or
* for a Storage Vault (e.g. to perform custom network authentication), or
* for a Schedule (e.g. to shut down the computer afterward)
During a backup job, the commands are run in this order: Schedule Before, Protected Item Before, Storage Vault Before, Backup, Storage Vault After, Protected Item After, Schedule After.
Shell built-ins can be used as part of the command execution - the specified command is passed to either `cmd.exe` or `/bin/sh` as appropriate for your operating system.
***
[eazyBackup](https://eazybackup.com)
# Backup Report Email Address
Email addresses can be configured from two locations:
* Desktop application Accounts Settings page
* Client area Manage Accounts page
* Email reporting can be enabled and disabled per account
* Backup reports can be sent to one or multiple addresses
Open eazyBackup, select the "Account" tab, and click on "Change account settings" to update the email address.
Uncheck "Receive backup reports" to prevent eazyBackup from sending an email copy of the backup job. Logs can still be viewed from the "History" tab in eazyBackup.
### Sending reports to multiple email addresses
You can configure eazyBackup to send reports to multiple email addresses. Use comma separated format as shown below for multiple addresses.
### Configure report email from the client area
From the Manage Accounts page in the client area, you can configure basic email report settings
* Enable / disable reporting
* Add / remove and update email addresses
{% embed url="
### **Only Send Reports When Jobs Fail**
It is possible to filter reports so that you only receive an report email when the backup jobs fails. To accomplish this, you need to set the filter to "At least one of" and create a status filter for each condition where you want to receive an email. "Status" "equal" "Variable"
**Warning Status** - This means the backup completed but the backup could be incomplete, possibly some files were missed.
**Error Status** - This status means the backup failed and did not complete
**Cancelled** - The job was manually cancelled by the customer
**Missed** - The job did not run at the scheduled time
**Skipped** - Another backup job was already running, the next schedule job was skipped
***
[eazyBackup](https://eazybackup.com)
# Deleting a Protected Item
You can delete a Protected Item from the client user interface. Open eazyBackup, select the "Backup" tab, right click on the Protected Item and choose "Delete". Confirm you want to delete the Protected Item.
{% hint style="info" %}
Removing a protected item does not immediately delete customer data. Data from a deleted Protected Item will remain safe in your storage vault until the retention policy on the storage vault has expired.
{% endhint %}
***
[eazyBackup](https://eazybackup.com)
# Disk Image Backup
> *This feature requires eazyBackup 20.8.0 or later.*
> *This feature requires Windows 7, or Windows Server 2008 R2, or later.*
eazyBackup now supports taking disk image backups.
This backup type is only applicable when running on Windows. Disk Image backup on other operating systems is not currently supported by this Protected Item type.
When using the "Disk Image" Protected Item type, on the Items tab, you can select any currently-attached drives for backup, or individual partitions from any drive. It is possible to select "all drives" and exclude individual disks or partitions.
Any change to the partition structure of a drive will cause that drive to be recognized differently in eazyBackup. If you had selected such a drive, eazyBackup will warn you that the drive can no longer be found. You would need to reselect the drive and/or partitions in the eazyBackup app interface.
eazyBackup feeds raw data from each disk partition directly into its chunking deduplication engine. The disk image is deduplicated, compressed, and encrypted as it is being saved to the Storage Vault. No extra temporary spool data is generated and no additional disk space is required.
The backed-up disk image data will deduplicate with other data inside the Storage Vault. A 'Files and Folders' type backup of the same data volumes should achieve a high degree of space savings. The effectiveness of any such deduplication may be negatively affected by: (A) filesystem fragmentation on the physical volume; and/or (B) small file sizes.
eazyBackup does not currently allow additional file exclusions within a partition. A future version of eazyBackup may allow selecting files to exclude from supported filesystems (NTFS and FAT32). The files will appear to exist on the resulting disk image but contain only compressed zero ranges, saving disk space.
### Unused disk sectors
On supported filesystems, eazyBackup will exclude unused space from the disk in the backup image. Unused space is represented as zero ranges, that are compressed during the backup phase. When restoring the disk image, the file will include uncompressed zero ranges. Please see the "Supported volume types" section for more information about what filesystems are compatible with this feature. You may disable skipping free space by enabling the "Include unused disk sectors for forensic data recovery" option.
The disk must be set as Online in Windows for eazyBackup to exclude unused space. If the disk is set as Offline in Windows, eazyBackup is unable to exclude free space, even from a supported filesystem. You can change a disk's Online/Offline state from Disk Management (`diskmgmt.msc`) or from `diskpart`.
If a disk extent does not contain a filesystem (e.g. if it is a raw byte range), then eazyBackup is unable to determine which disk sectors are needed. If you select a "Raw byte range" extent, it is backed up in its entirety, even if the "Include unused disk sectors for forensic data recovery" option is selected. If the raw data contains mostly zero bytes, it will be highly compressed during the backup phase and when stored as chunks in the Storage Vault; however, if the raw data contains mostly random data, it will not compress well.
eazyBackup always skips backing up the pagefile of the booted Windows installation (`pagefile.sys` / `swapfile.sys`), even if the "Include unused disk sectors for forensic data recovery" option is enabled.
### Supported volume types
Please refer to the following table of filesystem support notes:
| Filesystem | Skip unused space | Consistency |
| NTFS (Microsoft) | Yes | Snapshot |
| ReFS (Microsoft) | Yes | Snapshot |
| FAT32 (Microsoft) | Yes | If volume is not in use |
| exFat (Microsoft) | Yes | If volume is not in use |
| UDF (Microsoft) | No | If volume is not in use |
Step 2. Select a storage vault or continue with the default if you only have one.
Step 3. Tick the "Show unknown items" box.
* Deleted Protected Items will appear as "Unknown" items
* Click the caret to expand the Protected Item to view all available dates you can restore from.
***
[eazyBackup](https://eazybackup.com)
# Random Job Delay – Protected Item Schedule
This feature will delay the start of each job by a random number of minutes between 0 and the configured number.
If your Protected Item is scheduled to start at 9:00, and you set a 30 minute Random Delay, this would mean that the jobs would randomly start somewhere between 9:00 and 9.30. The start time is chosen on a per-job basis, so different delays between 0 and the maximum configured number will apply to each job.
If you have several backups starting at the same time, this means that instead of all jobs starting within seconds of each other, the load will be distributed approximately evenly over the configured number of minutes, which will reduce the peak CPU / Network.
If you have a site with 100 backups starting at 9:00 and use a 30 minute random job delay, this would result in the 100 jobs being relatively evenly spread over the 30 minutes between 9:00 and 9:30. Typically the 100 jobs would start all at once.
A random job delay on all jobs starting at 9:00, for e.g., will help spread the load out over time; you could additionally change the start times of some of these jobs to help as well
{% embed url="
The .zip archive contains two files, install.dat & install.exe. Right click the 'install.exe' choose Run as administrator.
"Do you want this app to make changes to your device?" Click Yes.
When you complete the install, eazyBackup asks for your account details the first time you open the program.
You can find your backup account username and reset the account password within the [client area](https://accounts.eazybackup.ca/) from **Services -> Manage Accounts**.
#### **Silent install (advanced)**
eazyBackup allows you to install and configure the software silently, by running install.exe /CONFIGURE=user:password via your remote management software.
#### **Service account**
eazyBackup 18.6.0 and later automatically create a Virtual Account (NT SERVICE\backup.delegate) with all necessary permissions to back up files on the PC.
Isolating eazyBackup under a Virtual Account is supported on Windows 7 or later, and Windows Server 2008 R2 or later when that server is not a Domain Controller. On other machines (e.g. Windows Server 2008 RTM, and domain controllers) the backup service will run as LOCAL SYSTEM by default.
On a Domain Controller running Windows Server 2008 R2 or later, we recommend configuring a Managed Service Account inside Active Directory for the backup service. This allows you to isolate the backup service permissions in a password-less service account. You should apply this to the backup.delegate service (but not the backup.elevator service, used for software updates).
### **Upgrading**
The installer will safely remove and upgrade any prior version of eazyBackup, including those with a different software branding.
If the product name is changed as a result of the installation process, the newly-branded software may be installed into the old-branded directory name. You can avoid this issue by completely uninstalling and reinstalling the software.
#### **Silent upgrade (advanced)**
You can silently upgrade the software remotely via the eazyBackup Server interface, or by running install.exe /S via your remote management software.
#### **Service account**
In eazyBackup 19.3.0 and later, if you customize the backup.delegate service to use any user account other than LOCAL SYSTEM or NT SERVICE\backup.delegate, your changes will be preserved in any future software upgrade.
In eazyBackup 18.6.1 and later prior to 19.3.0, such changes will be preserved. However, if the chosen user account requires a password, it may need to be reconfigured after the software upgrade.
Prior to eazyBackup 18.6.1, any changes to the service user account were not preserved across software upgrades.
### **Uninstall**
The software can be uninstalled via the "Programs and Features" section in the Windows Control Panel.
During this process, you may be prompted whether you wish to preserve any username/password credentials saved on this computer.
You can also remove the saved credentials manually by deleting the AppData/Roaming/backup-interface/config.sys file.
You should also remove the saved credentials from the backup.delegate service. This is stored in the C:\Users\backup.delegate\AppData\Roaming\backup-tool\config.dat file (if the backup.delegate service was running as the NT SERVICE\backup.delegate user; the path may differ if the service was running as another user account).
#### **Silent uninstall**
You can silently uninstall eazyBackup for Windows by passing the /S command-line argument (e.g. "C:\Program Files\eazyBackup\Uninstall.exe" /S).
***
[eazyBackup](https://eazybackup.com)
# Linux (Other Distribution)
This is a distribution-agnostic package that can be used if eazyBackup does not have a more specific package available for your Linux distribution.
Please note that in order to avoid distribution-specific differences, the package does not automatically start on boot. You should configure your system to run the launch script in `/opt/` on boot (e.g. via a systemd unit, upstart script, `/etc/init.d/` script, or a line in `init.rc`).
### **System Requirements**
***
* CPU: `x86_64`, or `x86_32` with `SSE2`, or `ARM` (see below)
* Kernel 2.6.23 or later
* Dependencies
* `bash`, `xz`, GNU `awk`, and standard GNU/Linux system utilities
* `ca-certificates` and `tzdata` (see below)
#### **ARM CPU support**
eazyBackup is available for multiple ARM platform variants. The eazyBackup installer will select the best available binary for your hardware at install-time.
| **Platform** | **Description** |
| ------------ | ------------------------------------------------------------------------------- |
| ARMv8l | ARM 64-bit (Aarch64), no glibc required |
| ARMv7l | ARM 32-bit with vfp, and a glibc-based OS with the "hard-float" ABI (gnueabihf) |
| ARMv6kl | ARM 32-bit with vfp, no glibc required |
Timezone database dependency
eazyBackup on Linux requires the OS to provide an up-to-date timezone database, to perform timezone calculations
* On many Linux distributions, installing the `tzdata` or `timezone` package should be sufficient
* Otherwise, eazyBackup will look for a timezone database in all of the following locations;
* `/usr/share/zoneinfo`
* `/usr/share/lib/zoneinfo`
* `/usr/lib/locale/TZ`
#### **CA certificate database dependency**
eazyBackup on Linux requires the OS to provide an up-to-date set of root certificate authorities, to validate HTTPS / SSL connections.
* On many Linux distributions, installing the `ca-certificates` package should be sufficient
* Otherwise, eazyBackup will look for a certificate bundle in all of the following locations;
* `/etc/ssl/certs/ca-certificates.crt` (used by Debian/Ubuntu/Gentoo etc.)
* `/etc/pki/tls/certs/ca-bundle.crt` (used by Fedora/RHEL 6)
* `/etc/ssl/ca-bundle.pem` (used by OpenSUSE)
* `/etc/pki/tls/cacert.pem` (used by OpenELEC)
* `/etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem` (used by CentOS/RHEL 7)
### **Installation**
***
Run the `.run` file. This is a self-extracting archive, and will need to be executed in an elevated environment.
The installer will:
1. Install the software into `/opt/eazyBackup`
2. Prompt you for an initial username and password
3. Register the current Linux device into that eazyBackup account
4. Start running eazyBackup in the background.
If you make a mistake with the username/password prompt, you can run the `/opt/eazyBackup/backup-tool login prompt` command to re-enter login details.
#### **Linux Install options**
You can control the installer by setting environment variables in your shell before running the `.run` file.
The following options are available:\
`WRITE_INSTALL_LOG` Set this to a file path, to record details of the installation.\
`OVERRIDE_INSTALL_SERVER` Set this to a URL (including `http`/`https` and trailing slash) to override the authentication Server URL used by eazyBackup.
You can set an environment variable in bash either on the same line e.g. `WRITE_INSTALL_LOG=install.log ./install.run`\
or as a separate `export` command e.g. `export WRITE_INSTALL_LOG=install.log` followed by `./install.run`### **Restarting at boot** *** The installer creates a `backup-daemon-start.sh` script that can start the service. The eazyBackup agent on "Other Distribution" Linux can be restarted by running the `backup-daemon-start.sh` script. In order for eazyBackup to start after a system reboot, you must configure this script to be run on system boot. Different Linux distributions support different methods for running commands on system boot: choose the most appropriate method for your Linux distribution. Some common choices are documented below. #### **Preserve HOME environment variable** eazBackup uses the `$HOME` environment variable to find its saved credentials. When configuring eazyBackup to start at system boot, ensure that the `$HOME` environment variable is set (i.e. to `/root/`), to ensure that eazyBackup can find its saved credentials. If eazyBackup is unable to log in, it's possible that your Linux distribution does not set `$HOME` at this early-boot stage. In that case, you should try running `HOME=/root/ /opt/eazyBackup/backup-daemon-start.sh &` instead. eazyBackup will automatically try to use `/root/` as the `$HOME` directory if `$HOME` is not already set or if it is set to a blank path. Note: If you execute the .run installation script as root, this may have different results than if you execute the .run script using an elevated terminal session with 'sudo'. The 'sudo' command preserves the `$HOME` variable on Ubuntu; whilst on Debian the `$HOME` variable is erased, and sudo then sets it to the home directory of the originating user. #### **Start in the background** If you are running commands over SSH, please be aware that the backup-daemon-start.sh script runs in the foreground and will die when the SSH session is closed. You can avoid this by running the script in the background. You can run the script in the background (daemonize) by using the `backup-daemon-start-background.sh` file instead. #### **Startup via** `rc.local` You can make eazyBackup start at system boot by adding an entry to the `rc.local` file. First, find the `rc.local` file on your system: * `/etc/rc.local` (Debian/Ubuntu) * `/etc/rc.d/rc.local` (CentOS/RHEL) Add the following content to the `rc.local` file: `/opt/eazyBackupBackup/backup-daemon-start.sh &` If the `rc.local` file contains an `exit 0` statement, the additional command should be added *before* such a statement. As of CentOS 7, the `rc.local` file is not executable by default. You should run `chmod +x` on the `rc.local` file to enable using this method for startup scripts. #### **Startup via** `rc.d` You can make eazyBackup start at system boot by adding a file to the `rc.d` directory. First, find the `rc.d` directory on your system: * `/usr/local/etc/rc.d` (Synology DSM 6.1+) Add a new file to the `rc.d` directory with the following contents: ``` #!/bin/bash /opt/eazyBackupBackup/backup-daemon-start-background.sh ``` Mark the file as executable: `chmod +x /usr/local/etc/rc.d/my-eazybackup-startup-script.sh` #### **Startup via** `cron` You can make eazyBackup start at system boot by adding an entry to `root`'s crontab. 1. Run `crontab -e -u root` to launch a crontab editor 2. Add the line `@reboot /opt/eazyBackupBackup/backup-daemon-start-background.sh` #### **Startup via** `init.d` *No further documentation is available for this topic.* #### **Startup via** `systemd` You can use the following unit as an basic example: ``` [Unit] Description=eazyBackup Client After=network.target [Service] Type=simple RemainAfterExit=true User=root ExecStart=/opt/eazyBackupBackup/backup-daemon-start.sh [Install] WantedBy=multi-user.target ``` This unit file correctly starts the eazyBackup service at system boot. However, the process management in `systemd` is not fully compatible with the way eazyBackup's multi-process model works. In particular, there are compatibility issues with the software updater. As a result, the above unit is (A) unable to take advantage of process group cleanup; (B) unable to auto-restart the eazyBackup agent service; and (C) after a software upgrade, eazyBackup will keep running but the unit will remain in "exited" state. #### **Autostart for graphical desktop application** In the "Other Distribution" package, the graphical application is not automatically configured to start when the desktop logs in. You may add `backup-interface --background` as an autostart command to your desktop environment's settings. ### **Upgrading** *** The "Other Distribution" version of eazyBackup supports upgrading the software, with some caveats: * The `.run` file will automatically upgrade the existing version * The software can be remotely upgraded via the eazyBackup Server web interface. However, the existing service will only be replaced with the upgraded version if the product brand name is unchanged. Future "Other Distribution" versions of eazyBackup will support upgrading between installations regardless of product brand name. ### **Uninstall** *** To uninstall "Other Distribution" versions of eazyBackup, you should 1. Stop all eazyBackup processes 2. Remove the relevant subdirectory under `/opt/` 3. Remove any custom startup scripts ### **Change password on Linux client** *** Use the 'Change Password' function in the eazyBackup [client area](https://accounts.eazybackup.ca/). Then fully uninstall and reinstall the client, using the new credentials. Your device settings and Protected Items will be preserved. *** [eazyBackup](https://eazybackup.com) # Linux (Red Hat Enterprise Linux (RHEL), CentOS) Install eazyBackup using the "Linux Other distribution" package. For more information, please see the [Linux (Other Distribution)](/documentation/linux-other-distribution) article. {% content-ref url="/pages/Kzm9l3K4VXJbPT2wutwx" %} [Linux (Other Distribution)](/documentation/linux-other-distribution) {% endcontent-ref %} *** [eazyBackup](https://eazybackup.com) # Linux NAS (Synology, QNAP) Install eazyBackup using the "Linux Other distribution" package. For more information, please see the [Linux (Other Distribution)](/documentation/linux-other-distribution) article. {% content-ref url="/pages/Kzm9l3K4VXJbPT2wutwx" %} [Linux (Other Distribution)](/documentation/linux-other-distribution) {% endcontent-ref %} *** [eazyBackup](https://eazybackup.com) # “Application-Aware Writer” Backups VSS is a technology for taking a consistent point-in-time snapshot of a disk volume. A VSS Writer is an extra software plugin that detects when this action is taking place and ensures that application-specific files are in a safe state on disk. eazyBackup's "Application-Aware Writer" feature allows you to invoke a single VSS Writer, or a sub-component of a single VSS Writer, and back up only the files that it was protecting. This is also an important third-party integration point for application vendors. If your third-party application includes a VSS Writer, you can use this Protected Item type to back it up using eazyBackup. Some products that can be backed up with this Protected Item type are: * Oracle DB; * MailStore Server; * Microsoft Dynamics CRM; * Microsoft Sharepoint; * Pervasive PSQL; * other products natively supported by eazyBackup, including Microsoft Exchange Server, Microsoft Hyper-V, and Microsoft SQL Server; * and other products. {% hint style="info" %} **NOTE:** This Protected Item type is intended for integration with specific custom applications. If you want to back up normal files with a VSS snapshot, use the "Files and Folders" Protected Item type with the "take filesystem snapshot" option enabled. {% endhint %} ### Selecting components In eazyBackup, click the Edit button (pencil icon) to browse the available VSS Writers installed on your device. You can select the top-most checkbox to include all components within the VSS Writer, or you can select individual components within the VSS Writer. For instance, the Microsoft SQL Server VSS Writer allows you to select individual databases for backup. The VSS Writer itself may mark some components as non-selectable. This is shown in eazyBackup as a grey subcomponent without a checkbox. ### VSS Mode You can perform the operation in "VSS Full", "VSS Copy", "VSS Incremental", or "VSS Differential" modes. If a specific VSS Writer does not support the selected backup mode, it will perform the backup in "Full" mode. The actual behaviour of these modes is specific to each VSS Writer. For more information, consult the documentation for your VSS Writer. ### Backing up Oracle Database eazyBackup can back up the contents of any installed VSS Writer using the "Application Aware Writer" option. Oracle Database officially supports backup via its installed VSS Writer. You may need to install the Oracle VSS Writer separately. It is available with Oracle Database 11g and later (including 12c and 18c); newer versions of the Oracle VSS Writer can be installed separately to back up a 10g or 9i database. You should use the "Application Aware Writer" option and select the Oracle VSS Writer - ORCL component. Inside this option, you can select individual tablespaces for backup, or select the entire component. The Oracle VSS Writer reads the database with SYSDBA privileges. The Oracle VSS Writer supports log, copy, full, differential, and incremental backups: * if you take "full" or "copy" backups at the VSS component, eazyBackup will deduplicate them together, producing its own incremental backups * if you take "incremental" backups at the VSS component, it may be slightly more space-efficient than eazyBackup's incremental system as Oracle has more specific understanding of the file formats. However, when restoring, you must take care to restore the full backup and all incremental/log backups too, that adds complexity. More information about the Oracle VSS Writer is available in [Oracle's documentation](https://docs.oracle.com/cd/B28359_01/win.111/b32010/vss.htm#NTQRF280). *** [eazyBackup](https://eazybackup.com) # “Microsoft Exchange Server” Backup This Protected Item type backs up Microsoft Exchange Server databases. The underlying technology is VSS and is compatible with Microsoft Exchange Server 2007 and later, including Exchange Server 2016 (the latest version at the time of writing). The appropriate VSS writer must be installed. As Exchange Server can only be installed on Server SKUs of Windows, this backup type is only applicable when running on Windows Server. Some forms of Exchange Server backup will cause log truncation to occur on the Exchange Server. For more information, please see the official Exchange Server documentation. If circular logging is enabled on the Exchange Server, the 'Incremental' and 'Differential' backup types have limited effect. *** [eazyBackup](https://eazybackup.com) # “Microsoft Hyper-V” Backup This Protected Item type backs up Microsoft Hyper-V virtual machines. The underlying technology is VSS and is compatible with all versions of Hyper-V running on Windows Server, including Windows Server 2016 (the latest version at the time of writing). This backup type is only applicable when running on Windows Server. Hyper-V on Windows Desktop is not supported by this Protected item type. eazyBackup integrates with the Hyper-V VSS writer to perform a Hyper-V backup snapshot, including support for in-VM quiescence on supported guest operating systems. Backing up a Hyper-V virtual machine with eazyBackup includes, but is not limited to: * its configuration file * all attached virtual drives * the contents of memory (if the machine was running) * the full tree of saved checkpoints You can select individual virtual machines for backup, or choose "All virtual machines". ### Consistency and guest additions {% hint style="info" %} *The following information applies to all products that perform Hyper-V backup.* {% endhint %} When backing up a guest VM, it's important to get a consistent state of the VM. There are some different ways this happens. If the guest OS has all necessary Hyper-V integration services installed, then the host can request for the guest VM to take a VSS snapshot. The snapshot is then exposed to Hyper-V on the host for eazyBackup to back up. It shouldn't interrupt the guest OS. The VM backup is application-consistent. This is known as a "Production checkpoint". If the host OS is running Server 2012 R2 or newer, but there are no integration services inside the guest OS, then Hyper-V will take a checkpoint of the VM; eazyBackup will back up the checkpoint; and then the checkpoint will be removed. This kind of checkpoint does not interrupt the guest OS. The VM backup is crash-consistent. This is known as a "Standard checkpoint". * You can also achieve this behaviour by disabling "Production checkpoints" in the Hyper-V settings for the VM. If the host OS is older than Server 2012 R2, and there are no integration services inside the guest OS, then the VM will be paused; Windows will take a VSS snapshot of Hyper-V's files in paused state; the VM will be resumed and eazyBackup will back up from the VSS snapshot. It would cause a short interruption to the guest OS. The VM backup is crash-consistent. * You can also achieve this behaviour by disabling checkpoints in the Hyper-V settings for the VM. ### Replica VM *The following information applies to all products that perform Hyper-V backup.* If you are using Hyper-V replication, you can back up your virtual machines from either the primary or replica host. A backup taken on the primary VM host is application-consistent (if possible), by quiescing a VSS snapshot inside the VM guest; or crash-consistent otherwise. However, a backup taken on the secondary VM host is only ever crash-consistent, because the replica VM is not running in order for guest integration services to take a VSS snapshot. Current versions of Hyper-V do not allow backing up a VM that is currently replicating. If a VM is found to be currently replicating at the time of backup, eazyBackup will retry the operation a few times. If you repeatedly see errors of the form The virtual machine '...' cannot start a backup operation because it is currently executing a conflicting operation. Try the backup again., and you are running backups from the replica VM host, you could consider * scheduling the backup job to run at a time when it's more likely that the VM replication is up-to-date; or * using Before / After commands in eazyBackup to temporarily stop VM replication while the backup job is running. > For more information about backing up a replica VM, see:
#### Address
The address is always localhost, but eazyBackup does not use TCP addresses or TCP ports to connect to SQL Server instances. eazyBackup uses "Shared Memory" to connect to SQL Server instances.
eazyBackup's use of "Shared Memory" connection does improves performance for some operations, at the expense of only working on the local machine; but eazyBackup's use of VDI requires it to run against the local machine anyway.
If you encounter issues connecting to your SQL Server, you must ensure that "Shared Memory protocol" is enabled in SQL Server Configuration Manager.
Open Sql Server Configuration Manager -> SQL Server Network Configuration -> Protocols -> Shared Memory -> Enable
| Driver | TLS 1.2 Support | Notes |
| MSOLEDBSQL | Yes | Included with SQL Server 2016 and 2017; Optional download from https://www.microsoft.com/en-us/download/details.aspx?id=56730 |
| SQLNCLI11 | Yes | Included with SQL Server 2012 and 2014; Optional download from https://www.microsoft.com/en-us/download/details.aspx?id=50402 |
| SQLNCLI10 | No | Included with SQL Server 2008 |
| SQLNCLI | No | Included with SQL Server 2005 |
| SQLOLEDB | No | Included with SQL Server (all versions); Included with Windows since XP / Server 2003 |
| eazyBackup Version | Preferred driver | Fallback driver(s) |
| >= 18.9.6, >= 18.8.6 | MSOLEDBSQL | SQLNCLI11, SQLOLEDB |
### Multiple instances
eazyBackup supports backing up multiple instances from SQL Server. You can select an instance for backup, by entering the instance name in the "Instance Name" field. Leave this field blank to use the default instance.
eazyBackup Backup automatically lists available instances for selection in the drop-down menu.
### Backup mode
By default, eazyBackup opts to make a full database export from SQL Server, and then uses its own deduplication system to optimise the stored/uploaded data.
This is the "Full (copy only)" option. It is equivalent to the BACKUP WITH COPY\_ONLY T-SQL statement.
Because eazyBackup can efficiently deduplicate full image backups, it is normally sufficient to only take full backups of SQL Server in eazyBackup.
### Base images
You have the option to use SQL Server's own differential/log backup system. This may be more efficient, but it does require additional administrative work, and complicates the process of restoring data.
The SQL Server maintains one single point-in-time reference, from which it can produce differential backups and/or log-based backups. When you take a new "Full (base image)" backup, the point-in-time reference is moved forward, so that any future differential and/or log-based backups are based on the last base-image backup.
To use SQL Server's own differential/log backup system, you must create multiple Protected Items (each with a different schedule) in order to capture both a base image and a differential/log backups. By creating multiple Protected Items, you can individually schedule, report-on, and manage retention policies for both base and differential/log backups.
If you are using eazyBackup alongside another product for SQL server backups, you should ensure that only one product is taking base-image backups. Otherwise, it's possible that a chain of differential/log backups would be incomplete.
### **Differential**
eazyBackup can use SQL Server's own systems for differential backup. In this mode, you can regularly make "differential base" backups, and then a series of small "differential increment" backups, each containing the difference from the last base backup. These operations are equivalent to the BACKUP and BACKUP WITH DIFFERENTIAL T-SQL statements respectively. eazyBackup will still deduplicate multiple base backups that are sent to the same Storage Vault.
This is the "Differential increment" option.
### **Log**
You can opt to use SQL Server's own systems for log backup. In this mode, you must periodically take full (base image) backups, and regularly take log backups.
You have the choice of whether to apply log truncation. These operations are equivalent to the BACKUP LOG and BACKUP LOG WITH NO\_TRUNCATE T-SQL statements respectively. eazyBackup will still deduplicate all data that is sent to the same Storage Vault.
To use SQL Server's own log system, you must create multiple Protected Items (each with a different schedule) in order to capture both full and log backups.
This mode requires that the database Recovery Model is set to "Full" or "Bulk Logged" in SQL Server. For more information, please see: | Isolation Mode | InnoDB | MyISAM | Detail |
| Transaction | Consistent | Inconsistent | Wrap all read access in a single transaction, so that the read data is consistent |
| Lock tables (default) | Consistent, but slow | Consistent, but slow | Lock access to database before reading it, so that the read data is consistent. This requires that the MySQL user account has been granted the LOCK TABLES permission |
| None | Inconsistent | Inconsistent | Do not take a transaction and do not lock tables. |
| Services | Backup | Restore to Local | Restore to Cloud | Supported | Not Supported |
| Exchange Online | |||||
| Mailbox (Email) | Yes | Yes | Yes | Active users, shared mailboxes | Guest users, Deleted users, Discovery mailbox, Archive mailbox, Journal mailbox, Outlook group mailboxes |
| Calendar | Yes | Yes | Yes | Restore to local:JSON format | |
| Contacts | Yes | Yes | Yes | Restore to local:JSON format | |
| Tasks | No | No | No | ||
| SharePoint Online | |||||
| Sites | Yes | Yes | No | Restore lists, documents and pages individually | |
| Lists | Yes | Yes | Yes | ||
| Pages | Yes | Yes | No | ||
| OneDrive for Business | |||||
| Document Library (Word, Excel, PowerPoint, OneNote) | Yes | Yes | Yes | Displayed under "Documents" in associated SharePoint site | |
| Teams | |||||
| Files | Yes | Yes | Yes | Displayed under "Documents" in associated SharePoint site | |
| Chat | No | No | No | ||
| Calendar | No | No | No | ||
| Meetings | No | No | No | ||
| Call | No | No | No |
* `[datacenter-name]` vm-name to back up a specific VM on a datacenter * `vm-name` to target all matching virtual machines across all datacenters ### Notes For **Changed Block Tracking** and **Standard** mode * Performance is optimized by seeking over unallocated disk sectors. * Data transfer occurs over the NBDSSL protocol. * Separate snapshot files are not included in the backup. Current VM state is flattened in a single disk image. * Disks with independent disk mode is not supported and will be skipped during the backup process. ### Restore eazyBackup can restore the `vmx`, `vmdk`, and other files to the local disk. You must then copy them to the ESXi datastore, and import the VM from the ESXi/vCenter interface. eazybackup also supports restoring directly to the datastore. If backup is made while a VM is running off a snapshot, the resulting disk will be a flattened version of the snapshot branches. Do the following to reimport this virtual machine. * Update VMX config with `scsi0:N.fileName =` * (Optional): Reclaim disk space (`vmkfstools -K` ) to reset unallocated spaces for improved backup performance. If CBT was enabled. It is recommended to disable/restart CBT before the first boot. Granular restore of single files and folders is available for supported filesystems. # Granular Restore eazyBackup supports granular restore to recover individual files and folders from within a virtual disk image. The granular restore feature is available as part of eazyBackup at no additional cost. Compared to an ordinary File and Folder backup, the extra work involved to perform granular extraction of individual files from within a virtual disk image results in a small performance penalty. If you expect to restore individual files regularly, a File and Folder-type Protected Item may offer better performance. We recommend using the latest version of eazyBackup for best performance and compatibility. The available granular restore capabilities do not depend on the backup device's operating system. For example, restoring files from an NTFS image is possible on a macOS device, and restoring files from an EXT4 image is possible on a Windows device. For the following Protected Item types, Granular restore is available as an option during the Restore wizard process: | Protected Item type | Supported | Notes | | ------------------- | --------- | -------------------------------------------------------------- | | Disk Image | Yes | | | Hyper-V | Yes | `vhdx` files only, not `vhd` nor any `avhdx` differencing disk | | VMware vSphere | Yes | | The granular restore feature requires that the virtual disk uses a compatible partitioning scheme: | Disk partition structure | Supported | Notes | | ------------------------ | --------- | ------------------------ | | GPT | Yes | | | MBR | Yes | Including EBR partitions | | Windows Dynamic Disk | Partial | See note 1 | | Windows Storage Spaces | Partial | See note 1 | | Linux LVM2 | Partial | See note 1 | | Linux MD | Partial | See note 1 | {% hint style="info" %} Note 1: The underlying physical format is not supported for granular restore. However in a Disk Image backup, you may have the option to back up either the underlying physical format or the resulting virtual volume. If you back up the resulting volume, it may be supported for granular restore. {% endhint %} The granular restore feature requires that the partition uses a compatible filesystem type: | Filesystem | Supported | Notes | | ---------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | | NTFS | Yes | Advanced metadata and reparse points may not be available. Filesystems using Windows Server Data Deduplication may present files as reparse points. | | FAT | Yes | Filesystem recognition depends on the original format utility used | | EXT4 | Yes | Symlinks are not supported | | XFS | Yes | | | ReFS | No | | | exFAT | No | | ### Alternative solutions If your backup scenario uses an unsupported virtual disk partition type, or an unsupported filesystem type or filesystem feature, granular restore will not be available. In this case you can still achieve granular restore of individual files by first performing a full image restore, and then using a third-party tool to extract individual files from the virtual disk image file. We recommend the following software: #### 7-Zip * Free and Open Source, Windows (GUI) and macOS / Linux (command-line) * Can open VMDK disk descriptor and also the individual extent files * Supports many filesystems, including NTFS, FAT32, EXT 2/3/4, UDF, HFS, SquashFS * Known issues: * When loading the VMDK disk descriptor directly instead of the extent files, if no partition table is present (i.e. "Raw byte range" containing the MBR/GPT area at the start of the disk was not selected for backup) then the descriptor will only show an interior 'disk.img' file instead of partition contents.. You can workaround this issue by opening the individual partition extent files * Early versions of 7-Zip had only limited support for disk image features. Please manually ensure your 7-Zip installation is up-to-date, as 7-Zip does not have a built-in software update feature. #### DiskInternals Linux Reader * Freeware, Windows-only * Despite the product name, also supports Windows filesystems (NTFS, FAT) * Can mount VMDK files as a drive letter from the menu > Drives > Mount Image > "VMware virtual disks (\*.vmdk)" * Known issues: * Fails to open the VMDK disk descriptor if there is junk data in "Raw byte range" areas. You can workaround this issue by editing the descriptor file to replace these with zero extents. e.g. edit disk.vmdk change RW 16065 FLAT "disk-f0000.vmdk" 0 to RW 16065 ZERO #### Passmark OSFMount * Freeware, Windows-only * Can mount VMDK extent files as a drive letter * Known issues: * When loading the VMDK disk descriptor directly instead of the extent files, the disk partitions can be discovered, but mounting fails - both of the individual partitions and also when attempting to mount the VMDK as a raw disk ("Physical Disk Emulation" mode). You can workaround this issue by selecting the individual extent files to mount (works using "Logical Drive Emulation" mode) # How to Set a Storage Vault Quota Setting a storage quota allows you to control storage growth and keep your billing predictable. When a vault reaches its quota limit, **backups will stop automatically** until space is freed or the quota is increased. ### Step 1 — Open the Vault Management Page
**If Step 1 did not resolve the issue, proceed to Step 2.**#### **Step 2:** To clear the lock on the storage vault so new backup jobs can proceed you can run a retention pass on the storage vault. 1. From the Backup Application menu, Click on 'Settings' 2. On the Storage Vaults tab, Right click on the Storage Vault -> Advanced -> Apply retention rules now
To disable this warning, please ensure you have backed up the EFS encryption keys, and then enable the 'I confirm EFS keys are exported' option in the Protected Item settings.
Locate the eazyBackup Delegate and Elevator services.
Select each of the services and click the Restart button in the left side menu.
Verify that the service status shows Running after restarting both the delegate and elevator services.
At this point you should be able to open eazyBackup normally from the start menu shortcut.
***
[eazyBackup](https://eazybackup.com)
# Lstat: CreateFile \\\\?\UNC\ backup: Access is denied.
`Lstat: CreateFile \\?\UNC\ backup: Access is denied.`
When performing a backup of a network location such as a mapped network drive or UNC path you may receive an error message similar to this in your backup logs.
The error message, "`Lstat: CreateFile \?\UNC\Server\Path: Access is denied`," indicates that there was an error while trying to retrieve information about a file or directory located on a UNC (Universal Naming Convention) network path.
This error message could be due to several reasons, such as:
1. Incorrect login credentials: The network login credentials you supplied in the Protected Item to access the network drive may be incorrect, or the account you used may not have sufficient permissions to access the drive.
2. You have not added network credentials in the Protected Item, and the backup service is unable to access the UNC path without your login credentials.
Please see[ our guide](/guides/how-to-backup-windows-network-shares-and-unc-paths) to backing up network shares. There are some important steps you don't want to miss.
{% content-ref url="/pages/CUu86ODkLS7am2p8wn7r" %}
[How to Backup Windows Network Shares and UNC Paths](/guides/how-to-backup-windows-network-shares-and-unc-paths)
{% endcontent-ref %}
Some additional information on the error -> We frequently get asked about the meaning of Lstat and CreateFile:
**Lstat** and **CreateFile** are functions used in the context of accessing files and directories in Windows and Linux operating systems.
In Windows, the CreateFile function is used to create or open a file or device for reading, writing, or other types of operations.
Lstat is a function used in the Linux operating system to retrieve information about a file or directory, such as its type, size, and permissions.
***
[eazyBackup](https://eazybackup.com)
# Mount path conflict: Can’t mount path inside real directory
Backup reports the following error:
```
Invalid path 'C:\example\path\files':
Mount path conflict: Can't mount path 'C:\example\path\files'
inside real directory 'C:\example\'!
```
This issue is caused because both "C:\example\ " and "C:\example\path\files " are included for backup. Because the former (C:\example\\) is included, there's no need to specially include the latter (C:\example\path\files).
A new version of eazyBackup will have a filter to automatically skip this issue.
For now, you can work around this issue in eazyBackup by editing your protected item -> “items” tab, remove the included location "C:\example\\".
Substitute C:\example\ for your own path.
***
[eazyBackup](https://eazybackup.com)
# OneDrive error “The tag present in the reparse point buffer is invalid”
This warning may appear if you are using the OneDrive Files On-demand feature. If you have chosen to backup the contents of your OneDrive folder, the backup client may be trying to backup placeholder junction files/folder kept by the On-demand feature.
The message: "`The tag present in the reparse point buffer is invalid`" indicates that some of those junction files are likely in a damaged state, this could happen if OneDrive had crashed or terminated improperly at some point.
Usually this can be fixed by running chkdsk.exe from an elevated command prompt by running '`chkdsk c: /f`'.
Be aware that running this repair may require a system reboot.
You may also want to [see this article](/documentation/error-access-to-the-cloud-file-is-denied-backing-up-onedrive) to disable the OneDrive Files On-demand feature so that you can backup files stored on OneDrive:
{% content-ref url="/pages/rZuIDgot6cnH6UywoRKl" %}
[Error “Access to the cloud file is denied” backing up OneDrive](/documentation/error-access-to-the-cloud-file-is-denied-backing-up-onedrive)
{% endcontent-ref %}
***
[eazyBackup](https://eazybackup.com)
# Out of memory
eazyBackup needs RAM to run. The main cause for this is to hold deduplication indexes; therefore the amount of RAM used is proportional to the size of the Storage Vault.
You might see these error messages:
> * runtime: VirtualAlloc of 1048576 bytes failed with errno=1455 on Windows
> * 0x5AF ERROR\_COMMITMENT\_LIMIT: The paging file is too small for this operation to complete. on Windows
> * fatal error: out of memory on all platforms
On Linux, when the system is out of memory (OOM), the kernel "OOM Killer" subsystem will immediately terminate a process of its choosing, to free up memory. If you see an error message like signal: killed in eazyBackup on Linux, this means the process was terminated by a user or a subsystem, that might possibly be the OOM Killer. You can check for this in `dmesg` or `kern.log`.
You can reduce eazyBackup's RAM usage by trying to limit how much data is in each Storage Vault. For instance, instead of having multiple devices backing up into a single Storage Vault, create multiple Storage Vaults for each device. This will reduce the deduplication efficiency, but it will also reduce the necessary memory usage.
### **Other Options**
Some trade-offs are possible, that can reduce eazyBackup's memory usage at the expense of other system resource types:
### **Rescan unchanged files**
This option causes eazyBackup to read more data from the source disk, reading less data from the Storage Vault into in-memory indexes. This can have a varied impact on RAM usage, and may be positive or negative depending on the shape of your directories.
### **Prefer temporary files instead of RAM**
The "Prefer temporary files instead of RAM" option on a backup job schedule will cause eazyBackup to keep indexes in an on-disk database file, instead of a pure in-memory index. The on-disk database file is mapped into pageable memory, that can more easily be reclaimed by the OS when the system is under memory pressure.
Depending on how you measure eazyBackup's memory usage, this option may not immediately appear to have lower memory usage if your measurement includes `mmap` disk sections. However, the resident working set is reduced.
There is a major performance penalty for using this option (approximately 5x or worse) and it is not generally recommended.
Follow these steps to enable the "Prefer temporary files instead of RAM" option
* Open the eazyBackup agent
* Select the Protected Item, click 'Configure'
* Select the 'Schedule' tab
* Select and Edit your Schedule
* In the Schedule window, select the Advanced tab
* Enable the Prefer temporary files instead of RAM option
* Save changes
### **Drivers**
Ensure you have the correct drivers installed so that eazyBackup can connect to your database.
`OLE DB` and `ODBC` are data access methods that use pluggable "drivers" / "providers" for connecting to databases like SQL Server. The following drivers for `OLE DB` / `ODBC` support SQL Server:
| Driver | TLS 1.2 Support | Notes |
|---|---|---|
MSOLEDBSQL | Yes | Included with SQL Server 2016 and 2017; Optional download from https://www.microsoft.com/en-us/download/details.aspx?id=56730 |
SQLNCLI11 | Yes | Included with SQL Server 2012 and 2014; Optional download from https://www.microsoft.com/en-us/download/details.aspx?id=50402 |
SQLNCLI10 | No | Included with SQL Server 2008 |
SQLNCLI | No | Included with SQL Server 2005 |
SQLOLEDB | No | Included with SQL Server (all versions); Included with Windows since XP / Server 2003 |
***
[eazyBackup](https://eazybackup.com)
# VSS Error: Device is not ready
The error message indicating "`Device is not ready`" is a VSS snapshot error.
It indicates that the VSS snapshot may have been destroyed while the backup was in progress. VSS snapshots can be destroyed manually by malware, or by ‘cleanup’ type programs. They can also be destroyed if the device is low on disc space, and the device uses space in the ‘shadow’ area where the snapshot is being put together.
#### Suggested solutions are:
* Check if other software is requesting a VSS snapshot operation at the same time as eazyBackup's request for a VSS snapshot.
* Run the backup again to see if the problem still persists - the issue may have been temporary.
* Check the disk space on the device - low disk space is the most cause and is outside of eazyBackup control.
***
[eazyBackup](https://eazybackup.com)
# VSS Error: Couldn’t take snapshot. The shadow copy provider had an unexpected error while trying ...
The VSS Error: `Couldn’t take snapshot. The shadow copy provider had an unexpected error while trying to process the specified operation`
**Common VSS Related Errors:**
`0x800423f4: The writer experienced a non-transient error.`
`0x8004230f: The shadow copy provider had an unexpected error while trying to process the specified operation.`
`0x80042336: The writer experienced a partial failure. Check the component level error state for more information.`
### Suggestions:
1. Start by checking the VSS shadow storage size available on your hard drives.
* Open an elevated command prompt or PowerShell
* Run the following command to check the current usage:
```
vssadmin list shadowstorage
```
In the list of services, locate the eazyBackup Delegate service. Double click to open.
From the Log On tab, you will need to change the 'This account' user from eazybackup.delegate to an admin user that has read permission to your selected files.
Enter the password for your admin account, press OK to confirm the changes.
Restart the service for your changes to take effect.
***
[eazyBackup](https://eazybackup.com)
# Error “local error: tls: record overflow”
This message means the connection was corrupted over the network, and eazyBackup aborted the connection.
This can happen because of random network conditions. Retrying the operation should fix the issue.
If the issue keeps happening repeatedly, this message indicates that something is interfering with packets in your network.
* Failing NIC
* Bad NIC driver or driver configuration
* Failing RAM, on either the endpoint machine or any of the intermediate routers
* Outdated firewall or proxy, performing incorrect SSL interception
For more information, please see the record\_overflow section in [IETF RFC 5246](https://tools.ietf.org/html/rfc5246#page-31).
***
[eazyBackup](https://eazybackup.com)
# Microsoft SQL Server backup encountered a VDI error
You should ensure that the necessary VDI `.dll` files are registered and are the correct version for your SQL Server installation. You can use [Microsoft SQL Server Backup Simulator](https://github.com/Microsoft/tigertoolbox/releases/) to check the status of the VDI `.dll` files.
***
[eazyBackup](https://eazybackup.com)
# Troubleshooting Network Connectivity Errors
### Overview
eazyBackup transfers your data to your Storage Vault over an encrypted HTTPS connection. During a backup, the agent opens multiple parallel connections to eazyBackup's servers and keeps them open for the duration of the job. If anything on the path between your device and our servers interrupts those connections — a firewall, a security appliance, an unstable internet link, or a DNS problem — the backup job will fail with a network connectivity error.
This article explains what these errors mean, how to narrow down where the problem is occurring, and how to resolve the most common causes.
### Common Error Messages
You may see one or more of the following messages in your backup job log:
| Error message | What it usually indicates |
| ------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `wsarecv: An existing connection was forcibly closed by the remote host` | An open connection was terminated mid-transfer by a device between you and eazyBackup — commonly a firewall/UTM appliance, a multi-WAN router switching internet links, or an unstable connection. |
| `wsasend: ...` | Same as above, but the interruption occurred while sending data. |
| `tls: failed to verify certificate: x509: certificate signed by unknown authority` | A firewall or security appliance on your network is performing SSL/TLS inspection and replacing eazyBackup's certificate with its own. See SSL/TLS Inspection below. |
| `dial tcp: lookup [...]: no such host` | DNS failure — your device could not resolve the eazyBackup server hostname to an IP address. |
| `connectex: A connection attempt failed because the connected party did not properly respond...` | The connection to the server could not be established at all — typically a firewall block, an outbound port restriction, or an internet outage. |
| `net/http: request canceled (Client.Timeout exceeded while awaiting headers)` | The server did not respond in time — often caused by severe packet loss, a saturated internet connection, or a proxy delaying traffic. |
| `Couldn't save data chunk: context canceled` | A follow-on message: after one upload thread fails, the agent cancels the remaining threads. Look earlier in the log for the original error. |
| `HTTP/1.x transport connection broken` | An established connection was dropped mid-request by a device on the network path. |
The agent automatically retries failed transfers several times before giving up, so a single error in a log does not always mean the job failed — check the final job status.
### eazyBackup Service Endpoints
Your device must be able to reach the following endpoints outbound on **TCP port 443 (HTTPS/TLS)**. No other ports or protocols are required.
| Hostname | IP address | Port |
| -------------------------------- | ------------- | ------- |
| `csw.eazybackup.ca` | 45.45.161.146 | TCP 443 |
| `csw.obcbackup.com` | 45.45.161.146 | TCP 443 |
| `s3.ca-central-1.eazybackup.com` | 45.45.161.149 | TCP 443 |
If your firewall supports it, whitelist by **hostname**; otherwise, allow outbound TCP 443 to **45.45.161.146**. and **45.45.161.149**
***
### Quick Checks First
Before deeper troubleshooting, try these steps — they resolve a large percentage of network errors:
1. **Retry the backup.** Many network errors are temporary. A repeated backup job will also usually run faster, because data chunks that were already uploaded do not need to be sent again. (Any unused chunks left behind by a failed job are cleaned up automatically by the next retention pass.)
2. **Reboot your router/modem.** Consumer and small-business routers can run out of resources when handling a large number of simultaneous connections. A reboot clears the connection table.
3. **Check whether the error occurs at a consistent time of day.** If backups only fail during business hours or during known heavy-usage periods, your internet connection may be congested. Try rescheduling the backup to a quieter time.
4. **Check for recent network changes.** New firewall, new ISP, new security software, or a firmware update on a UTM appliance immediately before the errors began is a strong lead.
If the problem persists, work through the steps below to narrow down where the connection is failing.
***
### Step 1: Check Your Device Status in the Client Area
Log in to the client area at [https://accounts.eazybackup.ca](https://accounts.eazybackup.ca/) and open the **Dashboard**:
**
**Ctrl+Shift+Enter** to run the command as an administrator
In your command window, move to the root of your system drive.
Type the command:
```
cd\
```
Once you are at C:\ you can run the cipher utility with the following command.
```
cipher /u /n /h
```
This command will generate a list of all of the EFS encrypted files. The search process is recursive so it will look through sub-directories as well. We are including the /n switch to prevent cipher from triggering an update on the file which means that it will not try to use or renew the EFS certificate on the file. This is important where you may not have permissions to currently access the files but only traverse directory permissions.
When the process is complete, Cipher will display a list of encrypted files with their locations.
If there are no files listed as shown in the example above, you do not have any EFS encrypted files on your system drive.
### Disable EFS via Group Policy
If you want to prevent any new EFS encrypted files from appearing, you can easily do this with Group Policy editor.
Press Windows+R to open the “Run” box. Type “`gpedit.msc`” and press enter.
In the Group Policy Editor navigate to
```
Computer Configuration > Windows Settings > Security Settings > Public Key Policies
```
Right-click on the **Encrypting File System** folder in the left side navigation area. Select **Properties** and In the EFS Properties window choose "**Don't allow**", Click OK. This will disable the ability for users to use EFS.
***
[eazyBackup](https://eazybackup.com)
# Couldn’t save folder details: fs.TempFile: Access is denied
This error is likely related to the eazyBackup delegate service user having insufficient permissions to to access one of the default temp folder locations.
You will need to switch the eazybackup.delegate service user on this device to use the local system account, or another Windows user of your choice, such as your own account.
* Open Windows Services: Press the Windows Key + R
* In the Run dialog box type `Services.msc`, press enter
* In the list of Windows Services, locate eazyBackup.Delegate
* Right click on the eazyBackup.Delegate service, select properties
* Click on the Log On tab
* Select Log on as: Local System account - or another Windows user of your choice
* Click OK
* Right click on the eazyBackup.Delegate, select Restart
* Run a backup to confirm the issue is resolved
***
[eazyBackup](https://eazybackup.com)
---
[Next Page](/llms-full.txt/1)