1. Post Migrating the application to a different server, do I need a new license key?

Ans: Not required. The license key will be applied to the instance already, and reapplying the license key is not required in this case. Reapplying license key is needed when licensed items are upgraded or license key is renewed.

2. Is there any downtime during migrating the application to a new location?

Ans: Yes. Downtime has to be planned during this activity as the application has to be shutdown until migration is completed. However, agent-based log collection still happens in the agents if Enable Offline log collection is enabled in Agent Settings

3. How long should I plan for downtime for migrating application to new server?

Ans: Migrating the application to a different location is a copy-paste action that consumes time based on disk read and write speed.

4. Any suggestion to perform migration to a different location with less downtime?

Ans: If you are migrating to a different server, one option is to move the disk image to another instance in the case of virtual machines, or relocate the physical drive to another server for physical environments. This can help reduce downtime, especially when dealing with large data volumes. For even lower downtime, consider approaches such as storage replication, snapshot-based migration, or database/application replication with a planned switchover.

5. Can I delete the older version post migration?

Ans: Yes, Once you validate and confirm the new instance running stats, you are good to delete the older instance post migration.

6. What are the post migration steps to be performed?

Ans: Different drive in the same server : No post migration action to be taken

Migration performed to a different server:

• If you have enabled log forwarding from any Linux, Unix, router, switch, firewall, or syslog devices to EventLog Analyzer, you would need to re-point them to the new server.

• If an agent has been configured for any device, check whether it has been modified appropriately using the following steps.

Windows agent   

1. On the client machine, open regedit.msc and set the path to:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ZOHO Corp\EventLogAnalyzer\ServerInfo

2. Update the ServerIPAddress and ServerName values.

3. Open Services.msc and restart the ManageEngine EventLog Analyzer agent service.

Linux agent   

1. On the client machine, open <EventLog Analyzer Agent Home>\conf and edit the serverDetails file to update the SERVER_NAME and SERVER_IPADDRESS values.

2. Execute service auditd start and service auditd stop from a terminal.

7. Can I migrate my instance to cross functional OS ? ( Windows to Linux or Linux to Windows)

Ans: No, as there are differences in functionalities and usage of files this would not be possible. However, you can contact support to share your requirements to check on the feasibility plan based on your configuration & setup.

8. Can I migrate the collected live/ES/Elasticsearch data and EventLog Analyzer archive logs to another location?
   My Storage drive is getting full. Can I move the data to someother location?

Ans: Yes, you can migrate the data and re-point the data to different location instead of migrating the entire application. Refer Data Migration for step by step instruction.