Skip to main content
Solved

MSSQL Restore stream


Forum|alt.badge.img+12

Hi Fellas,

 

I have searched on the documentation about the changing the mssql restore stream but I couldn’ t find any good information about this. for example, Is it possible to change mssql restore stream from 8 to 4 ?

 

Best Regards.

Best answer by dude

It is not possible to my knowledge. From experience and gathered from support in the past is that whatever number of streams you use to Backup SQL Agents it will be the default for restores as well.

View original
Did this answer your question?

3 replies

dude
Byte
Forum|alt.badge.img+15
  • Byte
  • 287 replies
  • Answer
  • June 10, 2021

It is not possible to my knowledge. From experience and gathered from support in the past is that whatever number of streams you use to Backup SQL Agents it will be the default for restores as well.


Forum|alt.badge.img+7
  • Vaulter
  • 32 replies
  • June 10, 2021
dude wrote:

It is not possible to my knowledge. From experience and gathered from support in the past is that whatever number of streams you use to Backup SQL Agents it will be the default for restores as well.

 

That is correct. When multiple streams are used, multiple backupdevices are requested to be used from Microsoft SQL Server. So if 4 streams are used, 4 backupdevices are generated and on restore, SQL Server is expecting the same number returned. 


Anthony.Hodges
Commvault Certified Expert
Forum|alt.badge.img+10
  • Commvault Certified Expert
  • 88 replies
  • June 10, 2021
0ber0n wrote:

Hi Fellas,

 

I have searched on the documentation about the changing the mssql restore stream but I couldn’ t find any good information about this. for example, Is it possible to change mssql restore stream from 8 to 4 ?

 

Best Regards.

The SQL Server Virtual Device Interface Specification (official documentation has not changed since 2005!) forbids this sadly and it is not much fun when you drop the number of restorable tape drives down from the original library configuration. The reason it is like this is simply how the streaming device data pipelines divides the workload.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings