Unsolved
This post is more than 5 years old
15 Posts
0
1754
Limit parallelism on NMM SQL VDI Backup.
Hello,
I'm tryng to backup a SQL instance with more than 300 DB on one DDBOOST device.
I'm using the MSSQL: saveset but i can see that i've about one job for one DB in the running portion of the job, at the same time.
This mean about 300 parallel stream, with obviuously poor performance.
On the client the parallelism is set to 16, but networker seems to ignore this limitation.
The nw server, client, and module version is 8.2
How can I limit the parallelism of this job?
Thanks
Lorenzo
Maol1
15 Posts
0
January 28th, 2015 06:00
Hello,
i've not set the data striping on my backup command.
only nsrsqlsv -a myclient
Lorenzo
Deb_PS
156 Posts
0
January 28th, 2015 06:00
What is setting for the "Stripe" for the SQL backup?
Alternatively can you run a Manual Backup from the SQL server using "NetWorker User for SQL Server" and check the performance
I believe the strive setting is not proper in your case.
oldhercules
116 Posts
1
January 28th, 2015 23:00
Hello,
We are using nw8.1 + nmm3, but we were also unable to resolve such problems. I think client parallelism works only if you have many savesets in the client definition, but now you have only one (MSSQL:).
A simple workaround is to create more clients with specific (MSSQL:db1, MSSQL:db2,...) saveset definitions and run them in separate, not overlapping groups. The drawback of this solution is if something changes in the environment (add/remove db) then you should not forget to change the backup config.
Maol1
15 Posts
0
January 29th, 2015 00:00
Hello oldhercules,
I know that, we've this issue since we've modified the SS from MSSQL:blabla to MSSQL:
BTW we cannot mantain the specific SS for every db because on this instance there is more than 300 DB with high chance of change.
Thanks
Lorenzo
crazyrov
4 Operator
4 Operator
•
1.3K Posts
0
January 29th, 2015 01:00
Maol
on the other hand you could also limit the streams coming into the DD device by reducing the target session and max session setting on the device side.
ble1
2 Intern
2 Intern
•
14.3K Posts
2
January 29th, 2015 09:00
SQL VDI backups are quite touchy so if you reduce available targets, they tend to fail so limiting targets might not be welcome. And in general it would mean to have dedicated devices for SQL backup which translates to additional pool so suddenly whole setup changes. Real solution should be to implement change on client code side.
crazyrov
4 Operator
4 Operator
•
1.3K Posts
0
January 30th, 2015 00:00
Noted, Thanks H.
Castromotorbox
217 Posts
0
February 3rd, 2015 06:00
Hi,
NMM doesn't care of parallelism limitation set in Networker. We have seen the same with Exchange Backup.
The only way will be to limit the number of save stream on Storage Node (even if it's not ideal) or create many different client with different Save set.
Cheers
Greg