Please enable JavaScript to view this site.

UC Module

Linux based servers do not include manually created folders in the backup or restore processes. Instead you need to copy any additional folders manually.

For example, if a folder containing custom prompts for use in call flows was created separate from the default language folders, that server does not automatically backup or restore that folder. To resolve this, you must backup and restore the additional folder manually. The following example copies a folder called Custom from an existing server to create a backup.

To manually backup a custom folder:

1.Using an SSH file transfer tool, copy the folder Custom from /opt/vmpro to your PC to create a backup of the folder.

To manually restore a custom folder:

1.To restore the folder, again using an SSH file transfer tool, copy the folder to the /home/Administrator folder on the server.

2.Using the SSH command line, you now need to copy the Custom folder from /home/Administrator to the /opt/vmpro folder.

a.Login to the system's command line interface using the existing root user password. You can only does this directly on the server. Root access is not supported on remote connections.

a.At the Command: prompt, enter login.

b.At the login: prompt enter Administrator.

c.At the Password: prompt, enter the password for the user entered above.

d.To launch the Avaya command ine interface, enter /opt/Avaya/clish.

b.Enter admin. At the password prompt enter the admin password. The prompt should change to Admin>.

c.Enter root. At the password prompt, enter the current root user password.

d.When logged in, the prompt changes to something similar to root@C110~.

e.Change directory by entering cd /home/Administrator.

f.Move the Custom sub-folder to /opt/vmpro by entering mv Custom /opt/vmpro.

3.Using the SSH file transfer tool again, verify that the Custom folder has been copied to /opt/vmpro as required.


Performance figures, data and operation quoted in this document are typical and must be specifically confirmed in writing by Avaya before they become applicable to any particular order or contract. The company reserves the right to make alterations or amendments at its own discretion. The publication of information in this document does not imply freedom from patent or any other protective rights of Avaya or others. All trademarks identified by ™, ® or © are registered trademarks or trademarks respectively are the property of their respective owners.

Use of this site indicates acceptance of its cookies and analytics, and acceptance of the Avaya privacy policy.

© 2023 Avaya
Issue 17.a.-
Wednesday, January 4, 2023