Thanks guys. I will just stick with VSS then. At least, the snapshot for databases in the SQL box are created at the same time. That will be easier to manage savesets instead of defining multiple savesets in the backup.
Make the client parallelism equivalent to the number of Database on the SQL server. Also ensure you have a device that is capable and free to take in all these streams.
ble1
4 Operator
•
14.4K Posts
1
May 24th, 2014 13:00
No, it will do then sequentially. What you can do with VDI is:
MSSQL:database1
MSSQL:database2
[etc]
and make sure client parallelism is big enough to have them all run at the same time.
wlyeung_191be5
4 Posts
0
May 26th, 2014 06:00
Thanks guys. I will just stick with VSS then. At least, the snapshot for databases in the SQL box are created at the same time. That will be easier to manage savesets instead of defining multiple savesets in the backup.
crazyrov
4 Operator
•
1.3K Posts
2
May 26th, 2014 06:00
Make the client parallelism equivalent to the number of Database on the SQL server. Also ensure you have a device that is capable and free to take in all these streams.
ble1
4 Operator
•
14.4K Posts
0
May 26th, 2014 07:00
Actually I prefer VDI because I can use transaction logs at least.