Syneto HYPER appliances are available with two operating systems:

• SynetoOS 4: on HYPER Core appliances G2, G3 and G3+
• SynetoOS 5: on HYPER Edge G2 and HYPER Core appliances G4 and G5

These operating systems are not compatible due to different software architectures.

There are situations where end-users needs to:

• Ensure compatibility between HYPER appliances of different generations (e.g. HYPER Core G3 with G4);
• Maximize the investment in HYPER Core G2, G3, G3+ appliances by prolonging the usage lifetime of the platform;
• Benefit from the newer functionalities and improved security on the SynetoOS 5 platform

To address the situations above, end-users should migrate their data from SynetoOS 4 to SynetoOS 5, proceeding as follows:

• Run a command line tool on SynetoOS 4, to perform checks and gather information required by the migration;
• Install a new controller VM running SynetoOS 5 on the appliance;
• Export the storage pool from SynetoOS 4 and import it into SynetoOS 5;
• Import the prepared end-user data;
• Configure SynetoOS 5 for production;
• Remove SynetoOS 4 from VMware ESXi.

Prerequisites

Ensure the following prerequisites are met before starting:

Supported platforms

The migration is possible on the following platforms:

* For HYPER Core G2 only, each platform must be evaluated to comply with Syneto hyperconverged reference architecture.

Obtain a migration license

To perform the migration, each appliance requires an activated migration license. Contact your Syneto Account Manager to order migration licenses.

Before a migration begins, a valid license must be paid and activated on the HYPER appliance S/N (see paragraph “Activate a migration license”).

Activate a migration license

To activate a migration license and assign it to a specific HYPER device, you need to submit a new support ticket to Syneto Customer Support, providing the following information:

• HYPER appliance serial number
• Activation code received from the distributor

When purchasing a migration license, you will receive an activation code from your distributor along with your invoice.

Download SynetoOS 5 OVA file

Step 1. Connect to Syneto Central

Step 2. Click on Migrate to SynetoOS 5

Step 3. Click on Download OVA button

Migration procedure

1. Pre-migration checks

Step 1. Login to S 4 GUI

Step 2. Make note of network information (IP address, subnet mask, gateway and DNS)

Step 3. Check SMB shares (if present) and migrate data to another solution

Step 4. Check Volumes (if present) and migrate data to another solution

Step 5. Check Virtual Machines to retrieve the number of VMs to migrate

Step 6. Check Datastores:

1. Ensure that each datastore contains at most one VM
   
    
2. Verify that no VM has virtual disks on more than one datastore and take the recommended actions

Step 7. Check the number of Recovery Points

It is recommended to have between 1000-1500 recovery points for an efficient data migration.
 

• Connect to SynetoOS 4 controller VM through SSH

ssh admin@<your_ip_address_or_hostname>

• Exit the Syneto shell (if active)

[Config:syneto-host]$ un sh

• Check the number of recovery points on the appliance

zfs list -t snapshot -o name |wc -l

EXAMPLE OUTPUT

In this example, the number of recovery points on the system is 505.

Step 8. Login to VMware ESXi GUI (replace <your_ip_address_or_hostname> with the correct ip/hostname)

https://<your_ip_address_or_hostname>

Step 9. Check if the SSH service is enabled

