Video Screencast Help

Redirected SharePoint Restore Failure

Created: 18 Mar 2013 | 4 comments

Hi,

I'm trying to restore a SharePoint 2007 test/development environment using backups of our production environment.

Unfortunately it doesn't work, and the following is logged in the job detail:

03/18/2013 11:05:47 - Error bpbrm (pid=28066) from client web1: ERR - Unable to redirect the restore of SharePoint Portal Server data. Make sure that the specified Web Server exists and the correct credentials are used,that the specified site exists on the Web server, and that the databases being restored exist in the target server farm and are not being used by another portal.

I followed "Redirecting a restore of a SharePoint Web application to another farm" from the admin guide exactly at first.  Later I came across http://www.symantec.com/docs/TECH163540 which contradicts the admin guide:
 
Admin Guide: The target Web application and SQL database name must have new names (different from original names).
 
Technote: *In the destination farm, create a WebApp with the same DB structure as the source. 
  - This includes the same Web App, Port, Virtual App, database names and the path of the db and log data folders on the destination SQL server should be the same as the source SQL server. 
 
Does anyone maybe know which one is correct? I've tried both options without success, so any other tips would be appreciated.
 
NetBackup 7.5.0.5 everywhere.  Master/Media Server is SLES11 SP1, clients are Windows 2003 R2 and SharePoint 2007.
The SharePoint backup user has powerful rights on all systems, as specified in a seemingly related BackupExec note.
Distributed Application mappings were done as per admin guide and technote
Database structures match
 
Some messages from the TAR log file (this is attempting the restore with everything matching):
11:05:47.793 AM: [4416.6152] <2> tar_base::V_vTarMsgM: TAR - Microsoft SharePoint Resources:\Company Shared Services\Intranet\Content-DB 1 (SQL1/WSS_Content_Intranet)\
11:05:47.793 AM: [4416.6152] <2> JobCounter::Initialize: INF - RestoresInProgress Registry Value '401285:2' created
11:05:47.793 AM: [4416.6152] <2> ov_log::V_GlobalLog: INF - bedsSharePointV2Init():ENTER (Reason:4)
11:05:47.793 AM: [4416.6152] <2> ov_log::V_GlobalLog: INF - bedsSharePointV2Init():DLE_FindByName() for '(web1)' 
11:05:47.793 AM: [4416.6152] <2> ov_log::V_GlobalLog: INF - bedsSharePointV2Init():Found Resource DLE for '(web1)'
11:05:47.793 AM: [4416.6152] <4> tar_base::V_vTarMsgW: INF - tar message received from sharepoint_v2_access::V_OpenForWrite()
11:05:47.793 AM: [4416.6152] <2> tar_base::V_vTarMsgW: INF - Redirecting to Portal http://testintranet.
11:05:47.809 AM: [4416.6152] <2> ov_log::V_GlobalLog: INF - FS_ResolveDevName: [Intranet\Content-DB 1 (SQL1/WSS_Content_Intranet)\]
11:05:48.043 AM: [4416.6152] <2> ov_log::V_GlobalLog: INF - GetTopology returned be0, from server web11, as user PRODUCTION\SharePointBackup
11:05:48.043 AM: [4416.6152] <2> ov_log::V_GlobalLog: INF - NOT SQL Device Name: Intranet\Content-DB 1 (SQL1/WSS_Content_Intranet)\
11:05:48.246 AM: [4416.6152] <2> ov_log::V_GlobalLog: INF - GetTopology returned be0, from server web11, as user PRODUCTION\SharePointBackup
11:05:48.246 AM: [4416.6152] <2> ov_log::V_GlobalLog: INF - FS_DleEV::ResolveDeviceName - entering.
11:05:48.246 AM: [4416.6152] <2> ov_log::V_GlobalLog: INF - CMiscUtils::IsGoodEVName - entered.
11:05:48.246 AM: [4416.6152] <2> ov_log::V_GlobalLog: INF - ApplyRegExp(): Invalid input (Intranet\Content-DB 1 (SQL1/WSS_Content_Intranet)\). Parsing Failed.
11:05:48.246 AM: [4416.6152] <2> ov_log::V_GlobalLog: INF - GoodEvName(): Invalid EV device (Intranet\Content-DB 1 (SQL1/WSS_Content_Intranet)\).
11:05:48.246 AM: [4416.6152] <2> ov_log::V_GlobalLog: INF - CMiscUtils::IsGoodEVName - GoodEvName failed for (Intranet\Content-DB 1 (SQL1/WSS_Content_Intranet)\)
11:05:48.246 AM: [4416.6152] <2> ov_log::V_GlobalLog: INF - CMiscUtils::IsGoodEVName - exiting 0
11:05:48.246 AM: [4416.6152] <2> ov_log::V_GlobalLog: INF - FS_DleEV::ResolveDeviceName - IsGoodEVName failed to validate: (Intranet\Content-DB 1 (SQL1/WSS_Content_Intranet)\).
11:05:48.246 AM: [4416.6152] <2> ov_log::V_GlobalLog: INF - FS_DleEV::ResolveDeviceName - exiting. -536805853
11:05:48.246 AM: [4416.6152] <2> ov_log::V_GlobalLog: INF - FS_DleBEAO::ResolveDeviceName - entering.
11:05:48.246 AM: [4416.6152] <2> ov_log::V_GlobalLog: INF - CMiscUtils::IsGoodEVName - entered.
11:05:48.246 AM: [4416.6152] <2> ov_log::V_GlobalLog: INF - ApplyRegExp(): Invalid input (Intranet\Content-DB 1 (SQL1/WSS_Content_Intranet)\). Parsing Failed.
11:05:48.246 AM: [4416.6152] <2> ov_log::V_GlobalLog: INF - GoodEvName(): Invalid EV device (Intranet\Content-DB 1 (SQL1/WSS_Content_Intranet)\).
11:05:48.246 AM: [4416.6152] <2> ov_log::V_GlobalLog: INF - CMiscUtils::IsGoodEVName - GoodEvName failed for (Intranet\Content-DB 1 (SQL1/WSS_Content_Intranet)\)
11:05:48.246 AM: [4416.6152] <2> ov_log::V_GlobalLog: INF - CMiscUtils::IsGoodEVName - exiting 0
11:05:48.246 AM: [4416.6152] <2> ov_log::V_GlobalLog: INF - FS_DleBEAO::ResolveDeviceName - IsGoodEVName failed for (Intranet\Content-DB 1 (SQL1/WSS_Content_Intranet)\)
11:05:48.246 AM: [4416.6152] <2> ov_log::V_GlobalLog: INF - FS_DleBEAO::ResolveDeviceName - exiting.
11:05:48.246 AM: [4416.6152] <2> ov_log::V_GlobalLog: INF - Input Error (e000fe23) for Type: (43)
11:05:48.246 AM: [4416.6152] <2> ov_log::V_GlobalLog: INF - bedsSharePointV2ResolveDevName(): FS_ResolveDevName returned e00084af osId for DLE :-1 DeviceName is Intranet\Content-DB 1 (SQL1/WSS_Content_Intranet)\ 
11:05:48.246 AM: [4416.6152] <2> ov_log::V_GlobalLogEx: ERR - sharepoint_v2_access::V_OpenForWrite(): Redirection of portal failed (0x1:Incorrect function.
) check url http://testintranet 
11:05:48.246 AM: [4416.6152] <4> tar_base::V_vTarMsgW: INF - tar message received from sharepoint_v2_access::V_OpenForWrite()
11:05:48.246 AM: [4416.6152] <2> tar_base::V_vTarMsgW: ERR - Unable to redirect the restore of SharePoint Portal Server data. Make sure that the specified Web Server exists and the correct credentials are used,that the specified site exists on the Web server, and that the databases being restored exist in the target server farm and are not being used by another portal.
11:05:48.246 AM: [4416.6152] <2> tar_base::V_vTarMsgW: ERR - unable to create object for restore: Microsoft SharePoint Resources:\Company Shared Services\Intranet\Content-DB 1 (SQL1/WSS_Content_Intranet)\ (BEDS 0x1: Incorrect function.
)
 
 
 
 
 
