로그인
 
홈라이브러리학습다운로드지원커뮤니티포럼
Resources for IT Professionals >
> 
> 
Disaster Recovery Plan recommendation for Microsoft Sharepoint Services 3.0

Answered Disaster Recovery Plan recommendation for Microsoft Sharepoint Services 3.0

  • 2012년 5월 17일 목요일 오후 10:11
     
     
    로그인하여 투표
    0

    We are using the Sharepoint Foundation Server 3.0.

    I have created a 2nd server for a test restore. 

    Our backup software is CA ArcServe v16, sp1 with Sharepoint & SQL agents.

    The restore stated successful in ArcServe but data not accessible because I didn't follow critical step:  Critical step states to "rename the Shared Service Provider database (SharedService1) to a new name that does not exist in the original Farm.  Then do the restore.  Then, after the restore, delete the Shared Service Provider."

    I have STSADM Technet article outlining utility but there is no mention of renaming "Shared Service Provider" 

    Can anyone shed any light on this task?

    Thank you all in advance.

    Doug

     

모든 응답

  • 2012년 5월 18일 금요일 오전 3:37
     
     답변됨
    로그인하여 투표
    0

    Hi,

    As you are using SSP this can not be sharepoint foundation it has to be MOSS 2007.

    You can use EDITSSP to rename it.

    Refer :

    http://technet.microsoft.com/en-us/library/cc262727(v=office.12).aspx

    I hope this will help you out.

    Thanks, Rahul Rashu

    • 답변으로 표시됨 Lhan HanModerator 2012년 5월 21일 월요일 오전 6:09
    •  
     
  • 2012년 5월 18일 금요일 오전 7:41
     
     답변됨
    로그인하여 투표
    0

    Please specify the correct product version. As indicated by Rahul, the version you specify does not exist.

    It must be one of the following:

    - Windows SharePoint Services 3.0 (WSS 3.0)

    - Office SharePoint Server 2007 ( MOSS 2007 )

    - SharePoint Foundation 2010 ( aka Windows SharePoint Services 4.0 - WSS 4.0 )

    - SharePoint Server 2010 (SP2010)

    What I expect is happening is that ArcServe does not recognize WSS 3.0 and assumes that MOSS 2007 is installed, hence the message regarding the Shared Services Provider (SSP). WSS 3.0 does not have an SSP, this is a MOSS feature.

    If you are indeed using either WSS 3.0 or SharePoint Foundation, then I would check with your backup solution vendor as these products are not in the supported products as stated in https://support.ca.com/cadocs/0/CA%20ARCserve%20%20Backup%20r16-ENU/Bookshelf_Files/HTML/readme/Readme.html#o1759293

    There is only a mentioning of MOSS 2007 and SharePoint Server 2010

    Dirk Van den Berghe

    • 답변으로 표시됨 Lhan HanModerator 2012년 5월 21일 월요일 오전 6:09
    •  
     
  • 2012년 5월 26일 토요일 오후 2:14
     
     
    로그인하여 투표
    0

    Thank you both for your suggestions.

    I'm using WSS 3.0 on a Windows 2008 R2 server. 

    Please see item #5 on this CA Arcserve Document.  I didn't do this step before the test restore and hence, the test server still points to it's original content database.  In the item it refers to renaming the "Shared Service Provider"

    https://support.ca.com/cadocs/0/CA%20ARCserve%20%20Backup%20r16-ENU/Bookshelf_Files/HTML/sharepnt/index.htm

    Is there a command line to list the "Shared Service Providers" 

    Is there a command line to rename them so I can use the restored content?

    In the CA Documentation it is referred to as "Shared Service Provider".  Is it known by another name in the EDITSSP or STSADM command line utility?

    The CA Support Rep said to rename the content on the test server to another name and then restore from the backup.  I'm assuming that I can also rename the default/current content and subsequently rename the restored content to the default/current name to gain access to this restored content.

    Also, the command line help does not mention "EDITSSP"
     
  • 2012년 5월 27일 일요일 오전 9:41
     
     
    로그인하여 투표
    0

    As mentionned before, WSS 3.0 does not have Shared Service Providers and does not have any commands to list thes SSP's.

    If you want to restore individual content ( documents, list items, subsites, etc...) from a backup without interfering with the existing content I would suggest the following procedure:

    - restore the content database to the SQL instance with a different content database name

    - create a new web application in WSS 3.0 with a different URL (e.g. http://restore.contoso.com)

    - attach the content database to the new web application

    At this point you will be able to access the restored content with the restore URL. If you had a site with url http://original.contoso.com/sites/siteA, then you should have the restored version of this site at http://restore.contoso.com/sites/siteA

    Grab what you need using export or copy fucntionality and restore it to your production sites

    If you want to restore the complete web application, then you can follow the guidelines of your CA Support Rep:

    - stop all SharePoint services on your server

    - rename the existing content database to something else

    - restore the content database from backup

    - start all SharePoint services.

    Again verify with your CA Support Rep that their product also supports WSS 3.0, because if the CA restore continues to ask you about SSP's, then the product thinks you are using MOSS and not WSS.

    Dirk Van den Berghe

     
  • 2012년 6월 26일 화요일 오후 5:53
     
     
    로그인하여 투표
    0

    Thank you for your repsponse.  The question I am asking is in your reply.  "rename the existing content database to something else"

    How can I do this task. 

    I've read the documents and it doesn't register.

    I can do a successful restore but I can not figure out how to rename the existing content database before the restore.

    Thanks in advance.

    Doug