Netbackup, Sharepoint 2007 Cross farm restore - lab enviroment creator

See planning a cross domain replication disaster recovery domain on page 49  PDF, and always perform a full backup prior to and after  any changes to your environment.

Hi Guys,

I’ve got success :) . I recheck everything in Sharepoint backup check list and also find this article TECH158316 as usefull  (Currently is not accessible , Google cache can help ).  

As additional steps I add service account for SharePoint backup to “Netbackup Legacy Client Service”and recreate web application on destination farm to have exact match of IIS port and location of Web Application C:\inetpub\wwwroot\wss\80\

Now I have some troubles with some webparts that are missing after restore, but I think to push these troubles to SharePoint team.

But, (always have BUT J), now I have problem with GRT backup and restores I’m hitting known bug: http://www.symantec.com/business/support/index?page=content&id=TECH87800

GRT Backup completes without any error or warnings, but when I try to restore I cannot select file to restore files and folders appear to be missing.  If I try to restore file which is seen in recovery console, files are restored but their size is 0 KB.

I find following errors in Windows log about NFS and think that they might be the problem:

Source:        NfsRdr

Event ID:      16384

Level:         Warning

Description:  Client for NFS requested a mount with file locking enabled, and the remote Network File System (NFS) server does not support file locking.   Client for NFS mounted the shared resource anyway. File locking may not be available.   To avoid this warning in the future, enable file-locking suppport on the remote NFS server.

-------------------------------- 

Log Name:      Application

Source:        NfsClnt

Event ID:      16397

Level:         Warning

Description: Windows(R) Lightweight Directory Access Protocol (LDAP) failed a request to connect to Active Directory Domain Services(R) for Windows user < \netbackup_user>.   Without the corresponding UNIX identity of the Windows user, the user cannot access Network File System (NFS) shared resources.    Verify that the Windows user is in Active Directory Domain Services and has access permissions.

-------------------------

Do you have any ideas?

Thank you Guys, without your help i couldn’t make it

Hi NDineV, any updates in this case?

Hi Roger C,

I can clarify that restore job is not initiated and is not seen in "Activity Monitor". The beds directory is empty, no logs.

SharePoint on both farms uses default location C:\inetpub\wwwroot\wss\*".

I also delete Web application from test farm and try again restore but same result restore job doesn't start.

Hi,

I noticed that you (step 3) created the Web Application on the Test farm with same structure, I don't think is a necessary step as I thought we created the Web Application on the fly - unless someone else can clarify here.

As I wonder if this created the same original IIS physical path ie "C:\inetpub\wwwroot\wss\*" etc,

I'm also confused as to whether you stated whether the restore actaully initiated this time round and the Job appeared in the Activity Monitor, could you clarify?

To check if the restore had errors - check the <install_path>\Veritas\Netbackup\logs\beds\SPSWrapper00.log on the Frontend commiting the restore.

This will help capture the 'stsadm' commands - which is called in the creating the Web Applciation on the new farm.

Hi Symontec, No.Restriction file is already set onto master server. 

Additionally, I would check the usage of the No.Restrictions file by taking a look of this TN http://www.symantec.com/business/support/index?page=content&id=TECH45378

Just a couple of tips more that I recall from what Symantec Support did:

When you run the BAR Console on the client or the NBConsole, use Right Click on the icon -> Run as administrator.

Another tip (it was not tested) they said is that when you select for restore, do not select from "All Folders" section but from "Contents" pane of the BAR Console.

Hi guys,

I map all SP frontend to production and test  SQL, but again restore job didn't start.

I've killed process bpspserver.exe and then, I try redirected restores of one web application on custom port from production farm to test farm,  in <install_path>\Veritas\Netbackup\logs\sps2vra log i find only this error message:

18:42:49.129 [2740.1652] <2> bprd_start_spss_recovery_asst: Connect to bprd successfully!
18:42:49.129 [2740.1652] <2> bprd_start_spss_recovery_asst: Sent bprdreq successfully!
18:42:49.176 [2740.1652] <2> bprd_start_spss_recovery_asst: Sending 0:Windows SharePoint Services Web Application/SharePoint - 51918/ to master
18:42:49.176 [2740.1652] <2> bprd_start_spss_recovery_asst: get_short failed: 0 14

after that i try GRT restores which works like charm.

I do restore in following orders, am I miss some step?

1) I got Full backup with no errors and fresh installed test  SP farm

2) Configure Distributed REstore Mapping

3) Create Web application on Test farm, I don't create any site collection or SSP 

4) Logon to frontend server from test farm and begin restore process; which didn't run :(

Actully from this how to http://www.symantec.com/business/support/index?page=content&id=HOWTO47543

I didn'tcomplete step 3 Remove the source Web application

Any suggestions?

Great, we will be waiting for your feedback.

Regards,

SAF