01-01-2020 10:41 PM
Hi all,
I've got a request from a user to restore a server. The server is missing its C drive but the other partition is intact (dont know how they found it). Luckily we have all local drive backup but no BMR. They ask me if C drive can be restored from the backup and make it bootable. Also, can this situation make use of the system state and shadow copy backup?
Thank you
01-01-2020 10:49 PM - edited 01-03-2020 12:06 AM
This TN should help :
01-05-2020 10:38 PM
01-05-2020 11:25 PM
Hi Marianne,
not yet tried this but finished reading it and shared it with the server admin team. We will perform this within this week and let U know the result.
Thank you
01-10-2020 02:24 AM
Hi Marianne,
I got another thing to add in my question. For this client, its last backup was on 2012 and the backup done on old master backup and media server where those server been migrated to new master and media server. However the backup image still valid. During restoration, I stumble upon this issue:
01/10/2020 14:47:17 - begin Restore 01/10/2020 14:47:20 - number of images required: 1 01/10/2020 14:47:20 - media needed: 0164L4 01/10/2020 14:47:22 - restoring from image solman_1329622693 01/10/2020 14:47:22 - Info bpbrm (pid=293844) MSSBA566 is the host to restore to 01/10/2020 14:47:22 - Info bpbrm (pid=293844) telling media manager to start restore on client 01/10/2020 14:47:25 - Info bpbrm (pid=292140) MSSBA566 is the host to restore to 01/10/2020 14:47:25 - connecting 01/10/2020 14:47:25 - Info bpbrm (pid=292140) start tar32 on client 01/10/2020 14:47:27 - Info tar32 (pid=276464) Restore started. 01/10/2020 14:47:27 - connected; connect time: 0:00:00 01/10/2020 14:47:40 - requesting resource 0164L4 01/10/2020 14:47:40 - awaiting resource 0164L4. Waiting for resources. Reason: Tape media server is not active, Media server: MSSBA567, Robot Type(Number): TLD(1), Media ID: N/A, Drive Name: N/A, Volume Pool: N/A, Storage Unit: N/A, Drive Scan Host: N/A, Disk Pool: N/A, Disk Volume: N/A 01/10/2020 14:47:56 - Info bpbrm (pid=293844) terminating bpbrm child 292140 jobid=708401 01/10/2020 14:47:56 - Info bpbrm (pid=293844) child done, status 150 01/10/2020 14:47:56 - Info bpbrm (pid=293844) sending message to media manager: STOP RESTORE solman_1329622693 01/10/2020 14:47:56 - end Restore; elapsed time 0:00:39 01/10/2020 14:47:58 - Error bptm (pid=296072) The following files/folders were not restored: 01/10/2020 14:47:58 - Error bptm (pid=296072) UTF - /C/Program Files/Veritas/NetBackup/version.txt 01/10/2020 14:47:58 - Info bpbrm (pid=293844) media manager for backup id solman_1329622693 exited with status 150: termination requested by administrator termination requested by administrator (150)
I have to canceled the job.
Is this issue related to the fact that the client was backup on the old master server?
01-10-2020 03:28 AM
Whoever performed the migration did not do a proper job.
The images and media ownership are still linked to the old media server:
Tape media server is not active, Media server: MSSBA567
You can transfer all image ownership for MSSBA567 to an active media server that has access to a robot and tape drive that can read media id 0164L4.
Bear in mind that the drive density must match the density of media id 0164L4.
Use this command:
bpimage -newserver <server-name> -oldserver MSSBA567
01-13-2020 04:25 PM
Hi Marianne,
Sorry for not put a few detail about my previous post. The old server is rdp-nb (which the client was backed up to)and as for the MSSBA567 (clustered) is actually our new master server. However, the media server is MSSBA572 which make me wonder why the system pointing at MSSBA567 (master server) instead of MSSBA572 (media server). Is it really related to whether the client was backed up by rdp-nb thus the restoration having this kind of issue?
01-13-2020 04:34 PM
@Marianne wrote:Whoever performed the migration did not do a proper job.
The images and media ownership are still linked to the old media server:
Tape media server is not active, Media server: MSSBA567You can transfer all image ownership for MSSBA567 to an active media server that has access to a robot and tape drive that can read media id 0164L4.
Bear in mind that the drive density must match the density of media id 0164L4.Use this command:
bpimage -newserver <server-name> -oldserver MSSBA567
this is in Master server host properties
01-14-2020 12:14 AM
Media is 'owned' by the media server who wrote the backup.
Maybe the person who performed the merge/migration changed previous environment's media ownership to the master instead of a media server in the new environment.
You can check media ownership of this tape with this command:
bpmedialist -m 0164L4
If media ownership is with the master, then best to change all ownership to a media server, using the command as suggested before. oldserver will be the master and newserver will be the media server in the current environment.
The 'Media Host Override' setting will only work for media and images still 'owned' by rdp-nb.
Why are there 2 entries for the same 'Original server'?
NBU will only use the 1st entry.
01-14-2020 05:07 PM
Hi Marianne,
Based on your reply, the "Media Host Override" settinng must containt the Original backup server (rdp-nb) and Restore server (MSSBA567) or Restore server (MSSBA572)?
Thank you
01-14-2020 05:17 PM
Hi Marianne,
Adding to my previous post, I have do a restore test from other client backed up by the new master server and new media server. From the detail status, I can see the it pointing to the media server the instead of pointing to master server:
01/15/2020 08:56:28 - awaiting resource 0774L6. Waiting for resources. Reason: Drives are in use, Media server: mssba572, Robot Type(Number): TLD(3), Media ID: N/A, Drive Name: N/A, Volume Pool: N/A, Storage Unit: N/A, Drive Scan Host: N/A, Disk Pool: N/A, Disk Volume: N/A
Thank you
01-14-2020 10:44 PM
@goliath_kj wrote:
Hi Marianne,
Based on your reply, the "Media Host Override" settinng must containt the Original backup server (rdp-nb) and Restore server (MSSBA567) or Restore server (MSSBA572)?
Thank you
As per my post that you have marked as Solution - you need to know which server currently 'owns' the media that is needed for resore.
We do not know what exactly was done during the migration/merge of masters.
That is why I asked you to run bpmedialist.
I can point you in the right direction if we have the correct information.
01-15-2020 03:53 PM
Hello Marianne,
I have execute bpmedialist as per suggested. Here is the output:
C:\Program Files\Veritas\NetBackup\bin\admincmd>bpmedialist -m 0164L4 Server Host = rdp-nb id rl images allocated last updated density kbytes restores vimages expiration last read <------- STATUS -------> On Hold -------------------------------------------------------------------------------- 0164L4 9 1 02/19/2012 11:38 02/19/2012 11:38 hcart 124508159 0 1 INFINITY N/A 0
From this output, rdp-nb (old master/media server) is the Server host of the media.
Thank you
01-15-2020 11:52 PM
Please have another look at Media Host Override entries - there are 2 entries for the original media server:
Original Restore server
rdp-nb mssba565
rdp-nb mssba572
NBU will only use the 1st entry and try to use mssba565 as restore media server.
I did not see you mention mssba565 anywhere - so, this server does not seem to be a Media Server, right?
Please delete the entry for mssba565.
You should only have rdp-nb -> mssba572.
It will be best if you move ALL tape and image ownership from rdp-nb (oldserver) to mssba572 (newserver) using the bpimage command.
01-28-2020 05:50 PM
Hello Marianne,
Sorry for the late reply as was on training the other week. I have removed the mssba572 entry in Media Host Override.
And I will move all tape and image image ownership from old server to new server as per adviced and will reply back with the result. Then will seek advice for the next step for the restoration.
Thank you
01-30-2020 05:37 PM
Hello Marianne,
Sorry for the confusion made. Actually the servers detail are:
MSSBA565 (clustered master server)
MSSBA566 & MSSBA567 (physical master server)
MSSBA572 (media server)
Then, I will do as per advice as to remove the mssba565 and only mssba572 remain in the Media Host Override.
01-30-2020 08:01 PM
Hi Marianne,
After change the entry on Media Host Override, I manage to restore a file as test where it was failed before. I will continue to perform the C drive restoration as per link provided before.
Thank you