- Planning the conversion
- Conversion requirements
- Conversion instructions
- Override conversions
- Important note on antivirus exclusions
- Advanced StorageServer settings
Before conversion, check the client version and review the following with the customer:
1. Commercial arrangements
For example, ESE removes the requirements for any plugin licencing, which may prove problematic to resellers.
2. OS compatibility
Mac, Windows Server 2003 and 2008 (non-R2) and earlier, and versions older than Windows 7 are not supported for conversion. The following OSs are supported:
- Windows 7: 32- & 64-bit
- Windows 8.1: 32- & 64-bit
- Windows 10: 32- & 64-bit
- Windows Server 2008 R2: 64-bit only
- Windows Server 2012 (incl. R2): 64-bit only
- Windows Server 2016 Standard
The following OSs cannot be converted from SE to ESE, but you can create fresh backup accounts for ESE to backup the data again:
- Ubuntu 16.04 LTS: 32- & 64-bit
- Red Hat Enterprise Linux 6
- Red Hat Enterprise Linux 7.3: 64-bit only
- CentOS 7: 32- & 64-bit
3. Transfer of applications
The following applications can be transferred during conversion without any reconfiguration:
- MS SQL (through VSS): 2012 (incl. R2), 2014 (Express), 2016 (Express)
- SIMS, FMS, Discover
- System State
Note: SE System State backup maps to ESE Windows Image Backup System State only backup (see below), which leverages the Microsoft feature and takes a long time. We recommend using the remote tunnel to turn off Windows Image Backup and turn on System State or Full System Backup instead.
The following applications cannot be transferred during conversion, but can be deselected in SE and then reselected and reconfigured in ESE:
- Exchange (through VSS): 2010, 2013, 2016
- Hyper-V: Windows Server 2012
- Oracle RMAN
- Script Plugin
- SQL Dumping plugin (can be replaced by VSS or Script Plugin)
- Windows Image Backup
The following applications cannot be transferred during an account conversion:
- VSS (aside from MS SQL)
4. Transfer of settings
The following settings can be transferred:
- Account limits
- Bandwidth throttling
- Binary patching (will be converted to ESE's built-in equivalent to delta patching)
- Command Line Support (can be achieved with PowerShell and REST calls)
- Email notification
- Password prompt (ESE v17.5 and later)
- Proxy settings
- SE Remote Management (will be converted to Remote Access in ESE)
- SE Staged Backup (will be converted to Transfer Deduplication in ESE)
The following settings cannot be transferred during conversion:
- Backup Operator mode (has been superseded by ESE's built-in equivalent)
- CPU and disk throttling
- Enforce minimum disk space
- Find button
- Mandatory patching
- Multiple backup sets
- Payload limit
- Segment and cycle backup
- SOCKS proxy server
- VPN/dial-up connection
5. Upgrading of the Storage Platform
Storage Platforms must first be upgraded to from v7.14 to v8 and then onto v16 or later. Upgrades from v7 to v16 are not recommended. See detailed upgrade paths here.
If the customer is running a v7 Storage Platform, Virtual Restore will be lost for all SE clients if the platform is upgraded beyond v7. If all clients are to be converted to ESE, this will not pose a problem since they will be able to use InstantData. However, any clients that remain on SE will lose the feature.
The following is required for successful conversion from SE/DL to ESE:
- The Account's SE/DL Agent must be upgraded to the latest release, and must have done at least one backup so that the key conversion information will have been updated on the Storage Platform. This ensures that eligibility for conversion can be checked. (Instead of performing a backup, you can also use the Retrieve Settings button in the Agent to send conversion information to the Storage Platform.)
- The upgrade process from SE to ESE requires the account to be converted from the Console first. You therefore need Storage Platform Administrator or Group Administrator permissions for the Console.
- The latest ESE Agent updates must be installed on the Storage Platform.
- To carry over the VSS SQL Server plugin, select its node only and not its parent, i.e. this:
and not this:
- The Windows service for the Agent must be running for the auto update to be initiated.
- There must be an ESE licence available in the Account's Group.
- There must be at least 1GB of RAM available on the StorageServer for every 1 million files in the Account that is to be converted, over and above the minimum 4GB required by normal StorageServer operation.
- There must be sufficient disk space on the StorageServer containing the Accounts that are to be converted, i.e. 10% more than what is currently used by the Account in question.
- The customer needs to know their encryption keys and testing is highly recommended. If the encryption keys are not known, they can either be tested with the Encryption Key Checker or obtained using the Group Certificate.
- You need to leave enough time to perform manual uninstallation and reinstallation of clients in case this is required (see below).
1. Perform the necessary upgrades:
- Upgrade the Storage Platform and Console to the latest version.
- Install the latest versions of the SE/DL and ESE Agent updates on the Storage Platform.
- Ensure that the applicable SE/DL Agents are up to date.
- Perform a backup on the SE/DL Agent or use the Retrieve Settings button in the Agent to ensure that conversion information is sent to the Storage Platform.
2. Convert your Accounts:
- Once conversion information has been sent, log into the Console as a user with Storage Platform Administrator or Group Administrator permissions.
- In the Account Management view, expand the Account Management tree and select the group containing the SE/DL Account(s) to be converted.
- Select one or more Accounts. (Multiple Accounts can be selected by holding in the CTRL key while left-clicking each Account.)
- Right-click one of the selected SE/DL Accounts to bring up the context menu.
- Select Advanced and click Convert Data to ESE Format. This will initiate a conversion wizard.
- Once the Account has been converted, the SE/DL Agent will automatically be upgraded to ESE at the next auto update check.
- Completed account conversions can be viewed in Enterprise Reports\Other\SEtoESEConversion.html
3. Convert unsupported applications and settings:
- Remove the application/s or disable the setting/s in SE, run a single backup, and then convert the account. The account and client should then both convert, with ESE being installed automatically as normal.
- The customer then needs to configure ESE to add back the application and/or apply the desired settings.
- Data from unsupported applications will be visible for restores, and can be restored to the application manually as file data.
- Profiling of settings can be transferred, but only if there is a direct match between SE and ESE (e.g. file selections). Options like turning off the backup transmission randomisation time in DL would not apply if an Account is converted, as they do not exist in ESE.
- Testing on a test client is always recommended.
If the Console shows an error and does not allow the conversion, you can override the warning logic and still convert the Account. However, this requires manual uninstallation of SE followed by manual installation of ESE, which can be time-consuming if performed on multiple Accounts. Stopping the service and copying the SE installation is recommended prior to uninstallation.
Although such conversions are possible, the following is not supported:
- Windows Backup Operator accounts
To convert an Account, launch the Console from the command-line using
When the client-side paths change, the antivirus exclusions also need to change. (This is compulsory for all manual SE to ESE conversions.) All ESE clients will need to add the new default installation path C:\ProgramData\Redstor Pro\Backup Client ESE (or the equivalent brand) to their exclusion list.
Certain advanced actions can be performed for all accounts on a StorageServer by editing the following settings in the StorageServer's settings.xml file (default location C:\ProgramData\Redstor Backup Pro\SS_Service):
1. By default, the setting
VerifyConvertedBackups is set to "True", which means a verification will be run on each of the converted backups.
2. To create a backup copy for each of the accounts before conversion starts, set
MakeBackupCopyBeforeConvert to "True". Note that this cannot be done on a per-account basis. While
MakeBackupCopyBeforeConvert is set to "True":
- If data verification on an account succeeds, the backup copy will remain available. The admin will need to manually delete the copy if it is not needed.
- If data verification fails, the backup copy will become obsolete and will be deleted automatically. The account will remain in SE/DL format, and any ESE data or indices that were created in the conversion attempt will be removed by the IntegrityCheck that automatically runs at the end of the conversion.
3. To facilitate the reversion of accounts from ESE to SE/DL, set
RestoreBackupCopyIfConvertingAgain to "True". Reversion entails the replacement of a converted account with its original SE/DL format and must be done manually by the admin. This is useful in case issues are observed with the converted account. If the admin then queues a second
ConvertData task for the converted account while
RestoreBackupCopyIfConvertingAgain is set to "True", the account will be reverted to SE/DL. Note that a backup copy of the account must be present for reversion to be possible.