Server migration - MOODLE Recordings

[Fran Pereyra]

Hi there, 

I need to move my BBB server to another provider. My server has recordings that were made from Greenlight users, and from several Moodle's.

After I make the new install on my new server, will I be able to move the recordings that were made from Moodle integrations? After the migration, Moodle will recognize the recordings? (even after changing the old shared api key to the new one?) 

The steps mentioned here are enought or there are further procedure? http://docs.bigbluebutton.org/2.2/customize.html#transfer-published-recordings-from-another-server

Thanks

[Martin Thomas Schrott]

if your hostname does not change everything should work automatically again.

if the hostname changes, you would have to adopt it in the meta xml file of existing recordings - unless you use scalelite, which ignores that.

hth

Martin

--
You received this message because you are subscribed to the Google Groups "BigBlueButton-Setup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-s...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-setup/f3294a27-42dd-4b4f-acf4-9f26f374eb3e%40googlegroups.com.

[Betim Gashi]

How many BBB servers you have one or multiple ?

[Fran Pereyra]

Jusst one server

[Murat]

Hi, I have problems also.

I moved my greenlight made recordings (all of /var/bigbluebutton) to another server. Moved greenlight db successfully. My domain has also changed. 

---------------------------------------------Old server--------------New Server

bbb version----------------------------------2.2.6-------------------2.2.9

greenlight version--------------------------2.5.x-------------------2.5.5

domain name-------------------------------bbb.xx.com----------bbb.yy.com

I cannot see recordings in greenlight. I also cannot play recordings using https://bbb.yy.com/playback/presentation/2.0/playback.html?meetingId=old_server_meeting_id

it returns with 403 forbidden. nginx log says playback.html failed permission denied. 

Any help would be greatly appreciated.

[Devrim Seral]

https://docs.bigbluebutton.org/2.2/install.html#upgrading

[Murat]

Thank you for your response, 

I actually didn't upgraded in the same server, i completely moved to another server and domain. I am able to succesfully log in my users in greenlight but they can't see their recordings. I tried bbb-conf --setip new_domain_name  restarted bbb but no success. 

Thank you.

[Murat]

1. Never download your recordings or greenlight database via ftp. ASCII mod is your enemy. Downloading my greenlight production db was corrupt. Use binary mod if you have to use ftp.

2. Permissions Permissions Permissions. If you are using external hdd always check permissions of mount point. 

My server back and working as expected. Succesfully moved from one server to another. 

By the way. Great effort! Respect all the bigbluebutton and greenlight team. Keep up the good work.

Cheers. 

[Fran Pereyra]

Hi Murat could you please share the steps you made to get the recordings from your first server back to the new one?

Thanks 

[Murat]

While you are moving your recordings 

If you have physical acces to server use ext4 formatted external hdd for backing up your recordings. If you don't have physical access never use ftp. ftp uses ascii mode default and ascii mod ruins your recordings. When download finishes you would assume that my recordings are backed up but beware! Never use ftp. If you have to use ftp, change your ftp software's mode to binary. If you are using ec2, tar your recordings into single file, send them to a s3 bucket and download them using aws cli. (https://stackoverflow.com/questions/43557711/fastest-way-to-download-large-files-from-aws-ec2-ebs). Do not extract them in windows. Extract them in your linux server.

1. Make sure your new bigbluebutton server working as expected without recordings. (Make sure your turn server working. (1007 is definitely related to I spend hours couse i assumed that my turn server is working. It turned out that my server was not working. Use https://webrtc.github.io/samples/src/content/peerconnection/trickle-ice )

2. If your hard disk large enough, copy your old /var/bigbluebutton folder to new server's' /var/bigbluebutton folder. Log out log in greenlight (or your lms) You will see your recordings are there.

       If your hard drive is not large enough and using external hard drive or another hard dive for /var/bigbluebutton and using symlinks (ln -s) 

       2.1. Make sure you followed (Root partition too small) 

             Make sure your hard drive's permissions are correct. 

             sudo chmod 777 /var/bigbluebutton

             sudo chown -R bigbluebutton:bigbluebutton /your/mount/point/bigbluebutton_recordings

             sudo chmod -R 755 /your/mount/point/bigbluebotton_recordings

 

Log out and log in greenlight (or lms) you should see your old recordings. If you don't see them you won't find any complaints about permissions in your log files. Check hard disk permissions. Especially permissions of upper folders of bigbluebutton_recordings

           sudo chown -bigbluebutton:bigbluebutton /your/mount/point

           sudo chown -bigbluebutton:bigbluebutton /your/mount/

           sudo chown -bigbluebutton:bigbluebutton /your/

I hope this helps. Cheers.

[Fran Pereyra]

Thank you so much for you reply Murat! This is more than useful, I really appreciate it.

One more thing please. What about Greenlight? How do I transfer Greenlight's DB to the new server for the recordings that were made from there? Any clue?

Thank you again Murat!

[Murat]

While moving Greenlight database copy all contents of db folder in /your/folder/to/greenlight/

But when you copy your db folder you will see that production folder will not be copied. If you don't notice that you will spend your hours to figure out. You need to change permissions of ~/greenlight/db/production folder. 

Before copying note the username and permissions of production folder. 

cd /to/your/greenlight/db

ls -la

you will see the username and permissions there 

-rw-------  1 murat murat    0 May  8 04:28 development.sqlite3

drwx------  2 murat murat 4096 May  8 04:28 migrate

drwx------ 19 red5  murat 4096 May 12 21:55 production

-rw-------  1 murat murat 5431 May  8 04:28 schema.rb

-rw-------  1 murat murat  105 May  8 04:28 seeds.rb

you can use https://chmod-calculator.com to learn more about your folder permissions. 

cd into db folder and 

sudo chmod -R 777 production

Now you can copy copy your old database folder to your new server. When you copy your database to new server you may change permissions and username again. 

cd into db folder in the new server and 

sudo chmod -R 700 production

sudo chown -R red5:murat production     (change red5 and murat according to your server)

[Murat]

And if you are using greenlight in docker image

cd /in/to/your/greenlight

sudo docker-compose down

sudo docker-compose up -d  

If you encounter an error and want to know what the error is do not use -d extension in second command. You will see all the information on the terminal while greenlight is starting. 

[Fran Pereyra]

Thank you so much Murat you are the king!! I've been able to get the users and their recordings to my new server, and I can login with them and see their recordings, but one thing is still not changed: when I click on PRESENTATION (to see a recording playback) it opens the OLD servers link.

I have done already the bbb-conf --setip and set new shared keys to .env file and updated links at " BIGBLUEBUTTON_ENDPOINT= " but greenlight is still using the old hostname for presentations and to create new meetings as well.

What I am doing wrong? Thanks so much!!!

[Fran Pereyra]

Hey Murat I just wanted to tell you that I MADE IT!!!! 🎉🎉🎉

In case anyone is reading is, I was missing this last steps in addition of what Murat suggested:

•  /greenlight/.env (on NEW server) --> update these lines with secret keys from your new bbb server (you can get it with " bbb-conf --secret ") just copy and paste it in /greenlight/.env  at the following lines (replace the old server keys):

BIGBLUEBUTTON_ENDPOINT= 

BIGBLUEBUTTON_SECRET=

• Restart greenlight!!!!!!!
  
  cd ~/greenlight
  docker-compose down
  docker-compose up -d
  
  
• Finally restart BBB:
  
  bbb-conf --restart
  
  
  GREENLIGHT DB MIGRATION DONE!!! 💪