1 Message
0
820
June 8th, 2022 16:00
command restore nsrsqlrc
Hello everyone, My name is Jose Rivera hoping you could help me with a consultation. Due to a problem with the number of mdf, ndf and ldf files in a client's database, it prevents me from restoring normally. In order to restore this base, I execute the following under command: from powershell nsrsqlrc.exe -s servernetworker -c clientserver -I dellsql.inp inside the file dellsql.inp contains the following example: -d "MSSQL:BASE" -c "'DATA1'= 'DATA1.mdf',...'DATA30'=DATA30.ndf" -t "3/8/2022 4:17:05 AM" -S normal " MSSQL:BASE" With this I can restore the base on a destination server but it takes a pool where it takes a long time to restore, how can I add this line to my file so that it takes a specific pool. Example of the pool where my saveset is -b "POOL001"
No Events found!
bingo.1
2.4K Posts
0
June 9th, 2022 01:00
I cannot really be of specific db help but I think this is not necessary at this point in time.
You can not especially instruct NW to recover from a specific pool/media.
When you instruct NW to recover, it will convert the browse/recover time to a save set id (ssid) and - by default - recover from the first instance with this ssid, represented by the clone id (which is nothing else but a time stamp). By default, NW will take the instance with the lowest cloneid.
If you have multiple copies/clones of a save set, you can overrule the default behavior by
- making the one wit the lowest cloneid unavailable (remove the tape for example)
- setting a saveset instance to 'suspect'
- use the combination of ssid/cloneid to precisely specify the save set.
But again - you cannot specify a pool to recover from.
As the first instance is usually pointing to a disk media, I am a bit surprised that the recovery is slow. But maybe you tell us a little bit more about your scenario.