When using NMM SQL VDI there is the option to use the "MSSQL:" saveset to back up all databases within a SQL instance. However, when you do this, backups run sequentially rather than in parallelism.
If you specify individual databases within the saveset (i.e., MSSQL:Database1001, MSSQL:Database1002) they back up using parallelism.
Since the product is able to enumerate all databases when using the MSSQL command, as well as being able to run with parallelism, there should be a way to allow it to do both.
This would help many backup administrators such as myself not to have to continually add and remove databases from a environment with a large amount of databases and frequent additions, etc. from having to constantly update the list of databases contained within the saveset.
It doesn't matter whether this is in a cluster, whether it's a standalone SQL server, etc. It's just all in the Client saveset fields.
Does this explain what needs to be added for optimal functionality?
ElanC
53 Posts
0
December 21st, 2016 01:00
Hi Alwatson,
Currently this design in NMM SQL VDI module is un-changed. Good to bring this up again.
I will go-ahead and update the focal-point with the details.
Can you please help me providing the env. details? This will help us to understand the ROI.
Thanks,
Elango C
watson-alix
1 Rookie
•
28 Posts
0
December 21st, 2016 08:00
ElanC -
Thank you for taking the time to reply to this.
This is environment agnostic for the most part.
When using NMM SQL VDI there is the option to use the "MSSQL:" saveset to back up all databases within a SQL instance. However, when you do this, backups run sequentially rather than in parallelism.
If you specify individual databases within the saveset (i.e., MSSQL:Database1001, MSSQL:Database1002) they back up using parallelism.
Since the product is able to enumerate all databases when using the MSSQL command, as well as being able to run with parallelism, there should be a way to allow it to do both.
This would help many backup administrators such as myself not to have to continually add and remove databases from a environment with a large amount of databases and frequent additions, etc. from having to constantly update the list of databases contained within the saveset.
It doesn't matter whether this is in a cluster, whether it's a standalone SQL server, etc. It's just all in the Client saveset fields.
Does this explain what needs to be added for optimal functionality?
Thank you!