So I have one old notebook server running in my office with some 20 users and there's the new server from the department in the server room, more powerful and maintained by someone that will stay in this university for many years:
Can I merge the users and data from the old notebook server into the new one, so that I can turn the old one off?
Apparently, this works:
old_server_nbfiles/home into new_server_nbfiles/home. You have to decide which admin folder you keep, or maybe download all the old_server's admin worksheets and upload them into the new_server admin account. Similarly, solve the problem manually if there are different users in both servers with the same name. This might involve sending an email or who knows.users.pickle file in the nbfiles.sagenb folder from both the old and the new server. This is a list with one entry per user. Merge both lists, but beware the admin account and the users in both servers with the same name. Your choices now should be compatible with the ones you made before. Use pickle.dump to save the new users.pickle that will go into the new_server nbfiles.sagenb folder.The above was done while the servers were not running. It was one real server and a sample one. If I get more problems with the two real world servers, I'll post them here.
Asked: 13 years ago
Seen: 802 times
Last updated: Jan 31 '12
Copyright Sage, 2010. Some rights reserved under creative commons license. Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
I'd be very interested in this answer, esp. with the flask nb.