Step 10 (optional). Enable the SSH service (if it's not already enabled)

Manage → Services

Look for the TSM-SSH service. Select the service and press Start.

Step 11. Check if VMware ESXi is managed by a vCenter server

Step 12 (optional). Disconnect VMware ESXi from the vCenter server (if it's managed by a vCenter server)

Host → Actions → Disconnect from vCenter Server

Step 13. From the SynetoOS VM, click on Edit Settings

Step 14. Make note of which PCI devices are configured on the VM

IMPORTANT
The same PCI device(s) must be added later to the newly installed SynetoOS 5 VM.

EXAMPLE

In the example above, the PCI device named “Fusion-MPT 12GSAS SAS3008 PCI-Express” will need to be added to the new SynetoOS 5 VM.

2. Deployment of SynetoOS 5 virtual appliance

Step 1. Deploy SynetoOS 5 virtual appliance ("How to deploy SynetoOS 5 virtual appliance")

Step 2. Set up the same configuration as on SynetoOS 4

• Configure the network adapters to be identical with SynetoOS 4 VM configuration
   
• Add all the same PCIe devices to SynetoOS 5 as those identified in SynetoOS 4
  
  
  
  

HYPER 2000 specific activities

In case you are migrating on a HYPER 2000 appliance with a hybrid pool (HDD only), add an 8GB virtual disk to SynetoOS 5.

3. Prepare SynetoOS 4 migration

Step 1. Login to SynetoOS 4 GUI

Step 2. Shutdown all VMs hosted by SynetoOS 4

Step 3. Access the Pools page (Wheel menu → Pools)

Step 4. Select the hybrid pool

HYPER 2000 specific activities

In case you are migrating on a HYPER 2000 appliance with a hybrid pool (HDD only), remove the Write acceleration drive from the hybrid pool.

Step 1. Click on Manage, next to Write acceleration

Step 2. Click on Clear to remove the drive

Step 3. Click Update to save the pool structure

HYPER 3000 specific activities

In case you are migrating on a HYPER 3000 appliance, remove the Spare drive from the hybrid pool.

Step 1. Click on Manage, next to Spares

Step 2. Click on Clear to remove the drive

Step 3. Click Update to save the pool structure

HYPER 4000 specific activities

In case you are migrating on a HYPER 4000 appliance, remove the Write acceleration drive from the flash pool (if it exists).

Step 1. Click on Manage, next to Write acceleration

Step 2. Click on Clear to remove the drive

Step 3. Click Update to save the pool structure

4. Run the survey tool on SynetoOS 4

Step 1. Connect to SynetoOS 4 controller VM through SSH

ssh admin@<your_ip_address_or_hostname>

Step 2. Exit the Syneto shell (if active)

[Config:syneto-host]$ un sh

Step 3. Download the survey tool on SynetoOS 4 system

wget https://storage.googleapis.com/syneto_public_files/downloads/Syneto-Tools/Migration/survey.py

Step 4. Run the survey tool

python3 survey.py

Step 5. Wait for the survey tool to successfully complete (about 30 seconds)

Completed collection of SynetoOS migration metadata
Generated: /flash/migration_data_SY2400990099_2024-11-01_10-12-50.tar.gz

Step 6. Once the survey is complete, a file named migration_data_<serial>_date_time.tar.gz is created on each identified pool.

You can run the survey tool multiple times. Each time a unique file will be created. The last file created will be used for migration.

EXAMPLE OUTPUT

Collecting SynetoOS migration metadata
 Survey ...
 Firmware Version ...
 Product license ...
License validation failed, to complete the upgrade, please purchase an OS5 upgrade license
 Networking ...
 DNS ...
 Hypervisors ...
 Replication targets ...
 Datasets ...
 Protected objects ...
 Virtual ecosystem ...
 Protection schedules ...
 SSH key-pairs ...
 Email alerts ...
Found 3 shares and 1 volumes

SMB/AFP Shares
ATTENTION: Shares are present on this appliance. For migration to SynetoOS5, please follow the guidelines. Datasets with Shares are available in the
commandline at:
Type | Pool Name | Used Size | Share name
SMB | flash | 40K | DEMO-SMB
SMB | flash | 40K | DEMO-SMB2
SMB | flash | 25K | DEMO-SMB3

iSCSI Volumes
ATTENTION: iSCSI volumes are present on this appliance. For migration to SynetoOS5, please follow the guidelines. iSCSI volumes are available in the
commandline at:
Pool Name | Used Storage | Volume name

flash | 12K | DEMO

3 virtual machines can be migrated automatically.

Completed collection of SynetoOS migration metadata
Generated: /flash/migration_data_SY2400990099_2024-11-01_10-12-50.tar.gz

5. Export storage pools and shutdown SynetoOS 4

Step 1. Export all storage pools containing customer data (e.g. flash and/or hybrid)

IMPORTANT
If you receive the error "Pool is busy", you will need to reboot the system and try again.

Step 2. Wait for the pool export to complete

Step 3. Shutdown the SynetoOS 4 VM

Step 4 (optional). Upgrade VMware ESXi to the latest available version

6. Power on and configure SynetoOS 5

Perform a final check before starting:

• 32 GB RAM assigned
• 32 GB RAM reserved (reservation checkbox)
• PCI Device(s) added (same as the SynetoOS virtual machine – usually 1 on HYPER 2000 and 4000 and 2 on HYPER 3000, depending on configuration)
• Deployed on datastore1

Step 1. Connect to VMware ESXi hypervisor

Step 2. Power on SynetoOS 5 VM

Step 3. Wait for the blue VM Console to appear (up to 5 minutes)

Step 4. Enter Configure Network

Step 5. Configure the network with your parameters (all fields are mandatory)

IPv4 Address is written in the form <IP>/<netmask_number>

Step 6. Wait for SynetoOS 5 to complete the configuration (up to 6 minutes)

You can refresh the screen (Refresh button), until all services are [running]

Step 7. Perform SynetoOS 5 quick setup ("SynetoOS 5 quick setup")

Step 8. Connect SynetoOS 5 to VMware ESXi ("How to connect SynetoOS 5 to the local ESXi hypervisor")

7. Migrate exported data to SynetoOS 5

Step 1. Connect to SynetoOS 5 controller VM through SSH

ssh admin@<your_ip_address_or_hostname>

Step 2. Become Super User

sudo su

Step 3a. Please update the zimport tool to the latest available version

rpm -Uvh https://yum.syneto.eu/LX/syneto-appliance/rc/release-5.4.2/latest/Packages/syneto-giove-5.4.2-3338.x86_64.rpm

Step 3. Run the zimport tool

zimport

Step 4. Respond to prompts as required (as below)

Pool import confirmation

Continue using pool: `flash` for import? Type 'yes' or 'y' to continue: y

The tool prompts for confirmation for each pool (flash or hybrid). A response other than "yes" or "y" will exit the migration.

Migration file check

Found migration data: /flash/migration_data_SY2400990099_2024-11-01_10-16-42.tar.gz
Found migration data: /flash/migration_data_SY2400990099_2024-11-01_10-16-45.tar.gz
Use migration data from /flash/migration_data_SY2400990099_2024-11-01_10-16-45.tar.gz Type 'yes' or 'y' to
continue: y

The last created migration data file is always used.

Connection check to ESXi through SSH

Searching for connected Vmware servers...
ssh: connect to host 172.16.254.1 port 22: Connection refused

Error ESXi reading startup script:
 command=cat /etc/rc.local.d/04-syneto-os-startup
 
Ignore error and continue anyway? Type 'yes' or 'y' to continue: y

The tool checks if ssh connection to the local hypervisor is enabled and tries to read a file. It can be ignored (the tool will use the API connection on 172.16.254.1).

Searching VMs and replicas

Searching virtual machine .vmx configuration files
Found VM: JumpServer
 /flash/datastores/JumpServer/JumpServer/JumpServer.vmdk
Found VM: FileServer
 /flash/datastores/FileServer/FileServer/FileServer.vmdk
Found VM: TestServer
 /flash/datastores/vm3/vm3/vm3.vmdk 

Looking for replicas

Searching replica virtual machine .vmx configuration files

Listing the datasets that will be migrated

Will upgrade VM: JumpServer
 Storage dataset=flash/datastores/JumpServer -> volume=cb08a9ff-de10-5623-aeae-6abd2215b7cd
Will upgrade VM: FileServer
 Storage dataset=flash/datastores/FileServer -> volume=1a60b7a3-999a-5432-b0e5-eddd675dd555
Will upgrade VM: TestServer
 Storage dataset=flash/datastores/vm3 -> volume=5724a933-002a-5ae9-9363-ee5999b1b678

Continue with the migration of 3 virtual machines? Type 'yes' or 'y' to continue: y

The tool prompts for confirmation on the migration of VMs. A response other than "yes" or "y" will exit the migration.

Importing recovery points

Preparing 33 recovery point(s) for virtual machine `JumpServer`
Preparing 47 recovery point(s) for virtual machine `FileServer`
Preparing 51 recovery point(s) for virtual machine `TestServer`

Continue importing recovery point(s)? Type 'yes' or 'y' to continue: y

The tool prompts for confirmation on the import of recovery points. A response other than "yes" or "y" will exit the migration.

 Imported 131 recovery point
 Import complete.

Removing SynetoOS 4

Searching for deprecated SynetoOS 4 VSA instance...
The SynetoOS 4 VSA instance will be removed from the startup process
 SynetoOS (SynetoOS 4.x Appliance | Version: syneto-os-4.8.5.4668 | Release date: 2024-02-06)

Remove SynetoOS 4 from startup? Type 'yes' or 'y' to continue: y

The tool prompts for confirmation to remove SynetoOS 4 from startup.

8. Complete SynetoOS 5 migration

HYPER 2000 specific activities

Only in case you have a HYPER 2000, add the Write acceleration drive to the hybrid pool.

Step 1. Login to SynetoOS GUI (replace <your_ip_address_or_hostname> with the correct ip/hostname)

https://<your_ip_address_or_hostname>

Step 2. Access Pools page

Step 3. Select the hybrid pool

Step 4. Click on Structure tab

Step 5. Click on Manage, next to Write acceleration

Step 6. Press the + icon

Step 7. Select the 8GB disk and click Add

Step 8. Update the pool structure

HYPER 3000 specific activities

Only in case you have a HYPER 3000, add the Spare drive to the hybrid pool.

Step 1. Login to SynetoOS GUI (replace <your_ip_address_or_hostname> with the correct ip/hostname)

https://<your_ip_address_or_hostname>

Step 2. Access Pools page

Step 3. Select the hybrid pool

Step 4. Click on Structure tab

Step 5. Click on Manage, next to Spares

Step 6. Press the + icon

Step 7. Select the spare disk and click Add

Step 8. Update the pool structure

Add Replication Target(s)

How to manage replication targets in SynetoOS 5

Configure SLA policies

How to manage SLA policies in SynetoOS 5

Protect VMs

How to protect a virtual machine in SynetoOS 5

Remove SynetoFileRecovery VM from ESXi

Step 1. Connect to VMware ESXi hypervisor

Step 2. Select the SynetoFileRecovery VM

Step 3. Delete the SynetoFileRecovery VM

The migration from SynetoOS 4 to SynetoOS 5 is now complete.

Troubleshooting

Error "Cannot import storage pool"

The error “Cannot import storage pool. One or more devices is currently missing/unavailable. Exiting.” may appear during the migration from SynetoOS 4 to SynetoOS 5.

To workaround this issue, please read the following article:

How to solve "Cannot import storage pool" during SynetoOS 4 > 5 migration

Reverting the migration

Returning the migrated data from SynetoOS 5 back to SynetoOS 4 is possible, but it requires additional steps. Partners and end-users are kindly requested to contact Syneto Customer Support, to schedule the required activities.