06-14-2016 08:03 PM
I can generate a Move Template by using the NetBackup MS SQL Client without problems, it locates the NBIMAGE, and correctly identifies the MOVE parameter to use. The logical dbname is not the same as the one that's found in the NBIMAGE even when parsing it.
I can use the following to retrieve the NBIMAGE name.
bplist.exe -B -t 15 -C <remote client> -R -I -l /
remoteclient001.MSSQL7.remoteclient001.db.db001.~.7.001of001.20160425010043..C
But, db001 is the current DB Name, not the logical name. When using the GUI this will give me the line
MOVE "gold_db" for the data
MOVE "gold_log" for the log
Yet these are not present in the NBIMAGE path retrieved from bplist.
I've seen hints that bpflist can get the metadata required, but that's not available on client installs.
How can I replicate the script generation process from the command line to generate the same Move Template as it would if done via the GUI?
06-14-2016 09:05 PM
The bpflist command is:
bpflist -client SQLhost1 -pt MS-SQL-Server -d MM/DD/YYYY
Can Windows client request to run a remote command in master server, and get thre result back? I believe it can be done, just not sure how to do it. Note that master server in latest version has tighter security measure, so this may get more difficult.
06-14-2016 11:22 PM
There is a chapter in the SQL admin guide about create scripts by bplist, there might be some clues there.
There has also been a post here about finding the SQL meta data from the backup images, just can't remember what is was called.
Maybe you can see the relevant commands in the dbclient log when creating the move template through the GUI.