Server Edition R.11.1.2.3 - Restore issues

[Marcin Stasiek]

Hello

I have virtual (VMWare) IPO Server Edition and I have to move it to another - fresh deployed virtual machine (Hypervisor can't merge current VM).
So I deployed another AppServer for backup/restore purposes and I created backup of my IP Office using SFTP. Now I try to restore backup on the new deployed IPO VM (ignited and pre-configured with the same IP Address and Hostname). When I choose "Restore" the IPO Server makes reboot and no data is restored. After reboot WebManager stops working (IP Office Service is not running).
Reffering to some AVAYA SR I changed all passwords to remove any special characters.
I have no more ideas. Maybe someone had similar problem?
I'll be grateful for any help.

Regards

 

[joul]

Could be that the system ID still will be different so the backup is not valid for the new machine

I haven't found any practical use for backup restore server when it is not EXACTLY the same server you are restoring to....

A tip for the brave hearts:

Personally I have found that I trust the non-Avaya approach better: (Works every time for me, but no guaranties! Try in lab first)

Used this several times. Saved us hours, if not days, of critical down-time for a customer where an upgrade failed and bricked the old server. And Avaya support could not solve it by asking for the usual config files and log files... Avaya said that this method was not recommended but I prevailed and had IT to fire up a new machine and I had the system up within a few hours.
[ul]
[li]Export Configuration from the old server and use most of the data in a modified Configuration.csv to import to the new machine.[/li]
[li]If you are using Nodal licencing, move licenses for this host ID in PLDS, You can create a new Host ID in the process. (You are allowed to move licence host 9999 times per customer)[/li]
[ul]
[li]Upload the new licence file to the new server.[/li]
[/ul]
[/ul]

Modifying the Configuration.csv: (This example using a Windows PC where Excel saves as CSV with commas, not semicolons)
1. first open the csv file with Notepad (not excel).
2. replace all Semicolons with a non used character for example the paragraph: § (IPO can have ";" in Lines and Short codes and we do not want excel to scramble the column positions!)
3. save the file.
4. Open the CSV in Excel.
4 a. Remove segments you don't want to upload to the new server.
4 b. Keep segments like
[ul]
[li]Line_Info_Start - to - Line_Info_End[/li]
[li]Extension_Info_Start - to - Extension_Info_End[/li]
[li]User_Info_Start - to - User_Info_End[/li]
[li]HuntGroup_Info_Start - to - HuntGroup_Info_End[/li]
[li]ShortCode_Info_Start - to - ShortCode_Info_End (only keep the non-default shortcodes)[/li]
[li]UserRestrictions_Info_Start - to - UserRestrictions_Info_End[/li]
[/ul]
4 c. Keep the column headers for each segment but remove the unique "_Guid" numbers for respective Line, Extension, User etc. (These ID-s will be auto-created in the new server)

5. Save the CSV file again. Also save as excel file if you need to fiddle more.

6. Open the CSV with notepad again.
7. Change back all the § characters to ; (semicolons) again.
8. Note that on each row with XXXXXXX_Info_Start and XXXXXX_Info_End there are now following commas which comes from Excel. Remove these commas.
9. save the file. Import this Configuration.csv to the new machine. Check status. Ensure licencing is valid.