+- MinimServer Forum (https://forum.minimserver.com)
+-- Forum: MinimServer (/forumdisplay.php?fid=1)
+--- Forum: General (/forumdisplay.php?fid=2)
+--- Thread: MinimServer complexity (was Configuration Backup) (/showthread.php?tid=1869)
MinimServer complexity (was Configuration Backup) - NASssd - 26-09-2014 00:35
I have configured MinimServer using MinimWatch to get it to function just the way I would like it. I took screen shots along the way so that I could easily go back to a setting if I made a mistake. I was wondering if there is a file on my Synology that that I could backup. I see there is a file called MinimServer.config. Could I save this to a local drive in case I had a failure and had to reload? Are there any other files that should be saved in case of failure? If I had to reload, would I be able to just cut and paste this file in to the Synology MinimServer/Appdata folder? Thanks for any help in advance.
Mark
RE: Configuration Backup - simoncn - 26-09-2014 09:02
(26-09-2014 00:35)NASssd Wrote: I have configured MinimServer using MinimWatch to get it to function just the way I would like it. I took screen shots along the way so that I could easily go back to a setting if I made a mistake. I was wondering if there is a file on my Synology that that I could backup. I see there is a file called MinimServer.config. Could I save this to a local drive in case I had a failure and had to reload? Are there any other files that should be saved in case of failure? If I had to reload, would I be able to just cut and paste this file in to the Synology MinimServer/Appdata folder? Thanks for any help in advance.
Mark
All your MinimServer configuration settings are saved in the minimserver.config file and this is the only file you need to backup. If you need to restore your settings later, you can copy this file into the MinimServer/appData folder. Make sure you have stopped MinimServer in Package Center before doing this copy.
A future version of MinimServer might create additional files that should be backed up. If this happens, it will be documented in the Release Notes.
RE: Configuration Backup - DavidHB - 26-09-2014 12:05
(26-09-2014 09:02)simoncn Wrote: ... MinimServer configuration settings are saved in the minimserver.config file and this is the only file you need to backup. If you need to restore your settings later, you can copy this file into the MinimServer/appData folder. Make sure you have stopped MinimServer in Package Center before doing this copy.
A future version of MinimServer might create additional files that should be backed up. If this happens, it will be documented in the Release Notes.
This is fine if the NAS has proper file management capabilities, which my ReadyNAS does not; SSH and a CLI is no substitute. Also, while some users will be happy messing around in AppData and its counterparts in other systems, others will not. Would it be possible to add a 'backup settings' button to the Properties window?
David
RE: Configuration Backup - simoncn - 26-09-2014 14:03
(26-09-2014 12:05)DavidHB Wrote: This is fine if the NAS has proper file management capabilities, which my ReadyNAS does not; SSH and a CLI is no substitute. Also, while some users will be happy messing around in AppData and its counterparts in other systems, others will not. Would it be possible to add a 'backup settings' button to the Properties window?
David
If MinimServer were to provide a way to copy the minimserver.config file to a different location, it is fairly likely that whatever catastrophe destroyed the primary copy would also destroy the backup copy. Only the user can ensure that the backup copy is located in a suitable safe place.
RE: Configuration Backup - DavidHB - 26-09-2014 16:02
(26-09-2014 14:03)simoncn Wrote: If MinimServer were to provide a way to copy the minimserver.config file to a different location, it is fairly likely that whatever catastrophe destroyed the primary copy would also destroy the backup copy. Only the user can ensure that the backup copy is located in a suitable safe place.
The scenario I had in mind was MinmWatch running on, say, a PC, saving the .config file from the NAS to a location on the PC, using a standard file save dialog. There are catastrophes that would destroy both those locations, but they are, I think, somewhat less likely than catastrophes that destroy only one. If the PC has off site backup, that pretty much covers all the bases.
That said, I accept that there are other options. It is pretty easy to build a text file by copying and pasting entries (especially the more complex ones) from the Properties window. If you can get to the .config file, you can also copy and paste from there into, for example, the Properties window of another instance of MinimServer. I copied entries from one Properties window to another when I set set up the instances of MinimServer I run under Windows and Linux, and that worked pretty well. But I'd still argue that a simple 'Backup' button is the method a non-technical user is most likely to use.
David
RE: Configuration Backup - NASssd - 26-09-2014 16:08
(26-09-2014 12:05)DavidHB Wrote:(26-09-2014 09:02)simoncn Wrote: ... MinimServer configuration settings are saved in the minimserver.config file and this is the only file you need to backup. If you need to restore your settings later, you can copy this file into the MinimServer/appData folder. Make sure you have stopped MinimServer in Package Center before doing this copy.
A future version of MinimServer might create additional files that should be backed up. If this happens, it will be documented in the Release Notes.
This is fine if the NAS has proper file management capabilities, which my ReadyNAS does not; SSH and a CLI is no substitute. Also, while some users will be happy messing around in AppData and its counterparts in other systems, others will not. Would it be possible to add a 'backup settings' button to the Properties window?
David
Thanks for the help. I do have one additional question. If I were to not have a problem, but wanted to upgrade storage to SSD drives, could I use the MInimServer.config file on new Raid 0 setup. Lets say I have two 3 tb Western Digital conventional spin drives in Raid 1 and get two 500 GB SSD drives and install them in a Raid 0 configuration in my Synology, can I use the the MinimServer.config file from the Western Digital Raid 1 configuration on the SSD Raid 0 setup?
Thanks,
Mark
RE: Configuration Backup - DavidHB - 26-09-2014 17:15
(26-09-2014 16:08)NASssd Wrote: If I were to not have a problem, but wanted to upgrade storage to SSD drives, could I use the MInimServer.config file on new Raid 0 setup. Lets say I have two 3 tb Western Digital conventional spin drives in Raid 1 and get two 500 GB SSD drives and install them in a Raid 0 configuration in my Synology, can I use the the MinimServer.config file from the Western Digital Raid 1 configuration on the SSD Raid 0 setup?
In those circumstances, you would be rebuilding your system from scratch (and would need to back up the contents of your NAS fully before changing the disks). Depending on your circumstances, and given that the cost of 2 500GB SSDs is a significant investment, it might be worth going the extra mile, and putting a completely new NAS on the network. This would make migration easier and safer.
Simon is the expert, but my experience with copying and pasting values and the fact that the .config file is plain text indicates to me that the old .config file can be copied to the location of the new installation and used as before. The one setting you need to be careful with is contentDir; the location of the music folder(s) on the new setup must be exactly the same as on the old, or this setting (and therefore MinimServer) will not work.
If I were doing the job with 2 NASs in place (at least temporarily), I would copy the music to and set up MinimServer (with default settings) on the new NAS. Then, using MinimWatch, I'd open Properties windows for both instances of MinimServer, and copy and paste the settings to the new instance as necessary (some of the default settings, including, probably, contentDir, will not need to be changed). That way, you can check the settings as you go. Having done essentially the same job, as described in my last post, I can confirm that the settings process only takes a few minutes.
David.
RE: Configuration Backup - simoncn - 26-09-2014 18:08
(26-09-2014 16:02)DavidHB Wrote: The scenario I had in mind was MinmWatch running on, say, a PC, saving the .config file from the NAS to a location on the PC, using a standard file save dialog. There are catastrophes that would destroy both those locations, but they are, I think, somewhat less likely than catastrophes that destroy only one. If the PC has off site backup, that pretty much covers all the bases.
Thanks for clarifying your suggestion. MinimWatch is intended as a remote control for the local MinimServer UI (as exposed on systems with a GUI such as Windows and Mac). I don't think it would be appropriate to start adding extra facilities such as remote file backup and restore.
I will think some more about this. It's only a problem for ReadyNAS and QNAP because the user doesn't have direct access to the location of the minimserver.config file on these NASs. How do other NAS apps handle configuration backup?
Quote:That said, I accept that there are other options. It is pretty easy to build a text file by copying and pasting entries (especially the more complex ones) from the Properties window. If you can get to the .config file, you can also copy and paste from there into, for example, the Properties window of another instance of MinimServer. I copied entries from one Properties window to another when I set set up the instances of MinimServer I run under Windows and Linux, and that worked pretty well. But I'd still argue that a simple 'Backup' button is the method a non-technical user is most likely to use.
David
It is very risky to copy and paste entries into a minimserver.config file. The syntax isn't documented and some of the properties have constraints on their values and/or dependencies on the values of other properties. Doing this is likely to cause problems and isn't supported. Copying a minimserver.config file from one NAS to another can also cause unexpected problems.
Restoring a complete backup minimserver.config file that was written previously by MinimServer on the same NAS should usually be OK. When doing this restore, MinimServer shouldn't be running.
RE: Configuration Backup - NASssd - 26-09-2014 18:12
(26-09-2014 17:15)DavidHB Wrote:(26-09-2014 16:08)NASssd Wrote: If I were to not have a problem, but wanted to upgrade storage to SSD drives, could I use the MInimServer.config file on new Raid 0 setup. Lets say I have two 3 tb Western Digital conventional spin drives in Raid 1 and get two 500 GB SSD drives and install them in a Raid 0 configuration in my Synology, can I use the the MinimServer.config file from the Western Digital Raid 1 configuration on the SSD Raid 0 setup?
In those circumstances, you would be rebuilding your system from scratch (and would need to back up the contents of your NAS fully before changing the disks). Depending on your circumstances, and given that the cost of 2 500GB SSDs is a significant investment, it might be worth going the extra mile, and putting a completely new NAS on the network. This would make migration easier and safer.
Simon is the expert, but my experience with copying and pasting values and the fact that the .config file is plain text indicates to me that the old .config file can be copied to the location of the new installation and used as before. The one setting you need to be careful with is contentDir; the location of the music folder(s) on the new setup must be exactly the same as on the old, or this setting (and therefore MinimServer) will not work.
If I were doing the job with 2 NASs in place (at least temporarily), I would copy the music to and set up MinimServer (with default settings) on the new NAS. Then, using MinimWatch, I'd open Properties windows for both instances of MinimServer, and copy and paste the settings to the new instance as necessary (some of the default settings, including, probably, contentDir, will not need to be changed). That way, you can check the settings as you go. Having done essentially the same job, as described in my last post, I can confirm that the settings process only takes a few minutes.
David.
Thank you for the reply. I will take screen shots of my current MinimWatch settings and then completely reconfigure my settings upon installing the SSD's. My plan is to purify my tags on my current music database on my Western Digital 3TB drives. As I go, I have two separate external back up drives to ensure the data is protected. I will then do a factory reset on my Synology 214Play and install the two Samsung 840 Pro 500 GB SSD's. I will set up a Raid 0 configuration and get all my music files copied into a music directory. At this point I will load Java and MinimServer and then configure manually with MinimWatch. This is going to be a lot of work, but my hope is an over all increase in performance. I read a post on this forum about using MinimServer with an SSD and transcoding and how much better the system sounded. I have been able to get a tremendous increase in sound quality with transcoding to wav and separate linear power supplies along with an HP Procurve switch. I have also noticed a notable difference with better ethernet cables. My quest is to turn my Synology into a hi end transport. So far it is working. My system is sounding better and better with every step I take. This forum is really an excellent resource for a digital audiophile. I really appreciate all the support. Thanks Again,
Mark
RE: Configuration Backup - simoncn - 26-09-2014 18:12
(26-09-2014 17:15)DavidHB Wrote: Simon is the expert, but my experience with copying and pasting values and the fact that the .config file is plain text indicates to me that the old .config file can be copied to the location of the new installation and used as before. The one setting you need to be careful with is contentDir; the location of the music folder(s) on the new setup must be exactly the same as on the old, or this setting (and therefore MinimServer) will not work.
I don't advise doing this. Some properties are specific to the NAS on which the minimserver.config file was originally written.
Quote:If I were doing the job with 2 NASs in place (at least temporarily), I would copy the music to and set up MinimServer (with default settings) on the new NAS. Then, using MinimWatch, I'd open Properties windows for both instances of MinimServer, and copy and paste the settings to the new instance as necessary (some of the default settings, including, probably, contentDir, will not need to be changed). That way, you can check the settings as you go. Having done essentially the same job, as described in my last post, I can confirm that the settings process only takes a few minutes.
This is a much safer approach and is the recommended way to migrate configuration settings.