Correct steps Updating from 3.1.1 to new without destroing my database

What are the correct steps Updating from 3.1.1 to 4.1 version without destroing my database and cause o corrupt file i have many lists and cues on my database i use version 3.1.1. on windows laptop and 3.1.1 on my prime go

I think going from 3.1.1 → 3.4 then 4.0 → 4.1 should be fine, though the 3.4 → 4.0 is likely unnecessary.

Before you upgrade anything, I would make sure you back up your databases using Windows Explorer (make a zip file to be safe or something) on your music drive and any other devices you use to perform, USB Storage and SD Cards, etc…

If you want to be super safe, take a snapshot of your Database2 folders before each upgrade.

1 Like

Sounds good above, However on a side note the jump from 4.0.1 - 4.1 will change the database and you will only then (engineOS & Engine software), neable to use the latest 4.1 Engine software and only 4.1 Engine OS. due to significant database changes you will NOT beable to read your databases if you wish to downgrade from 4.1. also 4.1 on a Mac by example has to be running the latest MacOS 12+ for Engine Software to run! etc

There was my problem! My Mac was not able to run the latest software for Engine and as a result the updated database on my usb 4.1 engine OS was not readable!

Luckily I had a backup of my older database Engine OS 3.4 and 4.0.1 So I was able to roll back the Engine OS Firmware to 4.0.1 and my older Engine 2.2 software could still be used and read the USB.

So unless its broken, think and plan your updates accordingly and make backups before you start!

1 Like

@dopeNL he is right, make sure you have 1-2 real copies of your Database and use @djliquidice approach.

Database changes have always a certain risks. I did the updates one by one and had no corruptions.

1 Like