Note: To deploy a new custom MSI, you need to have the latest client auto updates installed. See Article 1168.
1. In the Storage Platform Management Console, go to the Account Management view.
2. Right-click Storage Platform at the top of the account tree and click Add Group or Collection.
3. In the dialog box that appears, keep Backup Group selected and click Next.
4. Name the group (here "Installs") and specify a create key (password) for it. Set a group storage limit and default account size - your Redstor account manager can advise you on best practices. Click Finish.
5. In the Configure Group dialog box that pops up, go to the Licences tab. Add an Enterprise Server Edition backup client licence to your group by clicking on Enterprise Server Edition, and using the number field and Add button at the bottom. Click OK when you're done.
1. In the Console's Account Management view, right-click the name of your backup group and click Deploy. This will launch the Deployment Wizard.
2. Select a licence for the backup client, as well as an architecture (32-bit or 64-bit), and click Next.
Note: If multiple versions of the client are required, the deployment should be run multiple times.
3. Confirm that the new backup account created with this MSI will use the backup client host machine as its account name (this is the default).
4. Specify the default backup time.
5. Continue through the dialog boxes for Filter & Masks and Exclusions, making specifications as required, e.g. file types that should not be backed up.
6. In the Installer dialog box, keep the first user interface option (Only allow installation folder customisation) selected, and keep the language to Same as operating System.
7. In the Custom Backup Client Settings dialog box, in the Custom MSI (installer) field, specify PREPACCOUNT=YES and supply a password and an encryption key. The password must have a minimum of 4 characters and the encryption key a minimum of 8 characters.
- Important note on security: If you are not comfortable with passwords and encryption keys being stored in the MSI, these can also be randomly generated. Simply omit the details from the Custom MSI (installer) field. Ensure that you have configured a group certificate, and recover the encryption keys as described here. If you do not recover your encryption keys, you will have no record of your encryption keys, and will be unable to reconnect to your backup accounts.
The Custom MSI (installer) field will now contain three lines, as below:
8. Enter a custom a5backup.properties file in the last text field. This will enable you to configure more options, as shown at the end of this article.
9. Click Build to create the MSI.
10. Once the MSI has been created, copy the file to a directory on its host machine.
11. Install the MSI to create a backup account. You can do a test backup or wait for the first backup as determined by the backup schedule. To ensure that your backups run, select at least one file for backup using the ESE client. If no backup selection is included in the MSI, backups will not run.
Custom backup client options
The following settings can be added to a custom a5backup.properties.
Note: If supplying a custom a5backup.properties file, note that the settings will take precedence over any conflicting settings configured in the Deployment Wizard. It is advised that you test each new option individually to ensure that no conflict occurs with the Deployment Wizard.
Default daily automated backup schedule
For example, from the installation directory run:
cli.bat :schedule set Monday 15:00,16:30,17:15
The command can be repeated for different days of the week, eg
cli.bat :schedule set Monday 12:00
cli.bat :schedule set Tuesday 12:00
cli.bat :schedule set Wednesday 12:00
The advanced schedule is automatically enabled when these commands are used, and does not need to be specifically set.
Email notification settings (the SMTP authentication password needs to be in hashed format, and can be copied from a working installation)
notify.append.suffix=encountered, Please check Log
Old Article ID: 221
Posted: 01 Mar, 2013 by Flood A.