DSE Backup Expert Pro Help
DSE Backup Expert Pro is a professional backup and restore application, that covers a very broad range of backup needs, from a few files to entire physical hard drives.
DSE Backup Expert Pro is available in multiple flavors, for both Windows 10 and Windows Server, and it is also available in the Microsoft Store. It supports both perpetual (for life) licenses, and subscription licenses.
A backup action involves three elements:
The source: the data that needs to be backed up.
The target: the location where the data is backed up.
The intermediary: the backup application (DSE Backup Expert Pro) that transfers the data from the source to the target.
When running as a normal user, DSE Backup Expert Pro can backup data from these sources:
Individual files & folders, from the local computer or from the network.
File & folders' attributes.
File & folders' timestamps.
When running as an administrator, DSE Backup Expert Pro can also backup data from these sources:
File & folders' access rights.
Encrypted (EFS) files' raw data, without needing the encryption certificate, and without actually seeing the actual unencrypted contents.
Entire volumes (a.k.a. drives), sector by sector, including shadow copies created by Windows Volume Shadow Copy Service.
BitLocker encrypted volumes' raw data, sector by sector, without needing the encryption key, and without actually seeing the actual unencrypted contents.
Entire physical drives (HDDs, SSDs or SSHDs).
Note: When running as an administrator, DSE Backup Expert Pro can also copy an entire volume or physical drive directly to another volume or physical drive. Go to the Copy & Restore page if you want to do this.
When running as a normal user, DSE Backup Expert Pro can backup data to these targets:
Local file system, including external drives.
Network shares.
FTP servers.
SFTP servers.
Amazon Web Services (AWS) S3 buckets.
Microsoft Azure blob containers.
Microsoft Azure file shares.
Or it can send (small) backups as email attachments.
When running as an administrator, DSE Backup Expert Pro can also backup data directly to volumes and physical drives.
Additionally, DSE Backup Expert Pro offers these features:
Recognizes external volumes and drives even when Windows assigns them different letters every time they are connected. This way, a user can configure a backup task to save data to an external drive that does not get assigned the same letter every time.
Using the "Predefined Lists" feature, a user can easily configure and run backup tasks that backup files from hundreds of computers in the local network.
Schedule backup tasks to run at certain times, or even repeatedly, for certain time intervals.
Custom encryption using the AES family of encryption algorithms.
Define complex selections of files, using additive and subtractive paths.
Backup data to multiple targets in a single step. This way, an entire hard disk can be read only once, and saved to (for example) an AWS S3 bucket, a network share and an SFTP sever at the same time.
Perform custom actions before and after backup tasks.
Wait & retry when it cannot open a file. For example, if the user is saving a .txt file exactly when DSE Backup Expert Pro is trying to read it, DSE Backup Expert Pro will wait a few milliseconds and will try again.
Selective restore of files' contents and metadata. This way, a user can choose to restore only the files' contents, or only the files' access rights, or only the files' contents and the Owner security attribute, or any other combination.
For practical examples of using DSE Backup Expert Pro, see the Common Usage Scenarios section below.
A file with extension .bakex-rawf is created by DSE Backup Expert Pro for every original file when the user chooses to backup more than the contents of files.
A .bakex-rawf file contains a user selection of the following:
The original file's contents.
The original file's raw encrypted data (for EFS encrypted files).
The original file's security attributes:
The original file's Owner security attribute.
The original file's Group security attribute.
The original file's DACL security attribute.
The original file's SACL security attribute.
The original file's attributes:
The original file's Read-Only (R) attribute.
The original file's Hidden (H) attribute.
The original file's System (S) attribute.
The original file's Archive (A) attribute.
The original file's Not-Index (N) attribute.
The original file's Encrypted (E) attribute.
The original file's Compressed (C) attribute.
The original file's timestamps:
The original file's Created timestamp.
The original file's Las accessed timestamp.
The original file's Last write timestamp.
All these are optional. A user may choose to only backup the file rights and attributes, but not the file contents, if he or she so wishes.
It is not possible to back up both a file contents and the file's raw encrypted data at the same time.
A file with extension .bakex-rawd is created by DSE Backup Expert Pro for every original folder when the user chooses to backup additional information about folders.
A .bakex-rawd file is very similar to a .bakex-rawf file, except it does not contain the original folder's contents, or the original folder's raw encrypted data (because there is no such thing).
When restoring data from .bakex-rawf and .bakex-rawd files, a user can select to restore any combination of the above (which may or may not include the file contents). For example, a user may choose to restore only the files' access rights, skipping the files' contents.
Obviously, only data that was included in the .bakex-rawf and .bakex-rawd files can be restored. If the .bakex-rawf and .bakex-rawd files were created at backup time without the access rights information, then the access rights cannot be restored.
In order to use correctly the backup features related to volumes and drives, one must understand correctly the terminology.
A physical drive is an electro-mechanic (HDD), electronic (SSD) or hybrid (SSHD) physical device.
Such a physical drive is devided into one or more partitions.
One or more such partitions (from one or more physical drives) are mounted by Windows as a volume, and assigned a "drive" letter (e.g. C:\, D:\, etc...).
In most case, a volume occupies a single partition, but this is not always the case! A user can select multiple unmounted partitions on multiple physical drives and create a single volume (e.g. D:\) out of them.
In order to avoid confusions, please keep in mind that a volume (sometimes called a Windows drive) is not always equivalent to a single partition and sometimes it may be hosted on more than one physical drive.
DSE Backup Expert Pro can backup volumes in four different ways:
As logical volumes, using the <LogicalVolumeByLetter:>, <LogicalVolumeByLabel:> and <LogicalVolumeByFolder:> tags.
As extended logical volumes, using the <LogicalVolumeExByLetter:>, <LogicalVolumeExByLabel:> and <LogicalVolumeExByFolder:> tags.
As physical volumes, using the <PhysicalVolumeByLetter:>, <PhysicalVolumeByLabel:> and <PhysicalVolumeByFolder:> tags.
As Volume Shadow Copies, using the <VscOfVolumeByLetter:>, <VscOfVolumeByLabel:> and <VscOfVolumeByFolder:> tags.
Source or file image | Can be copied (or restored) to |
---|---|
Logical volume | A logical volume of the same size |
Shadow copy | A logical volume of the same size |
Extended logical volume | An extended logical volume of the same size |
Physical volume | A physical volume of the same size |
Physical drive | A physical drive of the same size |
A volume shadow copy is a sector-by-sector, consistent and read-only replica of the original volume.
Shadow copies can only be created for volumes for which System Protection is activated (in Windows).
Shadow copies can be used to take consistent sector-by-sector snapshots of volumes that are in use, including the system volume (where Windows boots from).
WARNING: On 64 bit Windows you need to run the 64 bit edition of DSE Backup Expert Pro in order for all features to work correctly. If you run 32 bit DSE Backup Expert Pro on 64 bit Windows, the features related to Volume Shadow Copy may not work correctly. This is not a problem when running 32 bit DSE Backup Expert Pro on 32 bit Windows, or when running 64 bit DSE Backup Expert Pro on 64 bit Windows, but only when the 32 bit app runs on a 64 bit operating system (because Volume Shadow Copy Service is not fully accessible from WoW64).
A logical volume and all of its shadow copies are compatible and of the same size.
A logical volume can be restored using an image of its shadow copy.
An extended logical volume is a logical volume with a few extra sectors (usually about 4,096 more bytes).
Features related to extended logical volumes are meant to be used only by advanced users, who really understand what the extra data is. Otherwise, data on the physical drive can be permanently destroyed.
A physical volume refers to the actual data stored on the magnetic or electronic support.
If the volume is not encrypted at the sector level (e.g. with BitLocker), then there is no difference between the extended logical volume and the physical volume.
If the volume is encrypted at the sector level (e.g. with BitLocker), than the extended logical volume refers to the clear (unencrypted) data, and the physical volume refers to the encrypted data.
A physical drive can be backed up using the <PhysicalDriveByIndex:>, <PhysicalDriveByLetter:>, <PhysicalDriveByLabel:> and <PhysicalDriveByFolder:> tags.
When defining the backup task source, just enter any of the above tags instead of the source path, alone. You can use the ... menu right next to the source edit box.
The target can be anything, a local folder, a cloud location, or even another volume or drive.
When defining the backup task target, just enter any of the above tags instead of the target path, alone, also check Target is a single file option. You can use the ... menu right next to the source edit box.
The source can be a local file or another volume or drive.
Go to the Copy & Restore page.
Browse and select a file containing a matching image.
Press F5.
Replace the text in the target field with a tag designating the target volume or drive, for example <LogicalVolumeByLetter: D>.
Click Copy.
Go to the Copy & Restore page.
Select a file (any file, it doesn't matter).
Press F5.
Replace the text in the source field with a tag designating the source volume or drive, for example <LogicalVolumeExByLetter: G>.
Replace the text in the target field with a tag designating the target volume or drive, for example <LogicalVolumeExByLetter: D>.
Select any overwrite policy other than "Do Not Overwrite".
Click Copy.
WARNING #1: Make sure to only copy logical volumes to logical volumes, physical volumes to physical volumes, etc. A shadow copy can only be copied to a logical volume.
WARNING #2: Make sure the target is of exactly the same size as the source. Sometimes it may seem to work if the target is larger or smaller, but this may not always be the case.
WARNING #3: A physical drive contains a partition table, where each partition is identified by a unique GUID. Creating clones of a physical drive will result in multiple partitions with the same GUID, which can lead to unpredictable behavior. If you really need to create such clones, make sure you shut down your computer immediately after that, and remove one of the physical drives.
A logical volume's image should only be copied to a logical volume of (at least) the same size!
An extended logical volume's image should only be copied to an extended logical volume of (at least) the same size!
A physical volume's image should only be copied to a physical volume of (at least) the same size!
A logical volume's shadow copy image should only be copied to a logical volume of (at least) the same size!
A physical drive's image should only be copied to a physical drive of (at least) the same size!
Make sure type of volume and drive images match the type of target (destination) they are copied to (e.g. logical volumes to logical volumes, etc.)! Volume shadow copies can be copied only to logical volumes.
When entering the path of a source or a target, DSE Backup Expert Pro accepts various tags that can be helpful to refer to volumes, drives, lists of computer names, local date and time, etc.
For example:
The <LogicalVolumeBy*:> tags can be used to specify logical volumes (by letter, by label or by root directory).
The <Utc*:> tags can be used to specify UTC date, year, month, etc...
The <WfDocuments:> tag can be used to specify the current user's Documents folder.
For a complete list of tags, with detailed explanations and usage examples, see the Tags Reference section below.
The list: tag element is an incredible powerful way to build complex selection of files.
For example, if you define a list named MyComps containing the names (or the IPs) of all the computers in your local network, then you can very easily create a backup task source that will include all files in all Desktop folders of all users on all computers in your local network:
For Source root folder enter \\<list: MyComps>\C$\Users\*.*\Desktop.
For File patterns enter *.*.
Obviously, you need to be a domain admin in order to use such a task source.
For more details, check out the list: tag element and this usage scenario.
DSE Backup Expert Pro can produce files with these extensions:
.bakex-encd is a file encrypted by DSE Backup Expert Pro.
.bakex-decd is the default extension of a decrypted file, when no other extension is available.
.bakex-rawf is a file that contains a source file's contents, attributes, timestamps and access rights. Such a file can be used to restore a file's contents and properties.
.bakex-rawd is a file that contains a source folder's attributes, timestamps and access rights. Such a file can be used to restore a folder's properties.
.bakex-vol is a file that contains the image of a logical volume. Such a file can be used to restore a logical volume.
.bakex-vol-ex is a file that contains the image of an extended logical volume. Such a file can be used to restore an extended logical volume.
.bakex-vol-vss is a file that contains the image of a shadow copy of a logical volume. Such a file can be used to restore a logical volume.
.bakex-vol-ph is a file that contains the image of a physical volume. Such a file can be used to restore a physical volume.
.bakex-drv-ph is a file that contains the image of a physical drive. Such a file can be used to restore a physical drive.
Main app license |
One is mandatory! The app won't run without a valid one. Available in both subscription and perpetual (for life) licensing models. Can be acquired from the Microsoft Store or from our website. SOURCES:
TARGETS:
|
Net Admin licenses |
They are optional. The app can run without a valid one, but it won't be able to access network sources in backup tasks (only in the Copy & Restore page). Available in both subscription and perpetual (for life) licensing models. |
App flavor |
Where to buy |
License lifespan |
License features |
---|---|---|---|
DSE Backup Expert Pro |
Subscription (yearly or monthly) |
Managed by Windows (acquired through the Microsoft Store application) Application updates will include all bug fixes, all new features, and all new major versions. |
|
DSE Backup Expert Pro 2021 |
Perpetual (for life) |
Managed by Windows (acquired through the Microsoft Store application) Application updates will only include bug fixes, and only till January 1st, 2026. Application updates will not include new features and new major versions. The license never expires. |
|
DSE Backup Expert Pro Desktop |
Our website |
Subscription |
.nmssl file(s) saved in the Nmssl subfolder in the app's installation directory. Application updates will include all bug fixes, all new features, and all new major versions. The license is only valid for a limited time, and it expires after that time passes by. |
Perpetual (for life) |
.nmssl file(s) saved in the Nmssl subfolder in the app's installation directory. Application updates will only include bug fixes, and only for about 5 years. Application updates will not include new features and new major versions. The license expires in about 1,000 (one thousand) years. |
||
DSE Backup Expert Pro Server |
Our website |
Subscription |
.nmssl file(s) saved in the Nmssl subfolder in the app's installation directory. Application updates will include all bug fixes, all new features, and all new major versions. The license is only valid for a limited time, and it expires after that time passes by. |
Perpetual (for life) |
.nmssl file(s) saved in the Nmssl subfolder in the app's installation directory. Application updates will only include bug fixes, and only for about 5 years. Application updates will not include new features and new major versions. The license expires in about 1,000 (one thousand) years. |
The DSE Backup Expert Pro Server flavor is meant to be used only on the Windows Server line of operating systems.
All flavors have the full set of features, with the exception of DSE Backup Expert Pro Server, which lacks these Windows 10 specific features:
It cannot display toast notifications.
Its UI cannot mimic the Windows theme (it only works with the light or dark theme).
It cannot have a jump list (with task shortcuts).
Note:
The DSE Backup Expert Pro MS Store app is free, but it won't work unless you also acquire one of these two subscriptions:
If you need to backup files and folders from other computers in your network, you don't have to buy additional DSE Backup Expert Pro licenses. Usually, all you need is to acquire Backup Expert Net Admin licenses, and they will allow your copy of DSE Backup Expert Pro running on one computer to backup files and folders from many other computers in the network.
It is about five times cheaper to acquire Net Admin licenses than buying additional DSE Backup Expert Pro licenses that would run on the other computers.
In many countries, subscription-based Net Admin licenses cost less than five percent of the electricity consumed by those computers.
Net Admin license files have to be installed on the same computer where the main app (DSE Backup Expert Pro) is installed, in the Nmssl subfolder, in the app's installation folder.
Net Admin licenses regulate only the number of network SOURCES you can use, not the number of network TARGETS, which is always unlimited.
Therefore, you can backup your data to an unlimited number of targets in your network, regardless of the Net Admin licenses you may or may not have.
Net Admin licenses regulate only the number of network SOURCES you can use in backup tasks, not the number of network SOURCES and TARGETS you use in the Copy & Restore page, which is always unlimited.
Therefore, in the Copy & Restore page, you can manually copy your data from an unlimited number of sources in your network, and to an unlimited number of targets in your network, regardless of the Net Admin licenses you may or may not have.
Net Admin licenses are additive.
For example, if you have a Net Admin 10 and a Net Admin 20, then you can backup files from 30 additional computers in your network.
Do Net Admin licenses allow me to backup volumes and physical drives from other computers in the network?
Not yet, this is not supported at this moment, but it will be supported in the next version of DSE Backup Expert Pro, and all non-expired Net Admin licenses will allow the use of this new feature at no extra cost.
A free module, called DSE Backup Expert Pro Agent is in development phase, and when it will be released, it will enable DSE Backup Expert Pro to access volumes and drives on computers running the Agent (not only in the local network, but on any accessible computer in the internet).
Do Net Admin licenses allow me to backup shadow copies of logical volumes from other computers in the network?
Yes, this should be supported now if your Windows installation and network configuration permit it. At this moment, the VscOfVolumeByLetter: tag element is the only way to do this, and it has to be used this way:
<VscOfVolumeByLetter: COMPUTER_NAME/LETTER> (e.g. <VscOfVolumeByLetter: OTHER_PC/D>).
However, please be aware that this may only be working in certain configurations of the Windows operating system. Check Microsoft Windows documentation for more details about when it is possible to access Volume Shadow Copies on remote computers.
Can Net Admin licenses acquired from the Microsoft Store be reused?
Net Admin licenses acquired from the Microsoft Store can only be used for the Microsoft Store app they were acquired for!
Therefore, please be aware that perpetual Net Admin licenses acquired for DSE Backup Expert Pro 2021 will not be transferrable to DSE Backup Expert Pro 2022.
Therefore, it is advisable to buy perpetual Net Admin licenses from the Microsoft Store only for the subscription-based app (DSE Backup Expert Pro). For the perpetual app (DSE Backup Expert Pro 2021) you can buy subscription based Net Admin licenses.
Can Net Admin licenses acquired from our website be reused?
Net Admin licenses acquired from our website can be transferred and reused when upgrading DSE Backup Expert Pro Desktop or Server.
All licenses that have not yet expired can be copied into the Nmssl subfolder of the new app's installation folder.
So when you're upgrading from DSE Backup Expert Pro 2021 to DSE Backup Expert Pro 2022, if your old (but un-expired) license file includes Net Admin licenses, copy it in the same folder with the new license, and the Net Admin licenses will be recognized.
Net Admin licenses acquired from our website cannot be used with the Microsoft Store editions of DSE Backup Expert Pro.
App flavor |
Net Admin license seller |
---|---|
DSE Backup Expert Pro |
Can be acquired from the Microsoft Store:
|
DSE Backup Expert Pro 2021 |
Can be acquired from the Microsoft Store:
|
DSE Backup Expert Pro Desktop |
When you acquire your main DSE Backup Expert Pro license, you can also include in it any number of Net Admin licenses you want. Also, you can acquire additional Net Admin licenses from our website afterwards (specify 0 main app licenses, and a non-zero Net Admin licenses). All license files (which are additive) should be copied to the Nmssl subfolder in the app's installation directory (e.g. C:\Progam Files\DSE Backup Expert Pro\Nmssl). |
DSE Backup Expert Pro Server |
When you acquire your main DSE Backup Expert Pro license, you can also include in it any number of Net Admin licenses you want. Also, you can acquire additional Net Admin licenses from our website afterwards (specify 0 main app licenses, and a non-zero Net Admin licenses). All license files (which are additive) should be copied to the Nmssl subfolder in the app's installation directory (e.g. C:\Progam Files\DSE Backup Expert Pro\Nmssl). |
Objective: Backup all *.doc and *.docx files under C:\MyDocs to F:\MyBackups\[current time].zip, where F: is an external drive whose letter might change to G: or H: the next time it is connected to the computer.
Prerequisites: Even if the drive's letter might change, DSE Backup Expert Pro can still uniquely identify it if it has a unique name (label) at the time the backup task runs. For this example, let's say the drive's label is MY-DRIVE.
Note that if you have two (or more) drives with the same label, and you connect both of them to the computer at the same time, the backup task won't run anymore because the app won't be able to uniquely identify the external drive.
Go to Backup Tasks and click Add new task
For Unique task name enter a descriptive name that contains only English letters, digits, dashes ('-'), periods ('.') and underscore ('_').
Under Task sources, click Add new source
For Source root folder enter C:\MyDocs.
For File patterns enter *.doc|*.docx.
Under Task targets, click Add new target
Check option Target will be compressed by DSE Backup Expert Pro.
For Target type select Copy to the file system.
For Target folder enter <RootOfVolumeByLabel: MyDrive>\MyBackups.
For Target file name enter <LocalDate:>.zip.
Objective: Backup all *.jpg and *.jpeg files under C:\MyPics to a Microsoft Azure storage account.
Go to the Microsoft Azure portal and create a storage account, then a file share or a blob container.
WARNING: Please be aware that item names in Azure blob containers are case sensitive (unlike item names in file shares)!
Go to Microsoft Azure Storage and click Add new Microsoft Azure Storage account
For Unique Azure Storage name enter a descriptive name that contains only English letters, digits, dashes ('-'), periods ('.') and underscore ('_').
For Microsoft Azure Storage account name enter the name of the storage account exactly as it appears in the Microsoft Azure portal.
For Key name select either key1, key2, or leave it blank.
For Key copy and paste the corresponding key value from the Microsoft Azure portal. For example, if you selected key1 above, copy & paste the Key1 value.
For Share name or Blob container name enter the name of the file share or blob container exactly as it appears in the Microsoft Azure portal.
If you created a blob container (not a file share), then check the This is actually a blob container, not a file share option.
Go to Backup Tasks and click Add new task
For Unique task name enter a descriptive name that contains only English letters, digits, dashes ('-'), periods ('.') and underscore ('_').
Under Task sources, click Add new source
For Source root folder enter C:\MyPics.
For File patterns enter *.jpg|*.jpeg.
Under Task targets, click Add new target
For Target type select Upload to a Microsoft Azure share or blob.
For Select Azure Storage select the storage account created above.
If you want the files to go into a specific subfolder, enter it in the Target subfolder field. Otherwise, leave it blank and the files will go into the root of the file share or blob container.
Objective: Backup all files under the Documents subfolders of all users on all computers in your network to this location: \\Server\BackupsShare\docs-[current time].zip
Prerequisites: License to run DSE Backup Expert Pro on a single computer, and Net Admin licenses for at least 50 computers (see licensing options).
Go to Predefined Lists and click Add new predefined list
For Unique list name enter a descriptive name that contains only English letters, digits, dashes ('-'), periods ('.') and underscore ('_'). For this example, let's name the list AllComputers.
In the Item value field enter the name (or the IP) of a computer in your network, then click the Add as a new item button.
Repeat previous step till all computers in your network have been added to the list.
Go to Backup Tasks and click Add new task
For Unique task name enter a descriptive name that contains only English letters, digits, dashes ('-'), periods ('.') and underscore ('_').
Under Task sources, click Add new source
For Source root folder enter \\<list: AllComputers>\C$\Users\*.*\Documents. This will be resolved to all Documents folders for all users on all computers whose names (or IPs) you entered in the AllComputers list.
For File patterns enter *.*.
Under Task targets, click Add new target
Check option Target will be compressed by DSE Backup Expert Pro.
For Target type select Copy to the file system.
For Target folder enter \\Server\BackupsShare.
For Target file name enter docs-<LocalDate:>.zip.
Objective: Backup all files under D:\MyFiles to the \\MyServer\backups\[current time] folder.
Go to Backup Tasks and click Add new task
For Unique task name enter a descriptive name that contains only English letters, digits, dashes ('-'), periods ('.') and underscore ('_').
Under Task sources, click Add new source
For Source root folder enter D:\MyFiles.
For File patterns enter *.*.
Expand the Select which information you want to back up for files dropdown and select Custom selection.
Select additional metadata you want to backup (access rights, attributes, timestamps). Note that if you select access rights, you need to run the app with elevated privilleges (run as administrator).
Under Task targets, click Add new target
For Target type select Copy to the file system.
For Target folder enter \\MyServer\backups\<LocalDate:>.
Objective: Backup the entire D: drive to an AWS S3 bucket.
Go to the Amazon Web Services (AWS) portal and create an S3 bucket.
Go to AWS S3 Buckets and click Add new AWS S3 Bucket
For Unique AWS S3 Bucket name enter a descriptive name that contains only English letters, digits, dashes ('-'), periods ('.') and underscore ('_').
For Access key ID select key ID, exactly as it appears in the AWS portal.
For Access key secret copy and paste the corresponding key secret from the AWS portal.
For AWS region select the region where the S3 Bucket is located.
For Bucket name select or enter the name of the S3 Bucket.
Go to Backup Tasks and click Add new task
For Unique task name enter a descriptive name that contains only English letters, digits, dashes ('-'), periods ('.') and underscore ('_').
Under Task sources, click Add new source
For Source root folder enter <LogicalVolumeByLetter: D> (you can select this value from the helper menu on the right).
Leave File patterns blank.
Under Task targets, click Add new target
For Target type select Upload to an AWS S3 bucket.
For Select AWS S3 bucket select the bucket created above.
If you want the resulted file to go into a specific subfolder, enter it in the Target subfolder field. Otherwise, leave it blank and the file will go into the root of the bucket.
Check the Target is a single file option. Otherwise, the resulted file will be created with the default name and extension.
For Target file name enter drive-d-<LocalDate:>.bakex-vol.
Objective: Backup the entire physical hard disk that contains the volumes E: and F: to the myftp.mydomain.com FTP server.
Go to FTP Servers and click Add new FTP Server
For Unique FTP server name enter a descriptive name that contains only English letters, digits, dashes ('-'), periods ('.') and underscore ('_').
For Server url or ip enter myftp.mydomain.com.
For Port enter 22.
For Username enter a user name that has the right to upload files to that server.
For Password enter that user's password.
The Passive mode option should be on by default.
If possible, check the Encrypted connection option. This is the safest way to upload files.
Unless you're absolutely sure you're only uploading ASCII files, check the Binary mode option.
Go to Backup Tasks and click Add new task
For Unique task name enter a descriptive name that contains only English letters, digits, dashes ('-'), periods ('.') and underscore ('_').
Under Task sources, click Add new source
For Source root folder enter <PhysicalDriveByLetter: E> (you can select this value from the helper menu on the right). This will get resolved to the physical drive with index 1 if the drive E: is located on the second physical hard disk (physical drive indices are zero-based).
Leave File patterns blank.
Under Task targets, click Add new target
For Target type select Upload to an FTP server.
For Select FTP server select the server created above.
If you want the resulted file to go into a specific subfolder, enter it in the Target subfolder field. Otherwise, leave it blank and the file will go into the root of the FTP server folder.
Check the Target is a single file option. Otherwise, the resulted file will be created with the default name and extension.
For Target file name enter hdd-1-<LocalDate:>.bakex-drv-ph.
Objective: Copy the entire D: logical volume to \\backups\share\MyD-2020-11-28.bakex-vol.
Close all applications that may be using volume D:.
Go to the Copy & Restore page.
Select any file in the left panel.
Select the network path \\backups\share in the right panel.
Go to the left panel and press F5.
In the Source field enter <LogicalVolumeByLetter: D> (you can select this value from the helper menu on the right).
In the Target field enter \\backups\share\MyD-2020-11-28.bakex-vol.
Click Copy.
Objective: Restore the entire physical hard disk at index 1 from the image file \\backups\share\hdd-1.bakex-drv-ph.
Close all applications that may be using physical drive 1.
Go to the Copy & Restore page.
Select the file \\backups\share\hdd-1.bakex-drv-ph in the left panel.
Select any file in the right panel.
Go to the left panel and press F5.
In the Target field enter <PhysicalDriveByIndex: 1> (you can select this value from the helper menu on the right).
Click Copy.
Objective: Copy the entire logical volume E: to the logical volume F:.
Prerequisites: Target volume F: must be of equal (or greater) size than source volume E:.
Close all applications that may be using logical volumes E: and F:.
Go to the Copy & Restore page.
Select any files in the left and right panel.
Go to the left panel and press F5.
In the Source field enter <LogicalVolumeByLetter: E> (you can select this value from the helper menu on the right).
In the Target field enter <LogicalVolumeByLetter: F> (you can select this value from the helper menu on the right).
Click Copy.
Tags are a very powerful way of controlling and enhancing the input (the sources) and the output (the targets) of a backup task. Tags can be used in both file and folder patterns.
A tag starts with the < (less than) character and ends with the > (greater than) character. It can contain more elements, separated by the | (vertical bar) character.
A tag can cause a file or folder pattern to resolve to more than one result, usually one for each tag element (with the exception of the list tag element, which itself alone can produce multiple results). Therefore, tags that resolve to more than one result can only be used in backup task sources. However, if a tag produces only one result, it can be used in both sources and targets.
There are two types of tag elements:
Built-in tag elements.
Custom tag elements.
Built-in tag elements are easily recognizable because they contain a : (colon) character, and some of them can accept a parameter.
Custom tag elements cannot contain a : (colon) character, and they cannot have parameters. If a custom tag element must refer a local drive path (like C:\), it must use the colon: tag element: <C<colon:>\> (yes, tags can be nested).
In all tag elements, leading and trailing spaces are ignored: < a | b > is the same as <a|b>. If you do need to enter whitespace, use the <space:> or <tab:> tags.
Spaces between the tag name and the tag parameter are ignored, too: <LocalDate: +1w> is the same as <LocalDate:+1w>.
Spaces inside a tag element's parameter are NOT ignored: <RootOfVolumeByLabel: The Label> is NOT the same as <RootOfVolumeByLabel: TheLabel>.
Also, spaces inside a custom tag element are NOT ignored: <a b|c d> is NOT the same as <ab|cd>.
In other words, only these spaces are ignored:
After the opening of a tag (after the < character).
Before the closing of a tag (before the > character).
Around a tag element separator (before and after the | character).
Between a tag element's name and the tag element's parameter (after the : character when used to indicate a tag element's name).
Two values:
Is resolved to:
Current date and time:
Is resolved to (for example):
Two tags in the same text:
Is resolved to:
These are the most common built-in tag elements.
This tag element can be used to prevent unwanted multiplication of tag elements with multiple results. This is the usage pattern:
Include the id: tag element as the first element in a multi-element tag, the first time that multi-element tag is used.
Assign it an integer parameter, for example <id: 1 | value1 | value2>.
Use only the id: tag element instead of the multiple tag further on in that pattern (e.g.: <id: 1>).
For example, by default this pattern:
Is resolved to four results:
If this is not what you wanted, then you need to use the id: tag:
Is resolved to:
This tag element is resolved to the items in the list specified as a parameter, and it produces as many results as there are items in the list.
If the list contains multiple elements, resolving the tag will produce multiple results. If the list is empty, resolving the tag will produce no results at all.
For example, let's say list MyList contains four items (the names of four users on the computer): John, Mary, James and Helen. Let's also say you want to create a task to backup all files on their Desktop folders. Then this pattern:
Is resolved to:
Using two or more list: tag elements in separate tags in the same pattern can result in undesired effects. For example, let's say list OtherList contains two items: John and Mary. Let's also say that John-PC and Mary-PC are the names of their computers, and that you want to backup all files on their Desktop folders. Then this pattern:
Is resolved to:
To avoid this, you need to use the id: tag this way:
Is resolved to:
The list: tag element can be used in a target only if it resolves to a single result. It can be used in a source regardless of the number of results it resolves to.
These tag elements can be used to escape various special characters that cannot be used directly in file paths and patterns.
This tag element is resolved to the < (less than) character.
This tag element is resolved to the > (greater than) character.
This tag element is resolved to the | (vertical bar) character.
This tag element is resolved to the : (colon) character.
This tag element is resolved to the / (forward slash, or simply slash) character.
This tag element is resolved to the \ (backslash) character.
This tag element is resolved to the (space) character.
This tag element is resolved to the (horizontal tab) character (ASCII code 8).
These tag elements are resolved according to the local date and time.
Please be aware that the local date and time may change instantly by one or more full hours when changing time zones, or when daylight saving time is in effect.
All local date and time tag elements support an optional delta parameter, entered in this format: +[value][unit] or -[value][unit], where:
[value] is an integer or floating-point number (e.g. 2, or 17.12). The period is the only decimal point accepted, regardless of the current locale.
[unit] is a single letter designating the time unit for the previous value. Accepted values are: w (weeks), d (days), h (hours), m (minutes), s (seconds) and f (milliseconds).
Tag | Gets resolved to |
---|---|
<LocalDate: +1w> | Adds one week to the current local date and time before resolving the tag. |
<LocalYear: -2.75d> | Subtracts 2.75 days from the current local date and time before resolving the tag. |
<LocalSecond: +17.01h> | Adds 17.01 hours to the current local date and time before resolving the tag. |
<LocalYear2: +5m> | Adds 5 minutes to the current local date and time before resolving the tag. |
<LocalDay: -1.2s> | Subtracts 1.2 seconds to the current local date and time before resolving the tag. |
<LocalMonth: +101f> | Adds 101 milliseconds to the current local date and time before resolving the tag. |
You can only use one delta parameter in such a tag. To add 2 days and 3 hours, use +51h or +2.125d instead.
Note that these delta parameters don't change the current local date and time of the computer. They only affect the resolved value of the tag element that contains them.
This tag element is resolved to the current local date and time in the format yyyy-MM-dd HH-mm-ss.
For example, if local date and time is 5:27pm, May 23rd, 2020, this tag element is resolved to 2020-05-23 17-27-00.
All local date and time tag elements support an optional delta parameter, as described here.
This tag element is resolved to the current local date and time in the canonical format yyyy-MM-ddTHH:mm:sszzz.
For example, if local date and time is 5:27pm, May 23rd, 2020, and the time zone is UTC+2, this tag element is resolved to 2020-05-23T17:27:00+02:00.
Date and time in the canonical format is useful when using AQS (Advanced Query Syntax) for searching the file system.
All local date and time tag elements support an optional delta parameter, as described here.
This tag element is resolved to the current local date and time in the canonical format yyyy-MM-ddTHH:mm:ss.fffzzz (it includes the milliseconds).
For example, if local date and time is 5:27pm, May 23rd, 2020, and the time zone is UTC+2, this tag element is resolved to 2020-05-23T17:27:00.000+02:00.
Date and time in the canonical format is useful when using AQS (Advanced Query Syntax) for searching the file system.
All local date and time tag elements support an optional delta parameter, as described here.
This tag element is resolved to the four-digit year of the current local date.
All local date and time tag elements support an optional delta parameter, as described here.
This tag element is resolved to the last two digits of the year of the current local date. This is a number between 00 and 99.
All local date and time tag elements support an optional delta parameter, as described here.
This tag element is resolved to the month of the current local date. This is a number between 1 and 12.
All local date and time tag elements support an optional delta parameter, as described here.
This tag element is resolved to the two-digit month of the current local date. This is a number between 01 and 12.
All local date and time tag elements support an optional delta parameter, as described here.
This tag element is resolved to the day of the month of the current local date. This is a number between 1 and 31.
All local date and time tag elements support an optional delta parameter, as described here.
This tag element is resolved to the two-digit day of the month of the current local date. This is a number between 01 and 31.
All local date and time tag elements support an optional delta parameter, as described here.
This tag element is resolved to the hour of the current local time. This is a number between 0 and 23.
All local date and time tag elements support an optional delta parameter, as described here.
This tag element is resolved to the two-digit hour of the current local time. This is a number between 00 and 23.
All local date and time tag elements support an optional delta parameter, as described here.
This tag element is resolved to the minute of the current local time. This is a number between 0 and 59.
All local date and time tag elements support an optional delta parameter, as described here.
This tag element is resolved to the two-digit minute of the current local time. This is a number between 00 and 59.
All local date and time tag elements support an optional delta parameter, as described here.
This tag element is resolved to the second of the current local time. This is a number between 0 and 59.
All local date and time tag elements support an optional delta parameter, as described here.
This tag element is resolved to the two-digit second of the current local time. This is a number between 00 and 59.
All local date and time tag elements support an optional delta parameter, as described here.
This tag element is resolved to the millisecond of the current local time. This is a number between 0 and 999.
All local date and time tag elements support an optional delta parameter, as described here.
This tag element is resolved to the three-digit millisecond of the current local time. This is a number between 000 and 999.
All local date and time tag elements support an optional delta parameter, as described here.
These tag elements are resolved according to the Universal Time Coordinated, also known as GMT (Greenwich Mean Time).
Please be aware that the UTC date and time does not change when changing time zones, or when daylight saving time is in effect. However, UTC time may change slightly when the computer time is synchronized to time a server.
All UTC date and time tag elements support an optional delta parameter, entered in this format: +[value][unit] or -[value][unit], where:
[value] is an integer or floating-point number (e.g. 2, or 17.12). The period is the only decimal point accepted, regardless of the current locale.
[unit] is a single letter designating the time unit for the previous value. Accepted values are: w (weeks), d (days), h (hours), m (minutes), s (seconds) and f (milliseconds).
Tag | Gets resolved to |
---|---|
<UtcDate: +1w> | Adds one week to the current UTC date and time before resolving the tag. |
<UtcYear: -2.75d> | Subtracts 2.75 days from the current UTC date and time before resolving the tag. |
<UtcSecond: +17.01h> | Adds 17.01 hours to the current UTC date and time before resolving the tag. |
<UtcYear2: +5m> | Adds 5 minutes to the current UTC date and time before resolving the tag. |
<UtcDay: -1.2s> | Subtracts 1.2 seconds to the current UTC date and time before resolving the tag. |
<UtcMonth: +101f> | Adds 101 milliseconds to the current UTC date and time before resolving the tag. |
You can only use one delta parameter in such a tag. To add 2 days and 3 hours, use +51h or +2.125d instead.
Note that these delta parameters don't change the current UTC date and time of the computer. They only affect the resolved value of the tag element that contains them.
This tag element is resolved to the current UTC date and time in the format yyyy-MM-dd HH-mm-ss.
For example, if the UTC date and time is 5:27pm, May 23rd, 2020, this tag element is resolved to 2020-05-23 17-27-00.
All UTC date and time tag elements support an optional delta parameter, as described here.
This tag element is resolved to the current UTC date and time in the canonical format yyyy-MM-ddTHH:mm:ssZ.
For example, if the UTC date and time is 5:27pm, May 23rd, 2020, this tag element is resolved to 2020-05-23T17:27:00Z.
Date and time in the canonical format is useful when using AQS (Advanced Query Syntax) for searching the file system.
All UTC date and time tag elements support an optional delta parameter, as described here.
This tag element is resolved to the current UTC date and time in the canonical format yyyy-MM-ddTHH:mm:ss.fffZ (it includes the milliseconds).
For example, if the UTC date and time is 5:27pm, May 23rd, 2020, this tag element is resolved to 2020-05-23T17:27:00.000Z.
Date and time in the canonical format is useful when using AQS (Advanced Query Syntax) for searching the file system.
All UTC date and time tag elements support an optional delta parameter, as described here.
This tag element is resolved to the four-digit year of the current UTC date.
All UTC date and time tag elements support an optional delta parameter, as described here.
This tag element is resolved to the last two digits of the year of the current UTC date. This is a number between 00 and 99.
All UTC date and time tag elements support an optional delta parameter, as described here.
This tag element is resolved to the month of the current UTC date. This is a number between 1 and 12.
All UTC date and time tag elements support an optional delta parameter, as described here.
This tag element is resolved to the two-digit month of the current UTC date. This is a number between 01 and 12.
All UTC date and time tag elements support an optional delta parameter, as described here.
This tag element is resolved to the day of the month of the current UTC date. This is a number between 1 and 31.
All UTC date and time tag elements support an optional delta parameter, as described here.
This tag element is resolved to the two-digit day of the month of the current UTC date. This is a number between 01 and 31.
All UTC date and time tag elements support an optional delta parameter, as described here.
This tag element is resolved to the hour of the current UTC time. This is a number between 0 and 23.
All UTC date and time tag elements support an optional delta parameter, as described here.
This tag element is resolved to the two-digit hour of the current UTC time. This is a number between 00 and 23.
All UTC date and time tag elements support an optional delta parameter, as described here.
This tag element is resolved to the minute of the current UTC time. This is a number between 0 and 59.
All UTC date and time tag elements support an optional delta parameter, as described here.
This tag element is resolved to the two-digit minute of the current UTC time. This is a number between 00 and 59.
All UTC date and time tag elements support an optional delta parameter, as described here.
This tag element is resolved to the second of the current UTC time. This is a number between 0 and 59.
All UTC date and time tag elements support an optional delta parameter, as described here.
This tag element is resolved to the two-digit second of the current UTC time. This is a number between 00 and 59.
All UTC date and time tag elements support an optional delta parameter, as described here.
This tag element is resolved to the millisecond of the current UTC time. This is a number between 0 and 999.
All UTC date and time tag elements support an optional delta parameter, as described here.
This tag element is resolved to the three-digit millisecond of the current UTC time. This is a number between 000 and 999.
All UTC date and time tag elements support an optional delta parameter, as described here.
This tag element is resolved to the Cookies folder of the current user. Usually this is C:\Users\[CurrentUser]\AppData\Local\Microsoft\Windows\INetCookies, but it is not guaranteed that the app has the right to access it.
This tag element is resolved to the Desktop folder of the current user. Usually this is C:\Users\[CurrentUser]\Desktop.
This tag element is resolved to the Documents folder of the current user. Usually this is C:\Users\[CurrentUser]\Documents.
This tag element is resolved to the Favorites folder of the current user. Usually this is C:\Users\[CurrentUser]\Favorites.
This tag element is resolved to the History folder of the current user. Usually this is C:\Users\[CurrentUser]\AppData\Local\Microsoft\Windows\History, but it is not guaranteed that the app has the right to access it.
This tag element is resolved to the Music folder of the current user. Usually this is C:\Users\[CurrentUser]\Music.
This tag element is resolved to the Pictures folder of the current user. Usually this is C:\Users\[CurrentUser]\Pictures.
This tag element is resolved to the user folder of the current user. Usually this is C:\Users\[CurrentUser].
This tag element is resolved to the Recent folder of the current user. Usually this is C:\Users\[CurrentUser]\AppData\Roaming\Microsoft\Windows\Recent.
This tag element is not available in DSE Backup Expert Pro Server (which is built specially for the Windows Server line of products).
This tag element is resolved to the Templates folder of the current user. Usually this is C:\Users\[CurrentUser]\AppData\Roaming\Microsoft\Windows\Templates.
This tag element is resolved to the Videos folder of the current user. Usually this is C:\Users\[CurrentUser]\Videos.
This tag element is resolved to the OneDrive folder of the current user. Usually this is C:\Users\[CurrentUser]\OneDrive.
This tag element is resolved to the Downloads folder of the current user. Usually this is C:\Users\[CurrentUser]\Downloads.
This tag element is not available in DSE Backup Expert Pro Server (which is built specially for the Windows Server line of products).
This tag element is resolved to the Recent folder of the current user. Usually this is C:\Users\[CurrentUser]\Pictures\Saved Pictures.
This tag element is not available in DSE Backup Expert Pro Server (which is built specially for the Windows Server line of products).
This tag element is resolved to the Screenshots folder of the current user. Usually this is C:\Users\[CurrentUser]\Pictures\Screenshots., but the operation will fail if it doesn't already exist.
These folders are intended primarily for the UWP (Universal Windows Platform) apps, and they may not always be accessible to standard Desktop applications. Therefore, some of these tag elements may not always work correctly in the releases of DSE Backup Expert Pro that are not purchased through the Microsoft Store.
Moreover, these tag elements are not available in DSE Backup Expert Pro Server (which is built specially for the Windows Server line of products).
This tag element is resolved to the Camera Roll folder of the current user. Usually this is C:\Users\[CurrentUser]\Pictures\Camera Roll.
This tag element is not available in DSE Backup Expert Pro Server (which is built specially for the Windows Server line of products).
This tag element is resolved to the Playlists folder of the current user. Usually this is C:\Users\[CurrentUser]\Music\Playlists.
This tag element is not available in DSE Backup Expert Pro Server (which is built specially for the Windows Server line of products).
This tag element is resolved to the Saved Pictures folder of the current user. Usually this is C:\Users\[CurrentUser]\Pictures\Saved Pictures.
This tag element is not available in DSE Backup Expert Pro Server (which is built specially for the Windows Server line of products).
This tag element is resolved to the Documents Library folder of the current user.
This folder is used by the UWP (Universal Windows Platform) apps, and it may not be accessible to standard Desktop applications. Therefore, this tag element may not work in the releases of DSE Backup Expert Pro that are not purchased through the Microsoft Store.
This tag element is not available in DSE Backup Expert Pro Server (which is built specially for the Windows Server line of products).
This tag element is resolved to the HomeGroup folder on the local computer, when supported by the operating system.
This folder is used by the UWP (Universal Windows Platform) apps, and it may not be accessible to standard Desktop applications. Therefore, this tag element may not work in the releases of DSE Backup Expert Pro that are not purchased through the Microsoft Store.
This tag element is not available in DSE Backup Expert Pro Server (which is built specially for the Windows Server line of products).
This tag element is resolved to the Media Servers folder of the current user.
This folder is used by the UWP (Universal Windows Platform) apps, and it may not be accessible to standard Desktop applications. Therefore, this tag element may not work in the releases of DSE Backup Expert Pro that are not purchased through the Microsoft Store.
This tag element is not available in DSE Backup Expert Pro Server (which is built specially for the Windows Server line of products).
This tag element is resolved to the Music folder of the current user.
This folder is used by the UWP (Universal Windows Platform) apps, and it may not be accessible to standard Desktop applications. Therefore, this tag element may not work in the releases of DSE Backup Expert Pro that are not purchased through the Microsoft Store.
This tag element is not available in DSE Backup Expert Pro Server (which is built specially for the Windows Server line of products).
This tag element is resolved to the Pictures folder of the current user.
This folder is used by the UWP (Universal Windows Platform) apps, and it may not be accessible to standard Desktop applications. Therefore, this tag element may not work in the releases of DSE Backup Expert Pro that are not purchased through the Microsoft Store.
This tag element is not available in DSE Backup Expert Pro Server (which is built specially for the Windows Server line of products).
This tag element is resolved to the Removable Storage Devices folder of the current user.
This folder is used by the UWP (Universal Windows Platform) apps, and it may not be accessible to standard Desktop applications. Therefore, this tag element may not work in the releases of DSE Backup Expert Pro that are not purchased through the Microsoft Store.
This tag element is not available in DSE Backup Expert Pro Server (which is built specially for the Windows Server line of products).
This tag element is resolved to the Videos folder of the current user.
This folder is used by the UWP (Universal Windows Platform) apps, and it may not be accessible to standard Desktop applications. Therefore, this tag element may not work in the releases of DSE Backup Expert Pro that are not purchased through the Microsoft Store.
This tag element is not available in DSE Backup Expert Pro Server (which is built specially for the Windows Server line of products).
This tag element is resolved to the Captures folder of the current user. Usually this is C:\Users\[CurrentUser]\Videos\Captures.
This tag element is not available in DSE Backup Expert Pro Server (which is built specially for the Windows Server line of products).
This tag element is resolved to the 3D Objects folder of the current user. Usually this is C:\Users\[CurrentUser]\3D Objects.
This tag element is not available in DSE Backup Expert Pro Server (which is built specially for the Windows Server line of products).
This tag element is resolved to the Recorded Calls folder of the current user. Usually this is C:\Users\[CurrentUser]\Recorded Calls.
This tag element is not available in DSE Backup Expert Pro Server (which is built specially for the Windows Server line of products).
These tag elements are resolved to the root folder of logical volumes on the local computer (e.g. C:, D:, etc).
These tag elements can be used in both source (read-only) and target (read/write) paths.
This tag element replaces the now-deprecated label: tag element.
This tag element is resolved to the root folder of the logical volume with the name (label) specified as a parameter for the tag element.
If there is no volume with that label, or if there is more than one volume with that label, the tag element won't be resolved, and the backup task will be affected as follows:
If the tag element is used in a source's path(s), those paths will fail (but other paths in the source may succeed).
If the tag element is used in a target's path, that target will fail entirely (but other targets in the backup task may succeed).
For example, if volume F is hosted on a memory stick and is labeled BAK_STICK, then <RootOfVolumeByLabel: BAK-STICK> will be resolved to F:.
This tag element is useful when working with external removable drives that contain volumes which are not assigned the same letters every time they are connected to the computer.
Please be aware that if in the computer there are volumes that are not accessible at the time this tag element is resolved (for example, they are encrypted by BitLocker, and have not been unlocked), such volumes are ignored at that time. Unlock them first if you want DSE Backup Expert Pro to be able to access them.
This tag element replaces the now-deprecated root: tag element.
This tag element is resolved to the root folder of the volume that contains in its root a folder named exactly as the parameter for the tag element.
If there is no volume with such a folder, or if there is more than one volume with such a folder, the tag element won't be resolved, and the backup task will be affected as follows:
If the tag element is used in a source's path(s), those paths will fail (but other paths in the source may succeed).
If the tag element is used in a target's path, that target will fail entirely (but other targets in the backup task may succeed).
For example, if F:\MyBackup is a folder on a memory stick, then <RootOfVolumeByFolder: MyBackup> will be resolved to F: (NOT to F:\MyBackup!).
This tag element is useful when working with external removable drives that contain volumes which are not assigned the same letters every time they are connected to the computer.
Please be aware that if in the computer there are volumes that are not accessible at the time this tag element is resolved (for example, they are encrypted by BitLocker, and have not been unlocked), such volumes are ignored at that time. Unlock them first if you want DSE Backup Expert Pro to be able to access them.
Terminology clarifications:
Sometimes logical volumes are referred to as partitions. While this may usually be accurate, sometimes one volume can occupy more than one partition, therefore this documentation will try to avoid this confusion.
Sometimes logical volumes are referred to as drives, or logical drives. However, it is important not to confuse them with physical drives, which are the physical electronic devices also known as hard disk drives (HDDs), or solid state drives (SSDs).
A logical volume usually occupies only one partition, on a single physical drive. However, it is possible for a logical volume to occupy more than one partition, on more than one physical drive.
A physical drive can host more than one logical volume.
For example, you can have both volumes C: and D: occupying exactly one partition each on physical drive 0 (zero), and volume E: occupying a partition on physical drive 0 (zero) and another partition on physical drive 1 (one).
These tag elements can be used to access logical volumes on the local computer. They get resolved to special Windows-specific paths, like \\.\C:, \\.\D:, etc.
Every logical volume in a Windows operating system is identified by one unique letter (C, D, E, etc.). These tag elements allow you to read and write directly to the sectors of a logical volume.
These tag elements can be used in both source (read-only) and target (read/write) paths.
This tag element is resolved to the path of the logical volume identified by the letter specified as a parameter for the tag element.
For example, <LogicalVolumeByLetter: D> will be resolved to the special Windows-specific path \\.\D:.
This tag element can be used in both source (read-only) and target (read/write) paths.
This tag element is resolved to the path of the logical volume with the label specified as a parameter for the tag element.
If there is no volume with that label, or if there is more than one volume with that label, the tag element won't be resolved, and the backup task will be affected as follows:
If the tag element is used in a source's path(s), those paths will fail (but other paths in the source may succeed).
If the tag element is used in a target's path, that target will fail entirely (but other targets in the backup task may succeed).
For example, if volume F is hosted on a memory stick and is labeled BAK_STICK, then <LogicalVolumeByLabel: BAK-STICK> will be resolved to the same Windows-specific path as <LogicalVolumeByLetter: F> (\\.\F:).
This tag element is useful when working with external removable drives that contain volumes which are not assigned the same letters every time they are connected to the computer.
Please be aware that if in the computer there are volumes that are not accessible at the time this tag element is resolved (for example, they are encrypted by BitLocker, and have not been unlocked), such volumes are ignored at that time. Unlock them first if you want DSE Backup Expert Pro to be able to access them.
This tag element can be used in both source (read-only) and target (read/write) paths.
This tag element replaces the now-deprecated LogicalVolumeByRoot: tag element.
This tag element is resolved to the path of the logical volume that contains in its root a folder named exactly as the parameter for the tag element.
If there is no volume with such a folder, or if there is more than one volume with such a folder, the tag element won't be resolved, and the backup task will be affected as follows:
If the tag element is used in a source's path(s), those paths will fail (but other paths in the source may succeed).
If the tag element is used in a target's path, that target will fail entirely (but other targets in the backup task may succeed).
For example, if F:\MyBackup is a folder on a memory stick, then <LogicalVolumeByFolder: MyBackup> will be resolved to the same Windows-specific path as <LogicalVolumeByLetter: F> (\\.\F:).
This tag element is useful when working with external removable drives that contain volumes which are not assigned the same letters every time they are connected to the computer.
Please be aware that if in the computer there are volumes that are not accessible at the time this tag element is resolved (for example, they are encrypted by BitLocker, and have not been unlocked), such volumes are ignored at that time. Unlock them first if you want DSE Backup Expert Pro to be able to access them.
This tag element can be used in both source (read-only) and target (read/write) paths.
Terminology clarification:
An extended logical volume is (in DSE Backup Expert Pro terminology) a logical volume (see above) that also includes a couple of hidden sectors.
These tag elements can be used to access extended logical volumes on the local computer, including their hidden sectors. They get resolved to special Windows-specific paths, like \\.\C:, \\.\D:, etc.
According to Microsoft documentation, this feature "should only be used with great caution by [people] familiar with the underlying structure of a hard disk drive and file system. Improper use [...] can result in damage to data on the partition, or destruction of the entire partition." Therefore, if you don't understand exactly what the hidden sectors are and what they are used for, it is better not to use these tag elements.
Technical details:
Extended logical volumes are opened like regular logical volumes (e.g.: by calling CreateFile("\\.\C:", ...)), followed immediately by a call to DeviceIoControl with control code FSCTL_ALLOW_EXTENDED_DASD_IO, to secure access to the volume's hidden sectors.
These tag elements can be used in both source (read-only) and target (read/write) paths.
This tag element is resolved to the path of the extended logical volume identified by the letter specified as a parameter for the tag element.
For example, <LogicalVolumeExByLetter: D> will be resolved to the special Windows-specific path \\.\D:.
This tag element can be used in both source (read-only) and target (read/write) paths.
This tag element is resolved to the path of the extended logical volume with the label specified as a parameter for the tag element.
If there is no volume with that label, or if there is more than one volume with that label, the tag element won't be resolved, and the backup task will be affected as follows:
If the tag element is used in a source's path(s), those paths will fail (but other paths in the source may succeed).
If the tag element is used in a target's path, that target will fail entirely (but other targets in the backup task may succeed).
For example, if volume F is hosted on a memory stick and is labeled BAK_STICK, then <LogicalVolumeExByLabel: BAK-STICK> will be resolved to the same Windows-specific path as <LogicalVolumeExByLetter: F> (\\.\F:).
This tag element is useful when working with external removable drives that contain volumes which are not assigned the same letters every time they are connected to the computer.
Please be aware that if in the computer there are volumes that are not accessible at the time this tag element is resolved (for example, they are encrypted by BitLocker, and have not been unlocked), such volumes are ignored at that time. Unlock them first if you want DSE Backup Expert Pro to be able to access them.
This tag element can be used in both source (read-only) and target (read/write) paths.
This tag element replaces the now-deprecated LogicalVolumeExByRoot: tag element.
This tag element is resolved to the path of the extended logical volume that contains in its root a folder named exactly as the parameter for the tag element.
If there is no volume with such a folder, or if there is more than one volume with such a folder, the tag element won't be resolved, and the backup task will be affected as follows:
If the tag element is used in a source's path(s), those paths will fail (but other paths in the source may succeed).
If the tag element is used in a target's path, that target will fail entirely (but other targets in the backup task may succeed).
For example, if F:\MyBackup is a folder on a memory stick, then <LogicalVolumeExByFolder: MyBackup> will be resolved to the same Windows-specific path as <LogicalVolumeExByLetter: F> (\\.\F:).
This tag element is useful when working with external removable drives that contain volumes which are not assigned the same letters every time they are connected to the computer.
Please be aware that if in the computer there are volumes that are not accessible at the time this tag element is resolved (for example, they are encrypted by BitLocker, and have not been unlocked), such volumes are ignored at that time. Unlock them first if you want DSE Backup Expert Pro to be able to access them.
This tag element can be used in both source (read-only) and target (read/write) paths.
Terminology clarification:
A physical volume refers (in DSE Backup Expert Pro terminology) to the physical sectors of an extended logical volume (see above).
The main difference between a logical and a physical volume is that accessing a physical volume means accessing directly the physical sectors on the physical drives that host the volume. Therefore, reading a BitLocker-encrypted physical volume means reading the actual encrypted sectors, which can be done without unlocking the volume first.
These tag elements can be used to access the physical sectors of the logical volumes on the local computer. They get resolved to one or more special Windows-specific paths, like \\.\PhysicalDrive0, \\.\PhysicalDrive2, etc.
Physical volumes are accessed by opening the physical drives that host them (e.g.: by calling CreateFile("\\.\PhysicalDrive0", ...)), but only the partitions occupied by the volume are actually read or written.
These tag elements can be used in both source (read-only) and target (read/write) paths.
This tag element is resolved to the paths of the physical volume identified by the letter specified as a parameter for the tag element.
For example, if volume D is hosted on two partitions on physical drives at indices 0 and 2, <PhysicalVolumeByLetter: D> will be resolved to both \\.\PhysicalDrive0 and \\.\PhysicalDrive2. First, DSE Backup Expert Pro reads (or writes) the sectors hosted on PhysicalDrive0, then the sectors hosted on PhysicalDrive2.
This tag element can be used in both source (read-only) and target (read/write) paths.
This tag element is resolved to the path of the physical volume with the label specified as a parameter for the tag element.
If there is no volume with that label, or if there is more than one volume with that label, the tag element won't be resolved, and the backup task will be affected as follows:
If the tag element is used in a source's path(s), those paths will fail (but other paths in the source may succeed).
If the tag element is used in a target's path, that target will fail entirely (but other targets in the backup task may succeed).
For example, if volume F is hosted on a memory stick and is labeled BAK_STICK, then <PhysicalVolumeByLabel: BAK-STICK> will be resolved to the same Windows-specific paths as <PhysicalVolumeByLetter: F>.
This tag element is useful when working with external removable drives that contain volumes which are not assigned the same letters every time they are connected to the computer.
Please be aware that if in the computer there are volumes that are not accessible at the time this tag element is resolved (for example, they are encrypted by BitLocker, and have not been unlocked), such volumes are ignored at that time. Unlock them first if you want DSE Backup Expert Pro to be able to access them.
This tag element can be used in both source (read-only) and target (read/write) paths.
This tag element replaces the now-deprecated PhysicalVolumeByRoot: tag element.
This tag element is resolved to the path of the physical volume that contains in its root a folder named exactly as the parameter for the tag element.
If there is no volume with such a folder, or if there is more than one volume with such a folder, the tag element won't be resolved, and the backup task will be affected as follows:
If the tag element is used in a source's path(s), those paths will fail (but other paths in the source may succeed).
If the tag element is used in a target's path, that target will fail entirely (but other targets in the backup task may succeed).
For example, if F:\MyBackup is a folder on a memory stick, then <PhysicalVolumeByFolder: MyBackup> will be resolved to the same Windows-specific paths as <PhysicalVolumeByLetter: F>.
This tag element is useful when working with external removable drives that contain volumes which are not assigned the same letters every time they are connected to the computer.
Please be aware that if in the computer there are volumes that are not accessible at the time this tag element is resolved (for example, they are encrypted by BitLocker, and have not been unlocked), such volumes are ignored at that time. Unlock them first if you want DSE Backup Expert Pro to be able to access them.
This tag element can be used in both source (read-only) and target (read/write) paths.
Terminology clarification:
A Volume Shadow Copy (VSC) refers (in DSE Backup Expert Pro terminology) to the logical sectors of a logical volume (see above), captured in a consistent state while the volume is still in use.
The main difference between a logical volume and a shadow copy of it is that the shadow copy can be read and backed up without the need to lock the volume first (even if the volume is hosting the operating system).
These tag elements can be used to access the logical sectors of the logical volumes on the local computer and also on the network, provided the network machine runs VSS (Volume Shadow Service).
Shadow copies of volumes are accessed by opening them like virtual files (e.g.: by calling CreateFile("\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1", ...)).
These tag elements can only be used in source (read-only) paths.
WARNING: On 64 bit Windows you need to run the 64 bit edition of DSE Backup Expert Pro in order for all features to work correctly. If you run 32 bit DSE Backup Expert Pro on 64 bit Windows, the features related to Volume Shadow Copy may not work correctly. This is not a problem when running 32 bit DSE Backup Expert Pro on 32 bit Windows, or when running 64 bit DSE Backup Expert Pro on 64 bit Windows, but only when the 32 bit app runs on a 64 bit operating system (because Volume Shadow Copy Service is not fully accessible from WoW64).
This tag element is resolved to the path of a temporary and newly-created shadow copy of the logical volume identified by the letter specified as a parameter for the tag element.
For example, <VscOfVolumeByLetter: D> will be resolved to a temporary special Windows-specific path (e.g. \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1).
Lifespan: The shadow copy is created when DSE Backup Expert Pro needs to read it, and it is deleted immediately after it is read entirely.
This tag element should only be used in source (read-only) paths, because shadow copies are read-only.
This tag element is resolved to the path of a temporary and newly-created shadow copy of the logical volume with the label specified as a parameter for the tag element.
If there is no volume with that label, or if there is more than one volume with that label, the tag element won't be resolved, and the backup task will be affected as follows:
If the tag element is used in a source's path(s), those paths will fail (but other paths in the source may succeed).
If the tag element is used in a target's path, that target will fail entirely (but other targets in the backup task may succeed).
For example, if volume F is hosted on a memory stick and is labeled BAK_STICK, then <VscOfVolumeByLabel: BAK-STICK> will be resolved to the same Windows-specific path as <VscOfVolumeByLetter: F> (e.g. \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1).
This tag element is useful when working with external removable drives that contain volumes which are not assigned the same letters every time they are connected to the computer.
Please be aware that if in the computer there are volumes that are not accessible at the time this tag element is resolved (for example, they are encrypted by BitLocker, and have not been unlocked), such volumes are ignored at that time. Unlock them first if you want DSE Backup Expert Pro to be able to access them.
Lifespan: The shadow copy is created when DSE Backup Expert Pro needs to read it, and it is deleted immediately after it is read entirely.
This tag element should only be used in source (read-only) paths, because shadow copies are read-only.
This tag element replaces the now-deprecated VscOfVolumeByRoot: tag element.
This tag element is resolved to the path of a temporary and newly-created shadow copy of the logical volume that contains in its root a folder named exactly as the parameter for the tag element.
If there is no volume with such a folder, or if there is more than one volume with such a folder, the tag element won't be resolved, and the backup task will be affected as follows:
If the tag element is used in a source's path(s), those paths will fail (but other paths in the source may succeed).
If the tag element is used in a target's path, that target will fail entirely (but other targets in the backup task may succeed).
For example, if F:\MyBackup is a folder on a memory stick, then <VscOfVolumeByFolder: MyBackup> will be resolved to the same Windows-specific path as <VscOfVolumeByLetter: F> (e.g. \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1).
This tag element is useful when working with external removable drives that contain volumes which are not assigned the same letters every time they are connected to the computer.
Please be aware that if in the computer there are volumes that are not accessible at the time this tag element is resolved (for example, they are encrypted by BitLocker, and have not been unlocked), such volumes are ignored at that time. Unlock them first if you want DSE Backup Expert Pro to be able to access them.
Lifespan: The shadow copy is created when DSE Backup Expert Pro needs to read it, and it is deleted immediately after it is read entirely.
This tag element should only be used in source (read-only) paths, because shadow copies are read-only.
Terminology clarifications:
A physical drive is a physical electronic device installed in a computer, also known as a hard disk drive (HDD), or a solid state drive (SSD).
These tag elements can be used to access the physical drives on the local computer. They get resolved to special Windows-specific paths like \\.\PhysicalDrive0, \\.\PhysicalDrive1, etc.
Please be aware that a logical volume can be hosted on more than one physical drive, therefore be careful if your intention is to backup one or more volumes.
These tag elements can be used in both source (read-only) and target (read/write) paths.
This tag element is resolved to the path of the physical drive identified by the number specified as a parameter for the tag element.
For example, <PhysicalDriveByIndex: 1> will be resolved to \\.\PhysicalDrive1.
This tag element can be used in both source (read-only) and target (read/write) paths.
This tag element is resolved to the path of the physical drive that hosts the volume identified by the letter specified as a parameter for the tag element.
If the volume is hosted on more than one physical drive, the tag element won't be resolved, and the backup task will be affected as follows:
If the tag element is used in a source's path(s), those paths will fail (but other paths in the source may succeed).
If the tag element is used in a target's path, that target will fail entirely (but other targets in the backup task may succeed).
For example, if volume F is a partition on the physical drive with index 1, then <PhysicalDriveByLetter: F> will be resolved to the same Windows-specific path as <PhysicalDriveByLetter: F> (\\.\PhysicalDrive1).
This tag element can be used in both source (read-only) and target (read/write) paths.
This tag element is resolved to the path of the physical drive that hosts the volume with the label specified as a parameter for the tag element.
If there is no volume with that label, or if there is more than one volume with that label, or if the volume is hosted on more than one physical drive, the tag element won't be resolved, and the backup task will be affected as follows:
If the tag element is used in a source's path(s), those paths will fail (but other paths in the source may succeed).
If the tag element is used in a target's path, that target will fail entirely (but other targets in the backup task may succeed).
For example, if volume F is a partition on the physical drive with index 1, and it is labeled BAK_STICK, then <PhysicalDriveByLabel: BAK-STICK> will be resolved to the same Windows-specific path as <PhysicalDriveByLetter: F> (\\.\PhysicalDrive1).
This tag element is useful when working with external removable drives that contain volumes which are not assigned the same letters every time they are connected to the computer.
Please be aware that if in the computer there are volumes that are not accessible at the time this tag element is resolved (for example, they are encrypted by BitLocker, and have not been unlocked), such volumes are ignored at that time. Unlock them first if you want DSE Backup Expert Pro to be able to access them.
This tag element can be used in both source (read-only) and target (read/write) paths.
This tag element replaces the now-deprecated PhysicalDriveByRoot: tag element.
This tag element is resolved to the path of the physical drive that hosts the volume that contains in its root a folder named exactly as the parameter for the tag element.
If there is no volume with such a folder, or if there is more than one volume with such a folder, or if the volume is hosted on more than one physical drive, the tag element won't be resolved, and the backup task will be affected as follows:
If the tag element is used in a source's path(s), those paths will fail (but other paths in the source may succeed).
If the tag element is used in a target's path, that target will fail entirely (but other targets in the backup task may succeed).
For example, if volume F is a partition on the physical drive with index 1, and if it contains a folder F:\MyBackup (on its topmost level), then <PhysicalDriveByFolder: MyBackup> will be resolved to the same Windows-specific path as <PhysicalDriveByLetter: F> (\\.\PhysicalDrive1).
This tag element is useful when working with external removable drives that contain volumes which are not assigned the same letters every time they are connected to the computer.
Please be aware that if in the computer there are volumes that are not accessible at the time this tag element is resolved (for example, they are encrypted by BitLocker, and have not been unlocked), such volumes are ignored at that time. Unlock them first if you want DSE Backup Expert Pro to be able to access them.
This tag element can be used in both source (read-only) and target (read/write) paths.
This is the first page that gets loaded when the app starts.
If the user has not set a password, or if the user chose to have DSE Backup Expert Pro remember that password, this page will immediately redirect to the Backup Tasks page.
This page lists all complex backup sources found in the currently loaded settings.
Note that it is also possible to define simple sources (in place) directly inside the backup tasks. Those sources are not listed in this page.
This item displays the main information about a source (like name and description).
It also offers button links for these actions: Edit, Duplicate, Simulate and Delete.
This dialog displays the results of a backup source simulation.
If you're not sure which files will get selected for backup, click the Simulate link at the bottom of the Source item and see the results in this dialog.
In this page you can edit a backup source, by changing its properties and by adding or removing paths.
A source's name can only contain letters, digits and the '_' (underscore) character. It must not start with a digit, and it can be maximum 256 characters long.
A source's name is case insensitive, and it must be unique among all the objects in the currently loaded settings.
Examples: my_files, my_daily_work, Johns_desktop, etc.
A source's description can contain any kind of characters. It can be maximum 1,024 characters long.
It should provide a meaningful description of the files it contains. For example: These are the files that I work on every day.
This item contains the options about the file contents and file system properties that are supposed to be backed-up or restored.
When this is checked, and the backup task requires the creation of temporary files (for example, a temporary .zip file that is to be uploaded to an FTP server), then the temporary files will be encrypted using the AES-256 algorithm.
The encryption key and the initialization vector (IV):
Will be generated by a cryptographic random number generator, which guarantees both unpredictability and irreproducibility.
Will only be used once, each time the backup task is run.
Will not be saved anywhere; it will only be stored in RAM and it will not be possible to be retrieved.
Will be forgotten immediately after the backup task finishes.
This ensures the consistency of the source files, and it is on by default.
However, there are times when you may want to uncheck this. For example, when backing up the contents of a volume or of a physical drive, unchecking this option will prevent the locking of the device.
Unchecking this option has the following effects:
Value | Meaning |
---|---|
When reading files | FILE_SHARE_WRITE will be specified when opening the file, allowing write operations to the file while it is being read. |
When reading logical volumes | The volume will not be locked while the backup task runs. Technical details: DeviceIoControl with code FSCTL_LOCK_VOLUME will NOT be called on the volume. |
When reading extended logical volumes | The volume will not be locked while the backup task runs. Technical details: DeviceIoControl with code FSCTL_LOCK_VOLUME will NOT be called on the volume. |
When reading physical volumes | The physical drives hosting the volume will not be taken offline while the backup task runs. Technical details: DeviceIoControl with code IOCTL_DISK_SET_DISK_ATTRIBUTES and parameter DISK_ATTRIBUTE_OFFLINE will NOT be called on the physical drives hosting the volume. |
When reading shadow copies of volumes | No additional effect, since shadow copies are read-only anyway. |
When reading physical drives | The physical drive will not be taken offline while the backup task runs. Technical details: DeviceIoControl with code IOCTL_DISK_SET_DISK_ATTRIBUTES and parameter DISK_ATTRIBUTE_OFFLINE will NOT be called on the physical drive. |
Please be aware that backing up a volume or a drive without locking it may seem to be working many times, yet still, the integrity of the file system cannot be guaranteed in these circumstances.
This option should only be attempted for backing up a volume or a drive for which locking is simply not an option (like a system volume for which you cannot get a shadow copy). In that case, follow these steps:
Stop and close all running applications.
If applicable, stop the indexing service.
If possible, disconnect from the internet.
If possible, boot the machine in safe mode.
Backup the system volume or drive.
WARNING: If you don't understand the explanation above, it's better to leave this option checked.
Selection | Meaning |
---|---|
FILES: Only the file contents (or drive sectors, for drives) | Copies only the contents of the files. |
FOLDERS: Only the folder contents (or drive sectors, for drives) | Copies the files contained by the folder. |
FILES: All information available (rights, attributes and timestamps) | Copies the contents, the access rights, the attributes and the timestamps of the files. |
FOLDERS: All information available (rights, attributes and timestamps) | Copies the contents, the access rights, the attributes and the timestamps of the folders. |
FILES: Custom selection | Copies the selected information for the files. |
FOLDERS: Custom selection | Copies the selected information for the folders. |
FOLDERS: Same as for files (above) | Same option as for files. |
Selection | Meaning |
---|---|
FILES: Only the file contents (or drive sectors, for drives) | Restores or copies only the contents of the files. |
FOLDERS: Only the folder contents (or drive sectors, for drives) | Restores or copies the files contained by the folder. |
FILES: All information available (rights, attributes and timestamps) | Restores or copies the contents, the access rights, the attributes and the timestamps of the files, if available. |
FOLDERS: All information available (rights, attributes and timestamps) | Restores or copies the contents, the access rights, the attributes and the timestamps of the folders, if available. |
FILES: Custom selection | Restores or copies the selected information for the files, if available. |
FOLDERS: Custom selection | Restores or copies the selected information for the folders, if available. |
FOLDERS: Same as for files (above) | Same option as for files. |
Backup source |
Backup target |
Backup result |
---|---|---|
C:\file.txt Only the file contents (or drive sectors, for drives) |
F:\baks Only the file contents (or drive sectors, for drives) |
F:\baks\file.txt The target file will be created with the default access rights for the target folder, the default attributes and the current timestamps. |
C:\file.txt Only the file contents (or drive sectors, for drives) |
F:\baks All information available (rights, attributes and timestamps) |
F:\baks\file.txt The target file will be created with the same access rights, attributes and timestamps as the source. |
C:\file.txt All information available (rights, attributes and timestamps) |
F:\baks Only the file contents (or drive sectors, for drives) |
F:\baks\file.txt.bakex-rawf The contents of the target file will include the access rights, the attributes and the timestamps of the source file. The target file will be created with the default access rights for the target folder, the default attributes and the current timestamps. |
C:\file.txt All information available (rights, attributes and timestamps) |
F:\baks All information available (rights, attributes and timestamps) |
F:\baks\file.txt.bakex-rawf The contents of the target file will include the access rights, the attributes and the timestamps of the source file. The target file will be created with the same access rights, attributes and timestamps as the source. So in this case the access rights, attributes and timestamps of the source are stored twice: first, as content in the target file, and as file system properties of the target file. |
C:\file.txt Only the file contents (or drive sectors, for drives) |
F:\baks\archive.zip (no target options are available in this case) |
F:\baks\archive.zip\file.txt The target file (the archive entry) will be created with the default properties for the archive. |
C:\file.txt All information available (rights, attributes and timestamps) |
F:\baks\archive.zip (no target options are available in this case) |
F:\baks\archive.zip\file.txt.bakex-rawf The contents of the target file (the archive entry) will include the access rights, the attributes and the timestamps of the source file. The target file (the archive entry) will be created with the default properties for the archive. |
Restore source |
Restore target |
Restore result |
---|---|---|
F:\baks\file.txt (no source options are available in this case) |
C: Only the file contents (or drive sectors, for drives) |
C:\file.txt The target (restored) file will be created with the default access rights for the target (restore) folder, the default attributes and the current timestamps. |
F:\baks\file.txt (no source options are available in this case) |
C: All information available (rights, attributes and timestamps) |
C:\file.txt The target (restored) file will be created with the same access rights, attributes and timestamps as the source file (the backup). |
F:\baks\file.txt.bakex-rawf (no source options are available in this case) |
C: Only the file contents (or drive sectors, for drives) |
C:\file.txt The target (restored) file will be created with the default access rights for the target (restore) folder, the default attributes and the current timestamps. The access rights, attributes and timestamps stored in the source file (the backup) will be ignored. |
F:\baks\file.txt.bakex-rawf (no source options are available in this case) |
C: All information available (rights, attributes and timestamps) |
C:\file.txt The target (restored) file will be created with the access rights, attributes and timestamps stored in the source file (the backup). |
F:\baks\archive.zip\file.txt (no source options are available in this case) |
C: Only the file contents (or drive sectors, for drives) |
C:\file.txt The target (restored) file will be created with the default access rights for the target (restore) folder, the default attributes and the current timestamps. |
F:\baks\archive.zip\file.txt.bakex-rawf (no source options are available in this case) |
C: Only the file contents (or drive sectors, for drives) |
C:\file.txt The target (restored) file will be created with the default access rights for the target (restore) folder, the default attributes and the current timestamps. The access rights, attributes and timestamps stored in the source file (the backup) will be ignored. |
F:\baks\archive.zip\file.txt.bakex-rawf (no source options are available in this case) |
C: All information available (rights, attributes and timestamps) |
C:\file.txt The target (restored) file will be created with the access rights, attributes and timestamps stored in the source file (the backup). |
The file contents will be included.
Not that it is also possible to backup or restore only the file system properties (access rights, attributes and timestamps) of files, excluding their contents, if you so choose.
For files:
If file contents are not included (above), and a corresponding target file does not exist, and if this option is checked, then an empty file with that name will be created, and the available file system properties will be applied to it.
For example, if DSE Backup Expert Pro is restoring only the access rights for file.txt, and there is no file.txt file in the target folder, then an empty file.txt will be created, and the access rights will be applied to it.
For folders:
It includes empty folders.
Please be aware that backing up empty folders is not supported on these target types: Azure blob containers, email recipients, and any time the target is an archive (.zip) file (regardless of the target type).
Backing up empty folders is only supported when the target is not a .zip file, and only on these target types: the file system, AWS S3 Buckets, Azure file shares, FTP and SFTP servers.
If this is checked, then for files encrypted by Windows (EFS) the raw (encrypted) data will be copied. This way, a backup operator can backup and restore encrypted files without being able to see the decrypted (clear) data itself.
This option may require backup operator or administrator privileges.
Include file or folder access rights
This option requires backup operator or administrator privileges.
Owner
This option requires backup operator or administrator privileges.
Group
This option requires backup operator or administrator privileges.
Discretionary Access Control List
This option requires backup operator or administrator privileges.
System Access Control List
This option requires backup operator or administrator privileges.
Include file or folder attributes
Depending on the sub-options checked, this may require backup operator or administrator privileges.
Read-only attribute
Hidden attribute
This option may require backup operator or administrator privileges.
System attribute
This option may require backup operator or administrator privileges.
Archive attribute
Do not index attribute
Encrypted attribute
Compressed attribute
Include file or folder timestamps
Created time
Last access time
Last write time
This item is displayed in the Edit Backup Source page, and displays all the details of a source path.
It also offers button links for these actions: Duplicate, Simulate, Delete, Move Up and Move Down.
This is the full path to the folder containing the files. For example: C:\Data\My Files or \\John-PC\D$\Work.
Usage of tags is permitted. For example: C:\Users\<John|Mary>\Desktop will include files in both C:\Users\John\Desktop and C:\Users\Mary\Desktop folders.
Usage of wildcards (* and ?) is permitted on all but the first level of the folder hierarchy. For example, this is a valid pattern: C:\Users\<J*|M*>\Desktop.
Usage of wildcards (* and ?) is not permitted at the top level of the folder hierarchy. For example, these are not valid patterns: ?:\Users\John, \\*\D$. In other words, you cannot use wildcards to reference multiple disk drives or multiple computers in the network.
AQS
If your license allows it, you can also use AQS (Advanced Query Syntax) on all but the first level of the folder hierarchy.
In this example, the third level will select all subfolders ending in "details" and created more than a week ago: D:\Data\*details System.DateCreated<colon:><lt:><UtcDateStd:-1w>\images\videos. Note the usage of the <colon:> and <lt:> tags, which get resolved to : and <. The entire pattern gets resolved to (for example): D:\Data\*details System.DateCreated:<2020-04-17T19:25:04Z\images\videos.
Note that when AQS is used, spaces between the folder pattern and the AQS property name are ignored. If your folder pattern contains spaces, you have to use double quotes: D:\Data\"*more details" System.DateCreated<colon:><lt:><UtcDateStd:-1w>\images\videos.
Volumes and drives
Alternatively, this text box can contain a tag with a single element referencing a logical (or physical) volume, or a physical drive. For example: <LogicalVolumeByLetter: D> or <PhysicalDriveById: 1>.
If you don't want to use tags, you can reference volumes and drives this way:
\\.\D: is a reference to the logical volume (drive) D: (sometimes also known as partition D:, or drive D:).
\\.\D> is a reference to the extended logical volume D: (that is, the logical volume D: plus its hidden sectors).
\\.\D< is a reference to the shadow copy of logical volume D: (that is, a consistent, sector by sector copy of volume D:).
\\.\D| is a reference to the physical volume D: (that is, the physical sectors underlying the logical volume D: and its hidden sectors).
\\.\PhysicalDrive1 is a reference to the physical drive at index 1 (the physical electro-mechanic (HDD) or electronic (SSD) device).
When the "Source root folder" field references a volume or a drive, the next field ("File patterns") should be empty.
WARNING: Only advanced users, who understand very well what they are doing, should work with volumes and drives directly! If you're not familiar with terms such as physical drives, partitions and volumes, it is recommended that you stick to backing up and restoring only regular files.
Enter the file types here. You can enter multiple file types, separated by the | (vertical bar) character. For example: *.jpg, file??.j*|picture*.???.
Spaces are not ignored; for example, *.jpg | *.jpeg means files with the jpg (jpg and a space) extension plus files whose name starts with a space.
AQS
If your license allows it, you can also use AQS (Advanced Query Syntax) in this field.
For example, this pattern selects documents authored by John: *.doc System.Author<colon:>John. Note the usage of the <colon:> tag, which gets resolved to :. The entire pattern gets resolved to: D:\Docs\*.doc System.Author:John.
Note that when AQS is used, spaces between the file pattern and the AQS property name are ignored. If your file pattern contains spaces, you have to use double quotes: *.jpg|"My * files.doc" System.Author<colon:>John. In this case, spaces in the first tag element (*.jpg) would not be ignored, only those in the second one!
When the previous field ("Source root folder") references a volume or a drive, this field ("File patterns") should be empty.
WARNING: Only advanced users, who understand very well what they are doing, should work with volumes and drives directly! If you're not familiar with terms such as physical drives, partitions and volumes, it is recommended that you stick to backing up and restoring only regular files.
This checkbox should be checked in order for this path to be taken into consideration.
If this checkbox is not checked, this path is ignored when backup tasks are run.
Check this checkbox if you want files in this path to be EXCLUDED from the backup source.
Paths are evaluated from top to bottom.
For example, a previous additive path can add all files matching the *.* pattern, and a following subtractive path can remove all files matching the *.temp pattern.
Check this checkbox to recursively include files in all subfolders.
This applies to both inclusive and exclusive paths.
This button opens the Smart Menu, which offers the possibility to insert tags and tag elements.
This page lists all backup tasks found in the currently loaded settings.
This item displays the main information about a task (like name and description).
It also offers button links for these actions: Start, Pause, Resume, Stop, Edit, Duplicate, Simulate and Delete.
This dialog displays the results of a backup task simulation.
If you're not sure which files will get selected for backup, click the Simulate link at the bottom of the Task item and see the results in this dialog.
In this page you can edit a backup task, by changing its properties and by adding or removing sources, targets, actions and scheduled runs.
A task's name can only contain letters, digits and the '_' (underscore) character. It must not start with a digit, and it can be maximum 256 characters long.
A task's name is case insensitive, and it must be unique among all the objects in the currently loaded settings.
Examples: backup_my_files, save_my_daily_work, Save_Johns_desktop, etc.
A task's description can contain any kind of characters. It can be maximum 1,024 characters long.
It should provide a meaningful description of what the task accomplishes. For example: This saves to a memory stick the files that I work on every day.
This must be checked for this task to run.
When this is not checked, scheduled runs will be disabled, too. After you check or uncheck this checkbox, you have to click on "Save" before it takes effect.
If checked, a toast notification will be displayed every time the task starts.
Note that this feature does not work in DSE Backup Expert Pro Server (which is built specially for the Windows Server line of products).
If checked, a toast notification will be displayed every time the task finishes (successfully or not).
Note that this feature does not work in DSE Backup Expert Pro Server (which is built specially for the Windows Server line of products).
If checked, a shortcut to this task will be created in DSE Backup Expert Pro's jump list, and also in the systray menu.
Note that clicking on the shortcut in the jump list will not work if the DSE Backup Expert Pro is already running with administrative privileges (this is intentionally disabled for security reasons). However, clicking the shortcut in the systray menu will work in that case, too.
Note that DSE Backup Expert Pro Server does not have a jump list.
If checked, source files will be deleted after backup.
WARNING: Use this option carefully, recovery of the deleted files may not be possible.
If checked, DSE Backup Expert Pro will accurately calculate the amount of data it needs to process when a backup task starts, and it will accurately display the progress while the backup task runs.
This controls the task abortion policy. A task can be aborted if a single source file cannot be opened for reading (set this value to 0), or it can keep running even if millions of source files cannot be opened for reading (set this value to a very large number, like billions or trillions).
The maximum allowed value for this is 9,223,372,036,854,775,807 (263 - 1).
Select how you want the local and UTC date and time tag elements to be evaluated while executing this task. The default value is "Current time when this task is started".
You may want to change the default value when you need to generate an identical file name in multiple backup tasks or actions. For example, a task produces a result named files-<LocalDate:>.zip, and you want to use exactly this result file as a source for your next task. You can do this by forcing both tasks to use the same date and time when evaluating the date and time tag elements.
Important terms:
Standalone Mode: a backup task runs in standalone mode if it was explicitly started by the user, or if it was started because it was scheduled to run at a specific time.
Subtask Mode: a backup task runs in subtask mode if it was started as an action of another task (the parent task). In this scenario, the parent task action's settings can dictate the "executing time" for this task and its actions.
Actions Before: all actions in the "Actions to do before this task" list of the current task.
Actions After: all actions in the "Actions to do after this task" list of the current task.
The Task Itself: the current task, excluding the Actions Before and Actions After.
Current System Time: the current time of the system clock.
Task Executing Time (for a task): the date and time used to evaluate tag elements in its sources and targets (not in its actions). This value is determined by the selection in the dropdown below, is calculated immediately before The Task Itself starts executing, and remains the same for all sources and targets in The Task Itself.
Action Executing Time (for an action): the date and time used to evaluate tag elements in the action's properties (e.g. file paths). This value is determined by the selection in the dropdown below, remains the same for a single action, but it may change from action to action, depending on each action's settings.
Value |
Meaning |
---|---|
Current time when this task is started |
This is the default. Task Executing Time is set to:
Action Executing Time is set according to each action's settings. |
Start of the last "Action to do before this task" |
Task Executing Time is set to the Action Executing Time of the last of the Actions Before. If there are no Actions Before, then Task Executing Time is set to the Current System Time (if the task runs in Standalone Mode), or to the value dictated by the parent task's action otherwise. Action Executing Time is set according to each action's settings. |
Start of the first "Action to do before this task" |
Task Executing Time is set to the Action Executing Time of the first of the Actions Before. If there are no Actions Before, then Task Executing Time is set to the Current System Time (if the task runs in Standalone Mode), or to the value dictated by the parent task's action otherwise. Action Executing Time is set according to each action's settings. |
Force all actions (and this task, too) in this task to use the same date and time |
Task Executing Time and Action Executing Time for all Actions Before and for all Actions After will be forced to the same value. That value is the Current System Time (if this task runs in Standalone Mode), or the value dictated by the parent task's action otherwise. Please be aware that this option is not enforced recursively. That is, it will only have effect on this task, its actions, and the sources and targets of the subtasks started by actions of this task (that is, the subtasks themselves). It will have no effect on the actions of the subtasks, unless this option is selected on the subtasks, too. |
This item allows the definition of a source for a backup task. You can select a predefined backup source, or you can define a simple source by typing in a folder and file pattern.
It also offers button links for these actions: Duplicate, Simulate and Delete.
Check this in order to select a predefined backup source. When checked, the item displays a dropdown with the predefined sources.
In order to be able to use this option, you have to go first to the Backup Sources page and define at least one source.
Select a predefined source from the dropdown. If you have not defined any sources, the dropdown is empty.
This is the full path to the folder containing the files. For example: C:\Data\My Files or \\John-PC\D$\Work.
Usage of tags is permitted. For example: C:\Users\<John|Mary>\Desktop will include files in both C:\Users\John\Desktop and C:\Users\Mary\Desktop folders.
Usage of wildcards (* and ?) is permitted on all but the first level of the folder hierarchy. For example, this is a valid pattern: C:\Users\<J*|M*>\Desktop.
Usage of wildcards (* and ?) is not permitted at the top level of the folder hierarchy. For example, these are not valid patterns: ?:\Users\John, \\*\D$. In other words, you cannot use wildcards to reference multiple disk drives or multiple computers in the network.
AQS
If your license allows it, you can also use AQS (Advanced Query Syntax) on all but the first level of the folder hierarchy.
In this example, the third level will select all subfolders ending in "details" and created more than a week ago: D:\Data\*details System.DateCreated<colon:><lt:><UtcDateStd:-1w>\images\videos. Note the usage of the <colon:> and <lt:> tags, which get resolved to : and <. The entire pattern gets resolved to (for example): D:\Data\*details System.DateCreated:<2020-04-17T19:25:04Z\images\videos.
Note that when AQS is used, spaces between the folder pattern and the AQS property name are ignored. If your folder pattern contains spaces, you have to use double quotes: D:\Data\"*more details" System.DateCreated<colon:><lt:><UtcDateStd:-1w>\images\videos.
Volumes and drives
Alternatively, this text box can contain a tag with a single element referencing to a logical (or physical) volume, or to a physical drive. For example: <LogicalVolumeByLetter: D>, <PhysicalDriveById: 1>.
If you don't want to use tags, you can also reference volumes and drives this way:
\\.\D: is a reference to the logical volume (drive) D: (sometimes also known as partition D:, or drive D:).
\\.\D> is a reference to the extended logical volume D: (that is, the logical volume D: plus its hidden sectors).
\\.\D< is a reference to the shadow copy of logical volume D: (that is, a consistent, sector by sector copy of volume D:).
\\.\D| is a reference to the physical volume D: (that is, the physical sectors underlying the logical volume D: and its hidden sectors).
\\.\PhysicalDrive1 is a reference to the physical drive at index 1 (the physical electro-mechanic (HDD) or electronic (SSD) device).
When the "Source root folder" field references a volume or a drive, the next field ("File patterns") should be empty.
WARNING: Only advanced users, who understand very well what they are doing, should work with volumes and drives directly! If you're not familiar with terms such as physical drives, partitions and volumes, it is recommended that you stick to backing up and restoring only regular files.
Enter the file types here. You can enter multiple file types, separated by the | (vertical bar) character. For example: *.jpg, file??.j*|picture*.???.
Spaces are not ignored; for example, *.jpg | *.jpeg means files with the jpg (jpg and a space) extension plus files whose name starts with a space.
AQS
If your license allows it, you can also use AQS (Advanced Query Syntax) in this field.
For example, this pattern selects documents authored by John: *.doc System.Author<colon:>John. Note the usage of the <colon:> tag, which gets resolved to :. The entire pattern gets resolved to: D:\Docs\*.doc System.Author:John.
Note that when AQS is used, spaces between the file pattern and the AQS property name are ignored. If your file pattern contains spaces, you have to use double quotes: *.jpg|"My * files.doc" System.Author<colon:>John. In this case, spaces in the first tag element (*.jpg) would not be ignored, only those in the second one!
When the previous field ("Source root folder") references a volume or a drive, this field ("File patterns") should be empty.
WARNING: Only advanced users, who understand very well what they are doing, should work with volumes and drives directly! If you're not familiar with terms such as physical drives, partitions and volumes, it is recommended that you stick to backing up and restoring only regular files.
Check this checkbox to recursively include files in all subfolders.
When backing up files from multiple sources, you can use the value in this field to direct each source to be stored in a different subfolder in the target (thus avoiding collisions).
For example, let's say you define three sources:
Source 1: D:\docs\*.* with subfolder in target documents.
Source 2: D:\images\*.* with subfolder in target img.
Source 3: C:\Users\John\Desktop\*.* with subfolder in target mydesk.
And let's say the backup target is F:\myBackup. When running the backup task, the files will be distributed as follows:
Files in source 1 (D:\docs\*.*) will go to F:\myBackup\documents.
Files in source 2 (D:\images\*.*) will go to F:\myBackup\img.
Files in source 3 (C:\Users\John\Desktop\*.*) will go to F:\myBackup\mydesk.
Without entering a value for the source subfolder, all sources would have ended up in F:\myBackup.
This item allows the definition of a target for a backup task.
It also offers button links for these actions: Duplicate and Delete.
Select the target type from the dropdown below:
Value | Meaning |
---|---|
Copy to the file system | The source files will be copied to the selected path on the local computer, on a removable drive, or on a network share. |
Upload to an FTP server | The source files will be uploaded to the selected FTP server. In order to use this option, first you need to add an FTP server in the Backup Targets > FTP Servers page. |
Upload to an AWS S3 bucket | The source files will be uploaded to the selected AWS S3 bucket. In order to use this option, first you need to add an AWS S3 bucket in the Backup Targets > AWS S3 Buckets page. |
Upload to a Microsoft Azure share or blob | The source files will be uploaded to the selected Azure share or blob. In order to use this option, first you need to add an Azure item in the Backup Targets > Microsoft Azure Storage page. |
Upload to an SFTP server | The source files will be uploaded to the selected SFTP server. In order to use this option, first you need to add an SFTP server in the Backup Targets > SFTP Servers page. |
Send as email attachment(s) | The source files will be sent using the selected email account. In order to use this option, first you need to add an email account in the Backup Targets > Email Accounts page. |
Just delete the source files | The source files will be deleted, without backing them up. Use this option carefully, recovery of the deleted files may not be possible. |
Select the predefined target from the dropdown.
The content of the dropdown below changes, depending on the type of target selected in the dropdown above (Target type). It may be empty if no targets of the selected type have been defined.
This field contains the parameters of the target selected above.
Depending on the type of target selected in the dropdown above (Target type), the value in this field means:
Value | Meaning |
---|---|
Copy to the file system | This field contains the full path of the target directory, which may be on the local computer, on a removable drive, or on a network share. |
Upload to an FTP server | This field contains the subfolder (on the FTP server) to upload to. It is ok to be empty. |
Upload to an AWS S3 bucket | This field contains the subfolder (in the S3 bucket) to upload to. It is ok to be empty. |
Upload to a Microsoft Azure share or blob | This field contains the subfolder (in the Azure storage) to upload to. It is ok to be empty. |
Upload to an SFTP server | This field contains the subfolder (on the SFTP server) to upload to. It is ok to be empty. |
Send as email attachment(s) | This field contains the recipients on the To line. It is ok to be empty. |
When sending the backed up files as an email attachment, this field contains the recipients on the Cc line. It is ok to be empty.
When sending the backed up files as an email attachment, this field contains the recipients on the Bcc line. It is ok to be empty.
When the target is a single file, this field contains the name of that file.
The target is a single file when the target is compressed, or when the sources contain a single file. In all other cases, the target cannot be a single file.
The target can be a single file only when the target is compressed, or when the sources contain a single file. In all other cases, the target cannot be a single file.
If this checkbox is checked, and the target is not compressed, and the sources contain more than one file, backing up to this target will fail. However, if the backup task contains other targets, backing up to those other targets may succeed.
If this checkbox is checked, the target files will be compressed by the operating system (if it supports file compression).
Note that it is not possible to have a file both compressed by the operating system and encrypted by the operating system at the same time (Windows does not allow this).
When this checkbox is checked, the target will be compressed, and the result will be a file in the .zip format.
When this is checked, if a source file cannot be read completely, the partial file will be deleted from the archive. However, this may require much more memory (RAM), and it may not work well with large archives (larger than the computer's internal RAM).
When this is not checked, memory usage is kept at reasonable levels, but if a source file cannot be read entirely, the partially written archive entry will not be removed.
However, usually it is OK to leave this unchecked, because situations in which a file can be read only partially are very rare.
This dropdown selects the policy to be applied when the target files already exist:
Value | Meaning |
---|---|
Do not overwrite existing files | Does not overwrite existing files. |
Overwrite only older files that are writable | Overwrites only those files that are both older and writable. |
Overwrite only older files, even if they have the read-only attribute | Forcibly overwrites all files that are older, even those that have the read-only attribute. |
Overwrite all files that are writable | Overwrites only those files that are writable, regardless of age. |
Overwrite all files, even if they have the read-only attribute | Forcibly overwrites all files, regardless of age, even those that have the read-only attribute. |
When this is checked, the files found in the target, but not in source, will be deleted AFTER the backup process finishes.
This option may be used to maintain an accurate (backup) copy of the source.
However, please be aware that overwriting the previous backup will leave you vulnerable to scenarios in which you backup accidentally modified (or deleted) files.
When this is checked, all files and folders in the target will be deleted BEFORE starting the backup process.
This option may not be acceptable when uploading files to a web server, because the files will be unavailable after they are deleted till they are uploaded again.
When this checkbox is checked, DSE Backup Expert Pro will write the files directly to their physical support, skipping the operating system's caches (that is, the files will be written in the write-through mode).
This option is meant to be used by advanced users. Please use it only if you know what you're doing.
When this checkbox is checked, the target files will be inaccessible until they are completely written. This is the default option, and this is the safe way to write data.
However, when the target is a logical or physical volume or a physical drive, you may have to allow access to it while DSE Backup Expert Pro is still writing it.
Allowing access to a target that's still being written is an advanced feature, meant to be used by advanced users. Please use it only if you know what you're doing.
Unchecking this option has the following effects:
Value | Meaning |
---|---|
When writing files | FILE_SHARE_READ | FILE_SHARE_WRITE will be specified when opening the file, allowing both read and write operations to the file while it is being written. |
When writing logical volumes | The volume will not be locked while the backup task runs. Technical details: DeviceIoControl with code FSCTL_LOCK_VOLUME will NOT be called on the volume. |
When writing extended logical volumes | The volume will not be locked while the backup task runs. Technical details: DeviceIoControl with code FSCTL_LOCK_VOLUME will NOT be called on the volume. |
When writing physical volumes | The physical drives hosting the volume will not be taken offline while writing to them. Technical details: DeviceIoControl with code IOCTL_DISK_SET_DISK_ATTRIBUTES and parameter DISK_ATTRIBUTE_OFFLINE will NOT be called on the physical drives hosting the volume. |
When writing shadow copies of volumes | Not applicable here, since shadow copies are read-only. |
When writing physical drives | The physical drive will not be taken offline while the backup task runs. Technical details: DeviceIoControl with code IOCTL_DISK_SET_DISK_ATTRIBUTES and parameter DISK_ATTRIBUTE_OFFLINE will NOT be called on the physical drive. |
Please be aware that writing to a volume or a drive without locking it may seem to be working many times, yet still, the integrity of the file system cannot be guaranteed in these circumstances.
This option should only be attempted for writing to a volume or a drive for which locking is simply not an option (like a volume or a drive which must be kept available at all times).
WARNING: If you don't understand the explanation above, it's better to leave this option checked.
If this checkbox is checked, the target files will be encrypted by the operating system (if it supports file encryption).
Please be aware that such files will only be readable for the current user, or for users for which the current user has granted access to the file encryption certificate.
Please be aware that such files could be permanently lost if the current user cannot log in anymore (lost password, system failure) and if (s)he has not exported the file encryption certificate to a safe location.
Also, note that it is not possible to have a file both encrypted by the operating system and compressed by the operating system at the same time (Windows does not allow this).
If this checkbox is checked, the target files will be encrypted by DSE Backup Expert Pro.
You have to choose an encryption algorithm and an optional hash signature algorithm (used for checking the integrity of the file when decrypting it).
Please be aware that if you lose the password, the data in the encrypted files may never be recovered.
Select the desired encryption algorithm from the dropdown below.
Select the desired (optional) hash signature algorithm from the dropdown below.
Enter the password in this field. The encryption key and the initialization vector will be generated from this password, using the RFC 2898 approach.
WARNING: Passwords are restricted to maximum 4,096 characters! Passwords longer than 4,096 characters will be truncated without other warnings!
Enter the password again in this field. The two passwords must match.
WARNING: Passwords are restricted to maximum 4,096 characters! Passwords longer than 4,096 characters will be truncated without other warnings!
In this page you can see the logs for backup tasks.
This dropdown contains the list of all the log files that were found.
These are the log entry details.
This item allows the definition of an action for a backup task, to be executed before or after the backup task itself.
It also offers button links for these actions: Duplicate, Delete, Move up and Move down.
Choose the desired action type from the dropdown below:
Value | Meaning |
---|---|
Run a backup task | The selected task will be started. |
Run an executable | The selected executable will be started with the selected parameters. |
Open a file | The selected file will be opened. |
Select the backup task to be run from the dropdown below. Note that the dropdown will be empty if you have not created other backup tasks besides this one.
Choose what to do if the selected backup task is already running.
Value | Meaning |
---|---|
Wait for it to finish and then start it again | DSE Backup Expert Pro will wait for the selected backup task to finish and then will restart it. |
Wait for it to finish, then keep going without restart it | DSE Backup Expert Pro will wait for the selected backup task to finish but won't restart it after that. |
Don't run this step | DSE Backup Expert Pro will skip this step and move to the next one. You should not choose this option when next steps depend on this one. |
Stop and restart it | The task will be stopped and then restarted. |
Stop it and keep going without restart it | The task will be stopped and execution of this task will continue without restarting it. |
Enter the full path to the file to be run.
Enter the arguments for the executable here.
Enter the environment variables for the executable here.
Multiple variables can be specified, one per line:
Optionally, you may choose to run the file as another user. If so, enter that other user name here.
Optionally, you may choose to run the file as another user. If so, enter the password for that user here.
WARNING: Passwords are restricted to maximum 4,096 characters! Passwords longer than 4,096 characters will be truncated without other warnings!
Select how you want the local and UTC date and time tag elements to be evaluated when starting this action. The default value is "Current time when this action is started".
You may want to change the default value when you need to generate an identical file name in multiple backup tasks or actions. For example, a task produces a result named files-<LocalDate:>.zip, and you want to use exactly this result file as a source for your next task. You can do this by forcing both tasks to use the same date and time when evaluating the date and time tag elements.
Important terms:
Standalone Mode: a backup task runs in standalone mode if it was explicitly started by the user, or if it was started because it was scheduled to run at a specific time.
Subtask Mode: a backup task runs in subtask mode if it was started as an action of another task (the parent task). In this scenario, the parent task action's settings can dictate the "executing time" for this task and its actions.
Actions Before: all actions in the "Actions to do before this task" list of the current task.
Actions After: all actions in the "Actions to do after this task" list of the current task.
The Task Itself: the current task, excluding the Actions Before and Actions After.
Current System Time: the current time of the system clock.
Task Executing Time (for a task): the date and time used to evaluate tag elements in its sources and targets (not in its actions). This value is determined by the selection in the dropdown below, is calculated immediately before The Task Itself starts executing, and remains the same for all sources and targets in The Task Itself.
Action Executing Time (for an action): the date and time used to evaluate tag elements in the action's properties (e.g. file paths). This value is determined by the selection in the dropdown below, remains the same for a single action, but it may change from action to action, depending on each action's settings.
Value |
Meaning |
---|---|
Current time when this action is started |
This is the default. Action Executing Time is set to the Current System Time when the action starts executing, regardless of the mode the task is running in (standalone or subtask). |
Start of the previous action (or of the task itself, if there are no actions before this one) |
Action Executing Time is set to the Action Executing Time of the previous action, or to the Task Executing Time if this action is the first in the Actions After list. If this action is the first in the Actions Before list, then Action Executing Time is set to the Current System Time (if the task runs in Standalone Mode), or to the value dictated by the parent task's action otherwise. |
Start of the first action (or of the task itself, if there are no actions before this one) |
Action Executing Time is set to the Action Executing Time of the first of the Actions Before. If there are no Actions Before, then Action Executing Time is set to the Current System Time (if the task runs in Standalone Mode), or to the value dictated by the parent task's action otherwise. |
Choose what you want DSE Backup Expert Pro to do after starting this action:
Value | Meaning |
---|---|
Don't wait | DSE Backup Expert Pro will move to the next step in this task. |
Wait till the task finishes | DSE Backup Expert Pro will wait for the task to finish, then will move to the next step. |
Wait till the task finishes, but stop it if not done in | DSE Backup Expert Pro will wait for the maximum amount of time specified below, and it will stop the task if not done in that time. After that, it will proceed to the next step. |
Wait till the task finishes, but leave it running and keep going if not done in | DSE Backup Expert Pro will wait for the maximum amount of time specified below, and it will leave it running in parallel and will move to the next step if not done in that time. |
This item allows the scheduling of a run for a backup task.
It also offers button links for these actions: Duplicate, Simulate and Delete.
Select the days in which you want this task to be run.
Select the time interval in which you want this task to be run. If the task is already running at that time, it won't be stopped and restarted.
Value | Meaning |
---|---|
On selected days, run only once at | The task will be run only once, at the selected time. |
On selected days, start at [...] and run every | The task will be run during the entire time interval, at specified sub-intervals. |
In this dialog you can enter the parameters for a scheduled run simulation.
Enter simulation start time here.
Enter simulation end time here.
This page lists all predefined lists found in the currently loaded settings.
This item displays the main information about a predefined list (like name, description and the first items).
It also offers button links for these actions: Edit, Duplicate and Delete.
In this page you can edit a predefined list, by adding, changing or removing items.
A predefined list's name can only contain letters, digits and the '_' (underscore) character. It must not start with a digit, and it can be maximum 256 characters long.
A predefined list's name is case insensitive, and it must be unique among all the objects in the currently loaded settings.
A predefined list's description can contain any kind of characters. It can be maximum 1,024 characters long.
It should provide a meaningful description of the items it contains. For example: Users on John's computer.
Add or rename an item
Enter the text of the item here. It can be an empty text. Items don't have to be unique, so you can enter the same text twice.
Click "Import..." to import the list items from an external text file.
Click "Export..." to export the list items to an external text file.
This page lists all FTP (File Transfer Protocol) servers found in the currently loaded settings.
This item allows editing the information for an FTP server (like name, description and connection information).
It also offers button links for these actions: Duplicate, Test and Delete.
An FTP Server's name can only contain letters, digits and the '_' (underscore) character. It must not start with a digit, and it can be maximum 256 characters long.
An FTP Server's name is case insensitive, and it must be unique among all the objects in the currently loaded settings.
Examples: my_ftp_server, ftp_mydomain_com, etc.
An FTP Server's description can contain any kind of characters. It can be maximum 1,024 characters long.
It should provide a meaningful description of the server. For example: This is my company's FTP server.
Enter server url or ip here.
For example: myfiles.myserver.com, or 101.202.303.404.
Enter server port here. Usually this is 21 (for unsecured connections) or 22 (for secured connections).
Enter the username here. This may be an email address for FTP servers that accept anonymous connections.
Enter the user's password here. This may be left blank for FTP servers that accept anonymous connections.
WARNING: Passwords are restricted to maximum 4,096 characters! Passwords longer than 4,096 characters will be truncated without other warnings!
Check this to select the passive mode, which should be on by default.
Using the passive mode is preferable, because it works when the app is running behind a firewall, a router or any other device implementing a NAT (Network Address Translation) protocol.
In the active mode, the app starts listening for incoming connections from the server, after informing it on which port it is listening. This option should only be used when the app is not running behind a firewall.
Check this to enforce the connection to be encrypted.
Check this to enable binary file transfer.
Otherwise, files will be transferred in ASCII/text mode.
Check this when the FTP server's file system is case sensitive.
Usually, this is only true for Linux and other Unix-like operating systems, and false for Windows.
Check this when the FTP server also accepts backslash (\) as directory separator, in addition to forward slash (/).
If you're not sure, do not check this.
This page lists all AWS S3 (Simple Storage Service) buckets found in the currently loaded settings.
This item allows editing the information for an AWS S3 bucket (like name, description and connection information).
It also offers button links for these actions: Duplicate, Test and Delete.
An AWS S3 Bucket's name can only contain letters, digits and the '_' (underscore) character. It must not start with a digit, and it can be maximum 256 characters long.
An AWS S3 Bucket's name is case insensitive, and it must be unique among all the objects in the currently loaded settings.
Examples: my_aws_bucket, my_daily_work, etc.
An AWS S3 bucket's description can contain any kind of characters. It can be maximum 1,024 characters long.
It should provide a meaningful description of what it contains. For example: These are the files that I work on every day.
Enter the access key ID here (it is provided by AWS when creating an access key).
Enter the access key secret here (it is provided by AWS when creating an access key).
WARNING: Key secrets are restricted to maximum 4,096 characters! Key secrets longer than 4,096 characters will be truncated without other warnings!
Select the AWS region.
Select the S3 bucket name from the dropdown.
You must select a region first, otherwise the dropdown below will be empty.
This page lists all Microsoft Azure Storage entries found in the currently loaded settings.
This item allows editing the information for a Microsoft Azure storage entry (like name, description and connection information).
It also offers button links for these actions: Duplicate, Test and Delete.
An Azure Storage's name can only contain letters, digits and the '_' (underscore) character. It must not start with a digit, and it can be maximum 256 characters long.
An Azure Storage's name is case insensitive, and it must be unique among all the objects in the currently loaded settings.
Examples: my_files, my_daily_work, Johns_desktop, etc.
An Azure Storage's description can contain any kind of characters. It can be maximum 1,024 characters long.
It should provide a meaningful description of the files it contains. For example: These are the files that I work on every day.
Enter the Microsoft Azure Storage account name here (it is provided by Azure after creating the account).
Enter the key name here, as provided by MS Azure. This is usually 'key1' or 'key2'.
If you don't know the key name, you can leave this blank.
Enter the key value here (it is provided by MS Azure after creating the account).
WARNING: Key values are restricted to maximum 4,096 characters! Key values longer than 4,096 characters will be truncated without other warnings!
Enter the name of the Azure blob container or Azure file share, as defined in the Microsoft Azure portal.
Check this is the Azure Storage is a blob container, not a file share.
It is very important that this checkbox is checked or unchecked correctly, otherwise the upload to Azure won't work.
Also, please be aware that in an Azure blob the file and folder names are case sensitive, while in an Azure file share they are case insensitive.
This page lists all SFTP (SSH File Transfer Protocol) servers found in the currently loaded settings.
This item allows editing the information for an SFTP server (like name, description and connection information).
It also offers button links for these actions: Duplicate, Test and Delete.
An SFTP Server's name can only contain letters, digits and the '_' (underscore) character. It must not start with a digit, and it can be maximum 256 characters long.
An SFTP Server's name is case insensitive, and it must be unique among all the objects in the currently loaded settings.
Examples: my_files, my_daily_work, Johns_desktop, etc.
An SFTP Server's description can contain any kind of characters. It can be maximum 1,024 characters long.
It should provide a meaningful description of the files it contains. For example: These are the files that I work on every day.
Enter server url or ip here.
For example: myfiles.myserver.com, or 101.202.303.404.
Enter server port here. Usually this is 22.
Enter the username here.
Enter the user's password or the user's private key here.
Please be aware that private keys cannot simply be typed or pasted into this field by hitting Ctrl+V; they have to be pasted by clicking the link "Paste private key."
WARNING: This password / private key is restricted to maximum 16,384 characters! Passwords and private keys longer than 16,384 characters will be truncated without other warnings!
Check this when the Password field above contains a user's private key, not a password.
Please be aware that private keys cannot simply be typed or pasted into the field above by hitting Ctrl+V; they have to be pasted by clicking the link "Paste private key."
Check this when the SFTP server's file system is case sensitive.
Usually, this is only true for Linux and other Unix-like operating systems, and false for Windows.
Check this when the SFTP server also accepts backslash (\) as directory separator, in addition to forward slash (/).
If you're not sure, do not check this.
This page lists all email accounts found in the currently loaded settings.
This item allows editing the information for an email account (like name, description and connection information).
It also offers button links for these actions: Duplicate and Delete.
An Email Account's name can only contain letters, digits and the '_' (underscore) character. It must not start with a digit, and it can be maximum 256 characters long.
An Email Account's name is case insensitive, and it must be unique among all the objects in the currently loaded settings.
Examples: my_work_account, my_backup_email, etc.
An Email Account's description can contain any kind of characters. It can be maximum 1,024 characters long.
It should provide a meaningful description of what it is. For example: This is the email account I use for sending files..
Type of email account (SMTP server, or Twilio SendGrid)
Enter email server url or ip here.
For example: mail.myserver.com, or 101.202.303.404.
Enter server port here. For unsecured connections, this is usually 25; for secured connections, this is usually 465 or 587.
Enter the user's email address here.
Enter the user's password here.
WARNING: Passwords are restricted to maximum 4,096 characters! Passwords longer than 4,096 characters will be truncated without other warnings!
Enter the username here. Usually this is the user's email address (entered above).
Enter the user's display name here (e.g. John Doe).
Recipients will see this name (associated with the email address entered above).
Check this to enforce the connection to be encrypted (SSL or TLS).
Use this page to browse files and restore backups.
Select a folder path here.
Select a folder path here.
Use this dialog to select or unselect files.
Enter a wildcard pattern or a regular expression for selecting (or unselecting) files. For example, *.docx.
Check this if the pattern above is a regular expression, and not a simple wildcard pattern (like *.*).
This dialog is displayed in order for the user to confirm the copying of files.
Enter files' target (destination) here.
This dialog is displayed in order for the user to confirm the restoring of files.
Enter the password that will be used when encountering encrypted files. If no encrypted files are restored, this is not needed.
WARNING: Passwords are restricted to maximum 4,096 characters! Passwords longer than 4,096 characters will be truncated without other warnings!
Enter files' target (destination) here.
By default, target content cannot be accessed while DSE Backup Expert Pro is still writing it. However, sometimes you may want to uncheck this (for example, when the target is a drive or a partition), but please be aware that in that case (if you uncheck this option) the integrity of the file system cannot be guaranteed anymore.
This dialog is displayed in order for the user to enter the password and to confirm the decrypting of a file.
Enter the password that was used to encrypt the file (the password set in the backup task settings).
WARNING: Passwords are restricted to maximum 4,096 characters! Passwords longer than 4,096 characters will be truncated without other warnings!
Enter files' target (destination) here.
This dialog is displayed in order for the user to confirm the extraction of files from an archive.
Enter files' target (destination) here.
This dialog is displayed when the user asks to create a new directory.
Enter the full path of the new directory here.
This dialog is displayed in order for the user to confirm the deletion of files and folders.
Check this to force the deletion of read-only, hidden and system files.
In this dialog is displayed the progress of a file operation (copying, extracting, decrypting, etc...).
Percentage of the current file that was processed.
Percentage of the total files that was processed.
After a file operation (e.g. copy), this dialog displays the files for which the operation failed (completely or partially).
Use this page to change the application's settings.
The dropdown below contains a list of the available languages.
If you change this setting, a restart of the app is required for it to take effect.
WARNING: The language, color scheme and zoom settings are not exported or imported with the other settings, nor are they encrypted when you choose to encrypt the app's settings.
The dropdown below contains a list of the available color schemes.
If you change this setting, a restart of the app is required for it to take effect.
WARNING: The language, color scheme and zoom settings are not exported or imported with the other settings, nor are they encrypted when you choose to encrypt the app's settings.
Enter the desired zoom factor in this text box. Acceptable values range from 50% to 200%.
If you change this setting, it will take effect immediately after clicking "Save".
WARNING: The language, color scheme and zoom settings are not exported or imported with the other settings, nor are they encrypted when you choose to encrypt the app's settings.
By default, many text elements have a sensitive help link next to them (🛈). You can hide it by unchecking this option.
If you change this setting, it will take effect immediately after clicking "Save".
If this is checked, the app's settings file will be encrypted by the operating system (provided that it resides on a file system that supports that).
Please be aware that if you cannot log in to this Windows account, and if you did not save the file encryption certificate from Windows, you will lose access to the settings file.
Please be aware that this feature may not work on all editions of Windows. For example, currently it works on Windows 10 Pro, but not on Windows 10.
If this is checked, the app's settings file will be encrypted with a user provided password, using the AES-256 encryption algorithm.
Please be aware that if you lose the password, it can be neither recovered, nor reset, and you will have to reset the settings.
WARNING: The language, color scheme and zoom settings are never encrypted, not even when check this option. Only the other settings are.
Check this if you want your password to be remembered. The password itself will not be stored, but the encryption key for the settings file will saved to disk in a protected way, accessible only to the current Windows user.
Select the location where you want temporary files to be created.
Some backup tasks require no temporary files, but other may require a temporary file as large as the task's sources themselves. Therefore, choose a location on a drive with sufficient free space.
Some sources of files may be marked as containing sensitive or personal information (e.g. a copy of your passport).
If this option is checked, when DSE Backup Expert Pro needs to create temporary files with those sources, those temporary files will be encrypted by the operating system (provided that the temporary files reside on a file system that supports that).
Please be aware that this feature may not work on all editions of Windows. For example, currently it works on Windows 10 Pro, but not on Windows 10.
If this option is checked, when DSE Backup Expert Pro needs to create temporary files, all those temporary files will be encrypted by the operating system (provided that the temporary files reside on a file system that supports that).
Please be aware that this feature may not work on all editions of Windows. For example, currently it works on Windows 10 Pro, but not on Windows 10.
Some sources of files may be marked as containing sensitive or personal information (e.g. a copy of your passport).
If this option is checked, when DSE Backup Expert Pro needs to create temporary files with those sources, those temporary files will be encrypted using a temporary (one time use) key and initialization vector, generated by a cryptographic random number generator, that guarantees both unpredictability and irreproducibility.
Use the dropdown below to choose the desired encryption algorithm.
If this option is checked, when DSE Backup Expert Pro needs to create temporary files, all those temporary files will be encrypted using a temporary (one time use) key and initialization vector, generated by a cryptographic random number generator, that guarantees both unpredictability and irreproducibility.
Use the dropdown below to choose the desired encryption algorithm.
Use the dropdown below to choose the desired encryption algorithm for temporary files that are to be encrypted by DSE Backup Expert Pro (selected in the two check boxes above).
Select the location where you want the application logs to be stored.
Application logs older than the selected number of days will be deleted (provided that the app is running).
Select the location where you want the backup task logs to be stored.
Backup task logs older than the selected number of days will be deleted (provided that the app is running).
If this is checked, DSE Backup Expert Pro will start automatically when the current user logs in.
If this is checked, DSE Backup Expert Pro will be minimized to the notification area (systray) when closed (by hitting Alt + F4, or by clicking X in the top right corner).
Note that if you click Exit the application will exit.
Use this dialog to export the app's settings to an external file.
Enter the full path to the target file here.
Enter an optional password here.
WARNING: You can leave this field blank, but please be aware that your settings may contain various passwords (for server or cloud accounts, etc.), therefore it is highly advisable that you do set a password.
If you do enter a password, the exported file will be encrypted with the AES-256 encryption algorithm.
WARNING: Passwords are restricted to maximum 4,096 characters! Passwords longer than 4,096 characters will be truncated without other warnings!
Confirm the password entered above. The two passwords must match.
WARNING: Passwords are restricted to maximum 4,096 characters! Passwords longer than 4,096 characters will be truncated without other warnings!
Use this dialog to import the app's settings from an external file.
Enter the full path to the source file here.
Enter the (optional) password that was used to export the file. You can leave this blank if the settings were exported without a password.
WARNING: Passwords are restricted to maximum 4,096 characters! Passwords longer than 4,096 characters will be truncated without other warnings!
In this page you can see the application's logs.
This dropdown contains the list of all the log files that were found.
These are the log entry details.
Use this dialog to set or to change the password used to encrypt the app's settings.
WARNING: Passwords are restricted to maximum 4,096 characters! Passwords longer than 4,096 characters will be truncated without other warnings!
Enter old password here.
WARNING: Passwords are restricted to maximum 4,096 characters! Passwords longer than 4,096 characters will be truncated without other warnings!
Enter new password here.
WARNING: Passwords are restricted to maximum 4,096 characters! Passwords longer than 4,096 characters will be truncated without other warnings!
Enter new password here, again.
WARNING: Passwords are restricted to maximum 4,096 characters! Passwords longer than 4,096 characters will be truncated without other warnings!
This page displays the help for the application.
This page displays help for a specific element.
This page displays the update options available for the installed license(s).
This drop down lists all the product updates that are available for the currently installed licenses.
This page displays the End-User License Agreement.
It does not apply to the editions of DSE Backup Expert Pro purchased from the Microsoft Store!
Last updated: November 10, 2020
Enactment date: the moment you download, purchase or use the Application for the first time
General terms
Please read this End-User License Agreement (hereafter referred to as the Agreement) carefully before purchasing, before downloading and before using the DSE Backup Expert software product (hereafter referred to as the Application). Also, please read this Agreement carefully before clicking the "I Agree" button below.
By clicking the "I Agree" button and using the Application, you are agreeing to be bound by the terms and conditions of this Agreement.
If you do not agree to the terms and conditions of this Agreement, do not click on the "I Agree" button and do not use the Application.
This Agreement is between you and Data Safety Expert Company (hereafter referred to as the Company), and governs your use of the Application and the services it connects to.
License
The Company grants you a revocable, non-exclusive, limited and restricted transferable license to download, install and use the Application, strictly in accordance with the terms of this Agreement.
Restrictions to Selling the Application
If you purchased a fully paid, non-discounted license, you may freely choose to sell only that license to anyone you want, for whatever price you want, or give it away for free (as a gift), as long as the buyer or receiver accepts this Agreement. You acknowledge that the Company is not required to update its records to indicate that said license belongs to some other entity, and you will still be listed in our database as the owner of the license.
If you purchased your license at a discounted non-zero price, you may only sell it or give it away freely as a gift after the passing of full 5 (five) calendar years after the date of purchase.
Free (trial) licenses are permanently non-transferable. If you have a free (trial) license, you cannot sell it, rent it, nor give it away as a gift to any other third party.
Exception to the Restrictions to Selling the Application
If you’re a company or any other kind of legal entity, and you are purchased by some other entity, or legally merge with another entity, then this license can legally be included in the above-mentioned transaction, regardless of the price it was acquired for. This exception includes free (trial) licenses, too.
Restrictions to Renting / Leasing the Application
You agree that you will not license, rent, lease, distribute or transmit the Application to any third party, unless you have an express written permission from the Company. Permanently selling your own license is permitted in some cases, see previous section.
Other restrictions
You agree that you will not reverse engineer the Application.
Commercial use
You can use the Application for commercial purposes, as long as these purposes don’t include renting, leasing or selling the Application without an express written permission from the Company. This also applies to free (trial) licenses.
Modifications to the Application
The Company reserves the right to modify the Application or any service to which it connects, with or without notice and without liability to you.
Disclaimer
You acknowledge that the software is provided "as is", without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and noninfringement.
Neither the Company, its licensors of affiliates, nor the copyright holders make any representations or warranties, expressed or implied, including but not limited to the warranties of merchantability, satisfactory quality, fitness for a particular purpose, accuracy, enjoyment and non-infringement of third-party rights.
There is no warranty by the Company or by any other party that the functions contained in the Application will meet your requirements or that the operation of the Application will be uninterrupted or error-free. You assume all responsibility and risk for the use of the Application to achieve your intended results.
In no event shall the Company, the authors, sellers, re-sellers or copyright holders be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from, out of or in connection with the software or the use or other dealings in the software.
Term and Termination
This Agreement shall remain in effect until terminated by you or by the Company.
The Company reserves the right to suspend or terminate this Agreement and your license to use the Application at any time, without any compensation and without any liability to you, with or without prior notice, if the Company considers, in its sole discretion, that you fail to comply with any provision of this Agreement.
You may also terminate this Agreement at any time, without any prior notice, by deleting the Application and all copies thereof from your computer(s). You acknowledge that in this case the Company shall not pay any compensation to you.
Upon termination of this Agreement, you shall cease all use of the Application and delete all copies of the Application from your computers.
Severability
If any provision of this Agreement is held to be unenforceable or invalid, such provision will be changed and interpreted to accomplish the objectives of such provision to the greatest extent possible under applicable law and the remaining provisions will continue in full force and effect.
Amendments to this Agreement
The Company reserves the right, at its sole discretion, to modify or replace this Agreement at any time. If a revision is material, we will provide at least 30 days' notice prior to any new terms taking effect. What constitutes a material change will be determined at our sole discretion.
Contact Information
If you have any questions about this Agreement, please contact us.