Restore controller only by having db folder

Restore controller only by having db folder

Restore controller only by having db folder
Restore controller only by having db folder
2024-10-03 15:41:18 - last edited 2024-10-16 02:08:43

Hello, accidentally I lost all files from the omada controller and the only thing left,is a backup of the folder db and all of it's content. 

 

I set up a new controller (docker) and replace the new db folder that was created,with the one I have as a backup from the old controller.

 

Controller starts but monogodb cannot start...

 

Is there a change to have my old settings(I only need the devices settings) just from the db folder?

 

Does the new controller has to be at the exactly same version as the db folder was taken from?

 

Is there a way just from that folder and it's content,to determine the version of controller that was taken?

 

Thanks 

  0      
  0      
#1
Options
1 Accepted Solution
Re:Restore controller only by having db folder -Solution
2024-10-09 01:37:53 - last edited 2024-10-16 02:08:43

  @xtrgeo 

Sorry.

We can't tell the controller version from the db file.

But the creation time or last modification time of the database file (or backup file) may have a certain relationship with the controller version release time. If you can obtain the approximate release schedule of TP-Link Omada controller versions, you can try to compare the file timestamps with it. For example, if a backup file is created shortly after the release of a specific version, then this backup may be based on that version. However, this method is only speculative and may be inaccurate due to factors such as update delays and differences in manual backup times.

 

Is your Docker working on a Windows or Linux system?

If Linux, you can install a new Omada controller and it will detect the file automatically. Like below:

 

Recommended Solution
  0  
  0  
#6
Options
5 Reply
Re:Restore controller only by having db folder
2024-10-04 06:31:22

Hi  @xtrgeo 

 

The Omada Controller's database is closely tied to the version of the controller software. In general, it's best if the new controller is at the exact same version as the one from which the backup was taken. Different versions may have different database schemas and structures. If the versions don't match, it can lead to issues such as MongoDB not starting correctly, as you're experiencing.

 

Which version is the db file from?

  0  
  0  
#2
Options
Re:Restore controller only by having db folder
2024-10-04 16:03:42

  @Vincent-TP 

As I wrote above I cannot remember from which version these backup database is. So I cannot create the specific version controller. 

 

Is there a way to understand from the database files what is the correct version of controller?

Maybe if I read the database with another database server?

  0  
  0  
#3
Options
Re:Restore controller only by having db folder
2024-10-08 02:14:12

Hi  @xtrgeo 

 

Normally, the file name will include the version number, such as the following file, it was export from controller version 5.14.26.23.

  0  
  0  
#4
Options
Re:Restore controller only by having db folder
2024-10-08 06:51:39

  @Vincent-TP 

once again: I HAVE NOT cfg file!!!!!!!!!!!!!!!!!!!! I only have the db folder. So, is thre a way to determine which controller version is exported from, just having those files? Is it written inside any file, any database filed?????//

  0  
  0  
#5
Options
Re:Restore controller only by having db folder -Solution
2024-10-09 01:37:53 - last edited 2024-10-16 02:08:43

  @xtrgeo 

Sorry.

We can't tell the controller version from the db file.

But the creation time or last modification time of the database file (or backup file) may have a certain relationship with the controller version release time. If you can obtain the approximate release schedule of TP-Link Omada controller versions, you can try to compare the file timestamps with it. For example, if a backup file is created shortly after the release of a specific version, then this backup may be based on that version. However, this method is only speculative and may be inaccurate due to factors such as update delays and differences in manual backup times.

 

Is your Docker working on a Windows or Linux system?

If Linux, you can install a new Omada controller and it will detect the file automatically. Like below:

 

Recommended Solution
  0  
  0  
#6
Options