More > JRiver Media Center 31 for Windows
MC clients don't take backups on a schedule
Matt:
One thing we could do would be to enable backup and restore on a library server client.
We would make the backups not contain the library files. They would only contain settings.
We would make a library restore disable the choice to restore the library. Only the choice to restore settings would be available.
We would make automatic backups work on connected clients, creating a backup of settings only.
Would this be a good change?
JimH:
There's a problem I can see. I use the same copy of MC in three modes at different times.
Stand-alone
Client
Server
We'd need to handle restoring each and we'd need to separate how they are stored (sub-directory for clients?)
Note that we're not committing to make a change yet. Just discussing and thinking.
DJLegba:
--- Quote from: JimH on July 21, 2023, 08:04:26 am ---There's a problem I can see. I use the same copy of MC in three modes at different times.
Stand-alone
Client
Server
We'd need to handle restoring each and we'd need to separate how they are stored (sub-directory for clients?)
Note that we're not committing to make a change yet. Just discussing and thinking.
--- End quote ---
The user gets to decide which backup file to restore, so I don't think this will present a problem.
JimH:
--- Quote from: DJLegba on July 21, 2023, 08:27:00 am ---The user gets to decide which backup file to restore, so I don't think this will present a problem.
--- End quote ---
How will they know? The types of backups need to be distinguished somehow.
dtc:
--- Quote from: JimH on July 21, 2023, 08:04:26 am ---There's a problem I can see. I use the same copy of MC in three modes at different times.
Stand-alone
Client
Server
We'd need to handle restoring each and we'd need to separate how they are stored (sub-directory for clients?)
Note that we're not committing to make a change yet. Just discussing and thinking.
--- End quote ---
I may be missing something, but why are these separate backups? Is seems like a single backup of the standalone on disk library covers everything that is needed.
When running as a client I do not think you want to back up the server portion of what is temporarily on the client, since that may change on the server between the backup and the restore. Once the restore is done on the client, it can simply reconnect to the server and be up to date.
When running as a server, does the system actually store anything specific to being a server other than what is stored in the main library?
I think what is needed is exactly the backup that you would get by disconnecting the client from the server and doing a backup of the standalone system. So, why not just backup appdata\roaming\J River\Media Center 31 or some subset of that? Other things may be needed, but it seems those would be unique to the standalone system? I guess you might lose the current playing now and some other dynamic items, but I am not sure that is critical to the backup and may not be wanted if running as a client.
It seems like backing up the standalone system and then having the user reconnect to the server may be the right way to go. For me, I would expect to have to do a reconnect after a restore, but I defer to those you run a lot of clients continuously.
Obviously, without knowing the full internal structure it is hard to know exactly what is required. Just thinking out loud.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version