I personally would never recover the bootstrap from a DD boost device. Why? - because it potentially could create problems, especially with forgotten access information. But I admit this is a very personal decision.
What I have done for years is to daily clone the current bootstrap to a locally attached file type device (FTD) where you can easily monitor its content. You better relabel the volume at the beginning of the process to ensure that it will only hold a single bootstrap. Make sure that you run a full bootstrap backup as the last backup on the old server so that the bootstrap (clone) is up-to-date and will contain all save sets in the media index.
Then copy this directory to the new server (most likely to the same directory), create the appropriate FTD and run the nsrdr command on this device. It will work without problems.
After you recovered the bootstrap, you need to scan the other disk devices device paths or you set these volumes to 'appendable' and mount them.
Scanner and mount (nsrmm) are 2 different commands - you cannot combine them. So please verify exactly when the issue arises. To get more information, add more verbosity to these commands and pipe the output to an appropriate text file.
Also use nsr_render_log and verify what' in the daemon.raw file.
bingo.1
2.4K Posts
0
November 9th, 2020 08:00
I personally would never recover the bootstrap from a DD boost device. Why? - because it potentially could create problems, especially with forgotten access information. But I admit this is a very personal decision.
What I have done for years is to daily clone the current bootstrap to a locally attached file type device (FTD) where you can easily monitor its content. You better relabel the volume at the beginning of the process to ensure that it will only hold a single bootstrap. Make sure that you run a full bootstrap backup as the last backup on the old server so that the bootstrap (clone) is up-to-date and will contain all save sets in the media index.
Then copy this directory to the new server (most likely to the same directory), create the appropriate FTD and run the nsrdr command on this device. It will work without problems.
After you recovered the bootstrap, you need to scan the other disk devices device paths or you set these volumes to 'appendable' and mount them.
Scanner and mount (nsrmm) are 2 different commands - you cannot combine them. So please verify exactly when the issue arises. To get more information, add more verbosity to these commands and pipe the output to an appropriate text file.
Also use nsr_render_log and verify what' in the daemon.raw file.