For later versions, see article 904.
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. Only then can the newly installed ESE Backup Client connect to the same account.
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:
- The Account is prepared by purging any partial backups and running a quick integrity check to correct any data discrepancies. (The “conversion” task on the StorageServer can still be cancelled.)
- Backup indexes and files are converted to the new format resulting in “duplicate” copies. (The “conversion” task on the StorageServer can not be cancelled.)
Note: This uses additional disk space on the affected StorageServer.
- At this point the Account is also disabled and locked to prevent any other Storage Platform tasks from being performed on it, such as backups.
- Once the conversion has taken place the data is verified with another quick integrity check.
- The original SE-format Account data is deleted, an ESE licence is reserved on the Backup Group, and the ESE Backup Client is able to connect to the converted Account.
- If a MirrorServer is affected by this Account, a conversion task for the relevant Account will be performed immediately.
Limitations exist that will prevent an SE Backup Account from being converted:
- Plug-ins. If the Backup Client of the Account uses plug-ins that are not provided or supported in ESE.
The following plug-ins will not prevent the Account from being converted:
- Email Notification (Plug-in ID 19)
- Script [(Plug-in ID 20)
- VSS [(Plug-in ID 29)
- System State (using WSB) (Plug-in ID 36)
- UNC (Plug-in ID 100)
- Workspace (Plug-in ID 1000)
Take note of the prompts on the screen. All data, however, will still be accessible for restores from the Backup Client after the Account has been converted.
- Operating system compatibility. If the operating system of the Account’s Backup Client currently resides on an operating system not supported by ESE.
- 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 2 mentioned above, 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 convert Backup Accounts:
Note: You'll need Storage Platform or Group Administrator permissions to access the menu item below.
- In the Account Management view, expand the Account Management tree and select the Group contain 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 the Account.)
- Right-click a selected SE Account 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.
- 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.
- In cases where the supported operating system cannot be confirmed, the conversion can be forced. See this article for details.