For previous versions, see article 845.
In order to facilitate upgrading existing Server Edition (SE) Backup Clients to Enterprise Server Edition (ESE), existing SE Backup Accounts on the Storage Platform can be converted to the data format used by ESE.
Some limitations exist that will prevent an SE Backup Account from being converted.
- Plug-ins. If the SE Backup Client of the Account has these plug-ins:
- MS SQL Server (non-VSS)
- SIMS (can be converted from v17.5)
- Other legacy/unsupported plug-ins (see the System Requirements Compatibility Matrix for supported plug-ins and the Upgrade Paths article for discontinued ones)
Plug-ins in use and configured (not just installed):
- System State (using WSB)
- Settings. Some settings cannot be carried over to the ESE Backup Client:
- Using a SOCKS proxy server
- Using a VPN/dial-up connection
- Using multiple backup sets
- Using staged backups (will be converted from v17.10)
- Using remote management
- SE installed in Backup Operator mode
- Operating system compatibility. If the operating system of the Account’s Backup Client currently resides on an operating system not supported by ESE.
- The SE Backup Clients of the Accounts in question have to be upgraded to v16.12 or later and having done at least one backup so that key conversion information is updated on the Storage Platform.
Note: This ensures that eligibility for conversion can be checked.
Tip: You can also use the Retrieve Settings button in the Client instead of performing a backup to send conversion info to the Storage Platform.
- The ESE Backup Client updates for v16.12 or later must be installed on the Storage Platform.
- The Windows service of the Backup Client must be running for the auto-update to be initiated.
- You'll need Storage Platform- or Group Administrator permissions in the SP Console to access the menu item mentioned in the steps below.
- Ensure that you have at least 1GB of RAM available on the StorageServer for every 1 million files in the Backup Account that is to be converted.
Note: This is over and above the minimum 4GB required by normal StorageServer operation.
- Because of Step 3 mentioned below (under How it works), ensure that sufficient disk space is available on the StorageServer containing the Accounts that are to be converted – 10% more than what as currently used by the Account in question.
Note: Post conversion, the SE-format Account data is deleted leaving behind only the new ESE data.
To perform the prerequisite upgrades:
- Upgrade the Storage Platform to v16.12 or later.
- Upgrade the Storage Platform Console to the same version.
- Install the same version of SE and ESE Client updates on the Storage Platform.
- Ensure that the applicable SE Backup Clients are upgraded to that version.
- Perform a backup on the SE Client or use the Retrieve Settings button on the Client to ensure that conversion information is sent to the Storage Platform.
To convert Backup Accounts:
- Once conversion information has been sent (as described above), log in to the SP Console with a user that has Storage Platform or Group Administrator permissions.
- In the Account Management view, expand the Account Management tree and select the Group containing the SE account(s) to be converted.
- Select one or many Backup Accounts. (Multiple Accounts are selected by using the “CTRL” key while left-clicking each Account.)
- Right-click one of the selected SE Accounts to bring up the context-menu.
- Select the Advanced menu option, and click Convert Data to ESE Format.
A wizard will be initiated guiding you through the rest of the process. Take note of the prompts and requirements displayed on the screen.
Once the Account has been converted, the SE Client will automatically be upgraded to ESE at the next auto-update check.
- The SE-format Account data is deleted leaving behind the new ESE-format data.
- ESE licences will automatically be allocated to newly converted ESE Accounts’ Backup Clients once an Account has been converted - the SE licences will be "refunded" to the owning Group. However, it is recommended that you allocate the appropriate number of ESE licences to affected Backup Groups for effective Storage Platform licence maintenance.
- All other applicable settings will have been converted to an Enterprise Server Edition equivalent.
When the conversion of an Account is initiated, a new task on the Storage Platform is started. This task will sequentially convert each Account in the selected list, one after the other.
At a high level, the process is as follows:
a) The Account data is converted from SE to ESE format
- Several checks are done to ensure the SE Account can be converted. (see Restrictions and Prerequisites above)
- The Account is prepared by checking data integrity.
- Backup indexes and files are converted to the new ESE format (SE Account data is still preserved).
Note: This uses additional disk space on the affected StorageServer.
- At this point the Account is also disabled and locked to prevent any other tasks, like backups and restores.
- Once the conversion has taken place the data is verified with another Quick Integrity Check.
Note: The “conversion” task on the StorageServer can no longer be cancelled.
- The original SE-format Account data is deleted, an ESE licence is reserved on the Backup Group, and the ESE Backup Client will be able to connect to the converted Account.
- If a MirrorServer is affected by this Account, a conversion task for the relevant Account is immediately performed on the MirrorServer.
b) The Backup Client is automatically upgraded to ESE
- Once the Account has been converted, the SE Client will automatically be upgraded to ESE at the next auto-update check.
Note: As mentioned above (see Prerequisites), the SE Backup Client must be on v16.12 or later for the automatic upgrade to take place.