Re: Full Backup and restore

One of the things that sharepoint backup and restore doesn't generally get
is the customizations. That is why you need to backup your third party
stuff, and copy the 12 hive.

However, I don't think you can simply copy back the missing bits and have
them work without redeploying them. Maybe Mike Walsh or Daniel know the
answer to that one.

-callahan
"ZAK" <ZAK@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C590B7BB-0FF1-448E-A569-FA873F22C3D2@xxxxxxxxxxxxxxxx
Hi Guys,
Since i was looking for answer to my question related to backup and
restore
and already found this thread so thought to add my question also. May be
it
will help others too. Here is my question.

I've 2 farms one for dev and one for User testing. I have a few site
collections in my dev environment with some 3rd party tools for workflow
creation and some custom web parts that i created. Everthing works fine in
dev environment. Yesterday, i created a backup of all site collections and
restore it in my test environment. All collections restored successfully
with
all subsites and contents. The only issue is, i did not get my custom
features i.e. 3rd party worklow features and my custom web part features
that
i had deployed in my dev environment. I read few MS KBs but there is no
clear
direction to how to handle this.

Is there are way to restore all custom features without redeploying them
in
the test envrionment?

Should i just copy the 12 hive into my test environment to restore the
custom features. Do i've to copy the 12 hive to all the servers or just
WFEs?

Thanks
ZAK
"Daniel Bugday" wrote:

öh..just to clarify the steps..

Install SharePoint (Which creates a new ConfigDB), restore the ContentDB.

Then add the ContentDB to SharePoint using Central Administration or
stsadm.
(what i called attached to ConfigDB)

/Daniel Bugday

"callahan" <cacallahan@xxxxxxxxxxxxxxxxxxx> wrote in message
news:uhZWy8H2HHA.4680@xxxxxxxxxxxxxxxxxxxxxxx
Whoa, wait. Daniel, did you just say that they should restore the
content
database and then attach the new config database to the content
database?
; )~ I think maybe you would install sharepoint, which would create a
new
config database, then restore the content databases and attach new web
applications to them.

But, in addition to backing up the content databases in SQL, and
backing
up the sharepoint specific files on the sharepoint server, I would also
use sharepoint's own backup capabilities.

Artificer, since you are using MOSS 2007, you can use its inbuilt
Backup
and Restore capabilities to first create a full backup of the farm.
Then
you can do differential backups after than. (you can also backup just
certain web applications and their content databases if you'd like)

Then when you rebuild the server, you can restore all of the web
applications and their content databases of the farm.

But, I would also keep the backups of the other separate components;
the
backups of the databases in SQL, and backup of the sharepoint files,
and
even the configuration files in IIS as well.

Daniel is right about backing up all the bits. It never hurts, and
it's
best to not keep all of your eggs in one basket. That way if your
sharepoint backups get lost, you can still at least restore the
contents
of your content databases with the SQL backups.

-callahan
"Daniel Bugday" <itkonsult@xxxxxxxxx> wrote in message
news:A59EE4B3-944A-4E3C-A010-91E4554B01C2@xxxxxxxxxxxxxxxx
Hi,
yes this is possible!

First of all you need a backup of the data from SQL server (the
ContentDB).

Then you need a backup of all SharePoint files on the Web-Front End
Server in your case this is the same machine.

-This files are located under c:\program files\common files\microsoft
shared\web server extensions\12

You also need all customizes files located under the IIS site path
usually located under c:\inetpub (check the path in IIS manager)

You also need the dll's in the GAC.

If SharePoint craches then you need to install SharePoint, restore the
ContentDB, configure the new configDB to attach the restored
ContentDB.

Install all customizations (The best thing here would be if you had a
Solution Package for all the customized files).

Hope this helps!

/Daniel Bugday

"Artificer" <eliezerfigueroa@xxxxxxxxx> wrote in message
news:1186350254.093170.277100@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I installed a SharePoint Portal Server 2007 following the procedure
for a sever farm. But I did install all the components including the
database server on the same computer.

After some daily use I have some sites, documents and appearance
customization running on it.
Now I want to know how to make a "real" full backup. I mean I want to
be able if something goes wrong to make a fresh installation of
SharePoint and restore all those sites, documents and appearance
customization on top of it. Is that possible?

What will be the considerations I should have? Like having the new
computer named in the same way or something like that.








.

Relevant Pages

  • Re: Restoring CompanyWeb
    ... You're probably using SharePoint 2.0 - you would have had to upgrade to get ... Were you using the built-in SBS backup to do a full system backup? ... In your scenario (where you need to do a full system restore to the same ...
    (microsoft.public.windows.server.sbs)
  • Re: Sharepoint Portal Server 2003 Backup: Is it even possible?
    ... So I'm left with spsbackup.. ... The SharePoint Portal Server Data Backup and Restore is a program ... This will help you restore a site. ...
    (microsoft.public.sharepoint.portalserver)
  • Re: Full Backup and restore
    ... I leave Backup and Restore to Daniel:) ... That is why you need to backup your third party stuff, ... creation and some custom web parts that i created. ... But, in addition to backing up the content databases in SQL, and backing ...
    (microsoft.public.sharepoint.portalserver)
  • Re: Restoring CompanyWeb
    ... We've decided to go for SharePoint Online, ... Were you using the built-in SBS backup to do a full system backup? ... In your scenario (where you need to do a full system restore to the same ... be back to a full, working install - Exchange, SharePoint, everything. ...
    (microsoft.public.windows.server.sbs)
  • Re: Trouble restoring STS backup fiel - wrong version
    ... is only for built-in SharePoint backup and restore utilities... ... named 'DST Update for WSS 2.0'... ...
    (microsoft.public.sharepoint.windowsservices)
Loading