nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Upgrade MediaBin 4.5.2 to 4.5.3

System

Hi there,

I sent a mail to support but, I would like to also hear what others have done in this process.

We are planning on upgrading our MediaBin servers from 4.5.2 to 4.5.3 unless there is a newer version instead? 4.6 is not out yet, right?

We currently bought a brand new server and the actual upgrade time is not of any concern. What is recommended upgrade procedure?

This is what I was thinking. Maybe you have a document of this already? ;-)

*** Preparation ***
1. Lock out access to users. (We disable a web site link.)
2. Manual backup of the MediaBin permissions to a SQL table.
3. Manual backup of the Windows Groups to a backup file.
4. Stop MBPServer Service.
5. Disable all of our custom Windows scheduled tasks.
6. Disable all of our custom backend exe processes.
7. Manual backup of the ImageDB folder.
8. Manual backup of 4.5.2 SQL mdf and ldf to a backup file.

*** Perform Upgrade ***
1. Run MediaBin upgrade against the SQL 2000 database.
2. Manual backup of 4.5.3 SQL mdf and ldf to a backup file.

*** Configure New Server ***
1. Install SQL Server 2005 on the new machine.
2. Install SQL Server 2005 SP1.
3. Lock down SQL security accounts.
4. Restore ImageDb files to the new server location.
5. Restore the 4.5.3 SQL backup file to the new SQL server backup folder.
6. Restore backup of the MediaBin permissions to a SQL table.
7. Restore backup of the Windows Groups to a backup file.

*** Install MediaBin 4.5.3 ***
1. Install MediaBin 4.5.3 on new server.
2. Stop MBPServer service.
3. Restore 4.5.3 SQL backup file to the new SQL server.
4. Modify the [MediaBin Repository].[MBSettings] table with the following.
a. FilePath
b. InstallDirectory
c. IPAddress
d. MBDataDirectory
e. ServerDomainName
f. ServerDomainName
5. Start MBPServer service.
6. Finish installing and configuring MediaBin per the installation documentation.

*** Questions ***
1. Can the upgrade from 4.5.2 -> 4.5.3 be done on a SQL2K?
2. Is there a change to the MBPScriptModel2.dll API?
3. Is there a change to the MediaBin Web Service API?
4. Are there any changes to the permissions model for Windows Groups?

Find more posts tagged with

Comments

msrinivas

1. Can the upgrade from 4.5.2 -> 4.5.3 be done on a SQL2K?

Yes. But I would recommend going to the latest SQL version. I am sure your DB group would want you to do that. 4.5.3 supports SQL2K5.

2. Is there a change to the MBPScriptModel2.dll API?

As far as I know, No

3. Is there a change to the MediaBin Web Service API?

As far as I know, there are new methods that have been added but no changes to existing ones

4. Are there any changes to the permissions model for Windows Groups?

I am not sure what you mean by this

********************************************

I was about to suggest an upgrade process but then realized that you did not provide any information on your existing architecture. Do you have a 3,2 or 1 machine architecture? Which of those are you getting new machines? The more information the more help Smiley Happy

HTH

Migrateduser

I may be misinterpreting this statement:
3. Manual backup of the Windows Groups to a backup file.
but it seems to imply that you have created LOCAL groups on your MediaBin Server machine and are using those groups to specify permissions. If that's the case, just be aware that MediaBin server stores Windows SIDs in the database. Therefore, it is likely that after you recreate these LOCAL groups on your new MediaBin Server machine, the SIDs will be different from the original ones.
In this case, we can provide a script to migrate the existing permissions to a flat file. The permissions can then be reapplied to the new server. The script will look up the group BY NAME to reapply the original permissions. NOTE you only need to go through this procedure if you're using LOCAL accounts (groups or users) and those SIDs will not be replicated on your new server.

Migrateduser

This reply is for both MediaBin_MTS and msrinivas.

Thank you both for your help, I appreciate it.

Yes, in the details our goal is to move to a new server and from SQL2K to SQL2K5. However, we just weren't sure if we could do the upgrade first and then transfer or what. You've answered my question.

That is correct, we create Windows Groups to store all of users and in the MediaBin app, we set specific permissions on folders by using the Windows Groups.

Because we were burned by the Windows SIDS stored in MediaBin once before, I have written an application which runs once a day to extract all the permissions from MediaBin and store it in a SQL Server table to circumnavigate the SIDS issue. Additionally, we backup all of the Windows Groups names, details, and SIDS to a separate file to ensure that in the event that we have to rebuild the box or transfer permissions, we can recreate everything through a script.

Our current configuration is as follows:
- 1 machine with MediaBin Server and SQL2K.
- 2 machines IIS web servers.

Our new configuration is as follows:
- 1 machine with MediaBin Server.
- 1 machine with SQL2K5.
- 2 machines IIS web servers.

Thanks again for your help.

msrinivas

Stacy,

Any specific reason why you are not using AD or LDAP and using local windows groups?

Coming to the upgrade steps, my personal preference when changing boxes is to recreate the existing environment on the new box. So install 4.5.2 on the new box and copy MBDataDirectory and also make a copy of the DB on SQL2K. The last step is because 4.5.2 doesnt support SQL2K5. Point the new box with 4.5.2 to the correct MBDataDirectory and DB and do what you have to do to migrate permissions. Make sure its up and running and everything is functional.

Once that is done, install 4.5.3 over 4.5.2 on the new box. The installer has upgrade scripts to update the DB. This should be fairly simple upgrade. Once it is done verify everything.

As a last step copy over DB from SQL2K to SQL2K5 and modify DSN and to point to the new DB.

I am sure I have missed some details and the devil is always in the detail Smiley Happy

If you have a dev server I would strongly recommend doing the upgrade on that box first.

HTH

Migrateduser

Yes, we use AD for our network however, I wasn't the person to setup the server configuration but, that does bring up a good point. I will contact IWOV support and ask them some questions because the permissions setting interface has never worked for us in MediaBin. Probably something to do with the way that we have our network configured.

Thanks for your tips, I appreciate it.

Migrateduser

Yes, we use AD for our network however, I wasn't the person to setup the server configuration but, that does bring up a good point. I will contact IWOV support and ask them some questions because the permissions setting interface has never worked for us in MediaBin. Probably something to do with the way that we have our network configured.

Thanks for your tips, I appreciate it.

In my experience, you need your groups to be "Domain Global" or "Domain Universal". The permission-setting interface will not work with "Domain Local" groups.

We opened a case for this ages ago (we were still using 4.01), but never got a fix for this.

Migrateduser

Hi Folco,

I spoke with support and they indicated to me that my OLAP/AD was not configured correctly. They told me to go into the documentation for mbin server and look at the LDAP settings under my MediaBin Enterprise Mangler.

I looked there and true enough, my settings were not configured. I haven't had time to play with it yet and I hope it does the job when I do set the correct settings.

Stacy

Migrateduser

So, with our new servers the database will be run on a separate server from the mbin server service. How do I change the server and database to point to the other machine?

Is it the registry settings:

[HKEY_LOCAL_MACHINE\SOFTWARE\MediaBin, Inc.\MediaBin\Platform\CurrentVersion]
"ServerName"="MediaBin Server on ****"
"ServerDomainName"="****"

msrinivas

The easiest way to accomplish changing DB settings is to change the DSN entry. Please make sure you stop MB services and copy the DB to the new server before you do it.

HTH

Migrateduser

I want to confirm that the sp3 build is 4.5.0.24 application version binaries?