Storage Manager 2019 R1

Hello rodrigo_bola,

That is correct that DSM 2019 doesn’t support SQL express.  Do you have more than 1 Compellent system?  Are you monitoring your performance to make improvements?  

Please let us know if you have any other questions.

hello Sam,

I'm thinking of my clients, when it comes time to install SCOS 7.4 I need to upgrade DSM, and I have to migrate from SQLexpress to SQL server.

because i have client with two system and i need to manage the replication!!!

thks

rodrigo

Why not use the Data Collector Internal Database? I have only 1 storage system here and I use the internal database with no problem... 

The only limitation if you are going to use the embedded database is that performance data and events are only keep for the last 30 days.

You could also look for the VMware DSM Appliance, I really don't know it the appliance internal database from the DSM appliance is a long term Database or if it has the same 30 days limitations from the DSM Windows Version, maybe someone here can confirm it!!

We use the internal DSM Database from beginning because we are a VMware shop. It comes with the same limitation that you only see the last 30 days. There is one exception when you use the IO Usage tab you can get IOPS and transferates up to a year but only on the most upper level which is your SC. As soon as you select a element like a Volume, Server you will see your max. 30 days again.

Compared this to my beloved EQL SANHQ i find it a little bit limited.

But most important..... the embedded (My?)SQL Database is not supportet for production environments even when you only have one SC (as most of my customers). When ever we have a support question this comes up to the table.

How can someone comes with a solution like a Appliance and than design a external dependancy which makes is even harder when this Appliance also acts like a witness? Sorry i dont understand. Please compare to the VCSA from VMware for example.

Regards,
Joerg

Hello

But most important..... the embedded (My?)SQL Database is not supportet for production environments even when you only have one SC (as most of my customers). When ever we have a support question this comes up to the table. -

How can someone comes with a solution like a Appliance and than design a external dependancy which makes is even harder when this Appliance also acts like a witness? Sorry i dont understand. Please compare to the VCSA from VMware for example. in the future will be use cloudIQ the logs and metrics remains on EMCcloud, now with 7.3.x you can access to the storage directly.

the problem is when you have clients with cross-replication SC-PS, and you need to get scos 7.4.2 advantage (veeam) you need to tell the costumer you need to have SQL server €€

thks

no money no funny

The problem is not the $$ or having no SQL around. The problem is that this SQL is a normal VM which runs on  the same Environment and most likely on the same SC system.  I want to limit the dependencies and having an external SQL is the oposite, especially when DSM acts as tiebreaker/witness.

Majority of my customers are SMB or just "small" and when there is a SQL around it is the cheap Express Version for sure.

Regards,
Joerg

Hello,

Sorry to resurrect an old thread; but I am interested in the same question as the OP.

The release notes for DSM 2019 R1 (https://topics-cdn.dell.com/pdf/dsm-2019-r1-rn_en-us.pdf) list both SQL 2016 & 2017 Express as supported external databases (albeit with the caveat that they are limited to 10GB).

The same release notes state that the "embedded database is not recommended for a production environment." but it is not clear to me if the embedded database would (or would not) be supported for production environments.

I don't want any issues when I need support. So which is the better database for a single SCv3000 deployment? Internal database (limited to 64GB / 30 Days) or a SQL Express database (limited to 10GB / x Days)? 

If I chose to implement either a Microsoft SQL (Full not Express) or a MySQL database:

1. where are the instructions on external database creation/preparation?
2. would MySQL 5.6/5.7 be supported with a Windows Server DSM installation or is MySQL only supported with the DSM virtual appliance?
3. Can the external database be installed on the same server as DSM or must it be a seperate server/VM?

Thanks

Martin

Hello martinco-cae,

You can use which every works best for your environment.  If the internal database fits your needs, then you can use it.  If it doesn’t & you need to keep records for longer then you will need to use an external database.  You can install the external database on the same system as DSM.  Here is a link to Dell EMC SC Series Arrays with MySQL.  https://dell.to/2Rat2yQ

Please let us know if you have any other questions.

Hi @DELL-Sam L 

That is great; thanks for the clarification.

Ref: MySQL config document. I was looking for the required steps on how to create/prepare the empty MySQL database for the DSM installer to use or do I just point the DSM installer at a MySQL server instance and it will create all of the required databases/tables itself?

Cheers

Martin

Thanks @bealdrid2 

Glad to hear you are having a good experience with the MySQL database backend.

I will get some lab time booked out and have a tinker with a single server DSM/MySQL install.

Cheers

Martin

I believe you will need to create the database manually (along with the user you want DSM to connect with)-

https://www.dell.com/support/manuals/us/en/04/storage-sc9000/dsm-2016-ig/prepare-a-mysql-database?guid=guid-e3feccf2-ed64-4976-ba8c-33381725d546&lang=en-us

At that point, DSM will create all the necessary tables,etc.

BTW, we've been using MySQL as the DB back end on a separate server, and it has been working great.

Hi @bealdrid2

Can you share your MySQL environment details?

I am trying to setup DSM appliance with External DB as mysql, but no luck.

thanks

As @bealdrid2 pointed out there is an error in DSM 2019 install guide in MySql preparation section; a step was missing. I followed 2016 Install guide for MySql preparation for the install and i was able to complete the install successfully.

thanks