Operating Systems:

Comments 4 CommentsJump to latest comment

Mark_Solutions's picture

Looks like it fails creating the SQL Database

Do you have everything setup correctly on the SQL Server, including the account you are using having sysadmin rights?

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

marcelg's picture

 

I think so..

The NetBackup services are configured to run using a domain account that is in the local Administrators group on all the servers involved.  Local Administrators have sysadmin rights on the database.

The Windows Client\SharePoint settings refer to this same account.

I manual restore of the database using the MS SQL Client works correctly.

Mark_Solutions's picture

Looking back through your log it all seems to go wrong quite early on :

11:05:48.246 AM: [4416.6152] <2> ov_log::V_GlobalLog: INF - ApplyRegExp(): Invalid input (Intranet\Content-DB 1 (SQL1/WSS_Content_Intranet)\). Parsing Failed.
 
11:05:48.246 AM: [4416.6152] <2> ov_log::V_GlobalLog: INF - GoodEvName(): Invalid EV device (Intranet\Content-DB 1 (SQL1/WSS_Content_Intranet)\).
 
11:05:48.246 AM: [4416.6152] <2> ov_log::V_GlobalLog: INF - CMiscUtils::IsGoodEVName - GoodEvName failed for (Intranet\Content-DB 1 (SQL1/WSS_Content_Intranet)\)
 
11:05:48.246 AM: [4416.6152] <2> ov_log::V_GlobalLog: INF - CMiscUtils::IsGoodEVName - exiting 0
 
11:05:48.246 AM: [4416.6152] <2> ov_log::V_GlobalLog: INF - FS_DleEV::ResolveDeviceName - IsGoodEVName failed to validate: (Intranet\Content-DB 1 (SQL1/WSS_Content_Intranet)\).

 

So it is either a Farm issue or a SQL issue but it does not seem to be able to validate the first database

Worth getting your SharePoint admin to dould check the setup of the alternate Farm again

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

marcelg's picture

We checked, but cannot find anything out of the ordinary.  Setting up the target farm seems to be very straightforward.  Following the steps under "Recovering a SharePoint 2007 Server (without BMR)" in the admin guide...

For now we just restored and re-attached the content database - it seems to satisfy the short-term testing requirements.