Re: Full Backup and restore
- From: "callahan" <cacallahan@xxxxxxxxxxxxxxxxxxx>
- Date: Mon, 6 Aug 2007 19:11:49 -0400
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.
.
- Follow-Ups:
- Re: Full Backup and restore
- From: Daniel Bugday
- Re: Full Backup and restore
- References:
- Full Backup and restore
- From: Artificer
- Re: Full Backup and restore
- From: Daniel Bugday
- Full Backup and restore
- Prev by Date: MOSS not sending email on workflows
- Next by Date: Re: MOSS not sending email on workflows
- Previous by thread: Re: Full Backup and restore
- Next by thread: Re: Full Backup and restore
- Index(es):
Relevant Pages
|