upgrade Mcafee CSR

[adnankhazaleh]

what is the needed time for McAfee CSR to update database schema after upgrade ? in our case , we use external MSSQL server and the database size is about 320 GB and update database schema running for the last two days without completion 

[LKS]

Hi adnankhazaleh,

Am really not an expert in CSR product, however i would say it depends on the size of your database, the database schema update can take a long time. There is no time frame for database upgrade. 

Reference : https://docs.mcafee.com/bundle/content-security-reporter-2.1.0-installation-guide-epolicy-orchestrat...

Was my reply helpful?

If you find this post useful, please give it a Kudos! Also, please don't forget to select "Accept as a soultion" if this reply resolves your query!

[adnankhazaleh]

update database schema task running for about 3 days without completion , is it normal ?

[LKS]

Since am not expert in CSR product, i will move this post to CSR team for further assistance.

Was my reply helpful?

If you find this post useful, please give it a Kudos! Also, please don't forget to select "Accept as a soultion" if this reply resolves your query!

[AaronT]

Per the 2.6 installation guide: The amount of time it takes for the schema to update depends on the size of your database. For example, a database with 50 GB of data takes about 5 hours to update.

So it could take 1 hour per 10 gb of data.

That's an estimate of course, but it depends on the database size and specs of the database server.

If it's running for longer than you expect, opening a ticket with support might shed some light on what %age is completed and an estimate of how much longer is needed

[Former Member]

Updating a database schema is really simple in case you are able to get your application offline. You shutdown the software, develop a backup of the present database schema, conduct all necessary update operations with tools as Liquibase or Flyway, restart the application program and hope that every thing works fine. But that changes in case your customers do not accept any downtime. Easy modifications, like eliminating a column or perhaps renaming a table, suddenly call for a multi step migration process. The reason behind that's that high available methods make heavy usage of redundancy.

Redundancy - A necessary evil If you would like to create a high available phone system, you have to put no less than two cases of every subsystem. Therefore, in probably the simplest case, you want a minimum of two cases of the application of yours and two situations of your respective database server.

The redundancy of all subsystems offers a great deal of advantages. The 2 most prominent ones are:

It increases the amount of parallel requests that the program of yours is able to handle.
It can make certain that your system continues to be all set up even when an example of 1 of your subsystems is not accessible.
Though they also create brand new challenges. I won't dive any deeper into subjects as monitoring, load balancing, tracing, then fault tolerance. When you do not have some knowledge about high available methods, you must find out about all of them. The best part is there are several great programs and libraries available which help you fix these challenges.load more...