Merv
14 years agoLevel 6
Getting sharepoint agent backup and restore to work over private backup LAN
Hi All,
Need some urgent help. have been working for over 2 weeks but not sure if these steps are correct.
I have 2 sharepoint environments, prod and uat - both seperate farms
1 x master and media NBU 7GA (solaris 10)
1 x media NBU 7GA(w 2008 r2)
Sharepoint clients-all w2008r2 with moss2007 NBU 7GA:
UAT/Dev:
1 x frontend
1 x index
1 x backend sql
Prod:
2 x frontend (nlb)
1 x index
2 x backend sql(MSCS)
I was told by support to get backup to work to follow these steps:
On the master/media
Edit the /etc/hosts file and add these:
<backup ip of node1> <public name of node1>
<backup ip of node2> <public name of node2>
<backup ip of node3> <public name of node3>
<backup ip of node4> <public name of node4>
for example:
192.168.1.10 mossfe1
192.168.1.11 mossfe2
192.168.1.12 mossindex
192.168.1.13 mosssql
On each SharePoint node including both passive and active SQL node
1. Edit the c:\windows\system32\drivers\etc\hosts, and add these lines:
<backup ip of that node> <backup name of that node>
<backup ip of the master server> <public name of master server>
for example for mossfe1:
192.168.1.10 mossfe1-bk
192.168.1.15 mynbumaster
2. Open the registry, go to:
HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\NetBackup\CurrentVersion\Config\
On the right hand side, create a String Value key called:
REQUIRED_INTERFACE
And give it the backup name of that node, for example: mossfe1-bk
Additional step for the SQL cluster
From the Cluster Administrator, go to the SQL Server resources and create a virtual IP resource.
Give it a backup IP and bind it with the passive node's backup IP and the active node's backup IP.
Back on the master server
Go to the Host Properties > Clients > double click the node. For example mossfe1.
See if you can access it.
I was first getting error code 26 - handshaking error and now getting a weird Invalid Status Code (-536836945) error after implementing the above:
Error bptm (pid=13393) media manager terminated by parent process
08/30/2010 17:58:25 - Error bpbrm (pid=13384) could not send server status message
08/30/2010 17:58:26 - end writing
Invalid Status Code (-536836945)
However one of the child jobs kicks off and completes with a status 1 backing up some files.
Also another question is configuring my SQL backups based on the above steps. Will it also work properly for the cluster backup and restore?
Thanks in advance.
Merv
Need some urgent help. have been working for over 2 weeks but not sure if these steps are correct.
I have 2 sharepoint environments, prod and uat - both seperate farms
1 x master and media NBU 7GA (solaris 10)
1 x media NBU 7GA(w 2008 r2)
Sharepoint clients-all w2008r2 with moss2007 NBU 7GA:
UAT/Dev:
1 x frontend
1 x index
1 x backend sql
Prod:
2 x frontend (nlb)
1 x index
2 x backend sql(MSCS)
I was told by support to get backup to work to follow these steps:
On the master/media
Edit the /etc/hosts file and add these:
<backup ip of node1> <public name of node1>
<backup ip of node2> <public name of node2>
<backup ip of node3> <public name of node3>
<backup ip of node4> <public name of node4>
for example:
192.168.1.10 mossfe1
192.168.1.11 mossfe2
192.168.1.12 mossindex
192.168.1.13 mosssql
On each SharePoint node including both passive and active SQL node
1. Edit the c:\windows\system32\drivers\etc\hosts, and add these lines:
<backup ip of that node> <backup name of that node>
<backup ip of the master server> <public name of master server>
for example for mossfe1:
192.168.1.10 mossfe1-bk
192.168.1.15 mynbumaster
2. Open the registry, go to:
HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\NetBackup\CurrentVersion\Config\
On the right hand side, create a String Value key called:
REQUIRED_INTERFACE
And give it the backup name of that node, for example: mossfe1-bk
Additional step for the SQL cluster
From the Cluster Administrator, go to the SQL Server resources and create a virtual IP resource.
Give it a backup IP and bind it with the passive node's backup IP and the active node's backup IP.
Back on the master server
Go to the Host Properties > Clients > double click the node. For example mossfe1.
See if you can access it.
I was first getting error code 26 - handshaking error and now getting a weird Invalid Status Code (-536836945) error after implementing the above:
Error bptm (pid=13393) media manager terminated by parent process
08/30/2010 17:58:25 - Error bpbrm (pid=13384) could not send server status message
08/30/2010 17:58:26 - end writing
Invalid Status Code (-536836945)
However one of the child jobs kicks off and completes with a status 1 backing up some files.
Also another question is configuring my SQL backups based on the above steps. Will it also work properly for the cluster backup and restore?
Thanks in advance.
Merv