Hi,

Can someone please tell me how you restore a single file that is stored in a
SharePoint database. I know about the Deleted Items folder, but I am more
concerned about a corrupt file. I would like to move to Sharepoint
replacing our current shared folders, but I need to know that restoring
files is achievable without too much effort.

TIA,

Jarryd

Re: Restore individual files in sharepoint by galvin

galvin
Thu Jun 12 06:50:52 CDT 2008

On Jun 12, 6:34=A0am, "Jarryd" <jar...@community.nospam> wrote:
> Hi,
>
> Can someone please tell me how you restore a single file that is stored in=
a
> SharePoint database. =A0I know about the Deleted Items folder, but I am mo=
re
> concerned about a corrupt file. =A0I would like to move to Sharepoint
> replacing our current shared folders, but I need to know that restoring
> files is achievable without too much effort.
>
> TIA,
>
> Jarryd

I would look into a tool like Data Protection Manager for an out-of-
the-box solution to this kind of problem.

Inherently, WSS provides a 2-stage recycle bin, but like you say, that
won't necessarily help with corrupt files. Do you have a big problem
with corrupted files?

Versioning could also serve as a sort of backup process, though it's
maybe a little coarse.

--Paul Galvin, Conchango
RSS @ http://feeds.feedburner.com/PaulGalvinsSharepointSpace
Web site @ http://paulgalvin.spaces.live.com
Twitter @ http://twitter.com/pagalvin (I follow anyone who follows
me)

Re: Restore individual files in sharepoint by Jarryd

Jarryd
Thu Jun 12 10:43:33 CDT 2008

Hi Paul,

Excellent reply. Thanks. Perhaps I am just being a little paranoid as I
hardly ever (knock on wood) have to reach for the tapes, but one does have
to be careful.

I checked out DPM. Looks radical. As for SP it seems as though you do
still need to have a spare recovery farm to recover a single item. From
what I understand DPM recovers the entire content database and then copies
the item to the live SP server. Its nice and automated, but I did find this
on a web page I googled that offers this level of backup/restore, but it
does require more elbow grease when restoring:
To enable recovery of individual SharePoint files


Use the following procedure to schedule a task to enable you to restore
SharePoint files:

1.Click Start, click Control Panel, click Scheduled Tasks, and then click
Add Scheduled Task.

2.Click Next on the first page of the Scheduled Task Wizard.

3.Click Browse, go to %SystemDrive%\Program Files\Common Files\Microsoft
Shared\Web server extensions\60\Bin, and then double-click Stsadm.exe.

4.Select how often you want this task to run, and then click Next.

5.Select a time to run the schedule, and then click Next.

6.Enter administrator credentials, and then click Next.

7.Select the Open advanced properties when I click finish check box, and
then click Finish. A dialog box appears.

8.Click the Task tab, and then in the Run box, type "%SystemDrive%\Program
files\Common files\Microsoft shared\Web server
extensions\60\Bin\Stsadm.exe" -o backup -url http://Companyweb -filename
target path -overwrite, where target path is where you save the backup of
your internal Web site. You must type the quotation marks. Click OK.

After you click OK, a dialog box appears, prompting you to enter
administrator credentials.

Note

If you do not want a duplicate of your SharePoint database in your backup,
you can exclude the location of the database by using the Backup
Configuration Wizard. Excluding the SharePoint database from your backup
does not allow you to restore a previous version of the database that is
more than one day old.


To restore SharePoint files

From the server:

1.Click Start, click Command Prompt, and then type "%SystemDrive%\Program
files\Common files\Microsoft shared\Web server
extensions\60\Bin\Stsadm.exe" -o createsiteinnewdb -url
http://companyweb/sites/RestoredSite -ownerlogin
DOMAIN\administrator -owneremail administrator@DOMAIN.local -databasename
STS_RESTORE, where DOMAIN is your server domain and
administrator@DOMAIN.local is your administrator's e-mail address. Include
the quotation marks as part of the path. Press ENTER.

2.Type "%SystemDrive%\Program files\Common files\Microsoft shared\Web server
extensions\60\Bin\Stsadm.exe" -o restore -url
http://Companyweb/Sites/Restoredsite -filename target path -overwrite, where
target path is the location where you chose to save your SharePoint backup.
Include the quotation marks as part of the path. Press ENTER.

3.Open Internet Explorer. In the address bar, type
http://Companyweb/Sites/Restoredsite. The site that appears is the same as
your company Web site.

4.In the restored site, navigate to the missing file.

5.Right-click the file, select Save Target As, and then select a location to
which to save the file.

6.Repeat steps 4 and 5 for all missing files.

7.Open your company Web site, navigate to the location where the missing
files should be, and then on the SharePoint toolbar, click
Upload Document.

Note

You cannot upload multiple files at the same time using the remainder of the
steps in this procedure. If you have a large number of files to restore to
the same location, click Start, click Server Management, click Internal Web
Site, and then click Import Files.

8.Type the path or browse to the location where you saved the file, and then
on the SharePoint toolbar, click Save and Close.

9.To delete the restored subsite:

a.Click Start, click Server Management, click Internal Web Site, and then
click Central Administration.
b.Under Virtual Server Configuration, click Configure Virtual Server
Settings.
c.Click companyweb.
d.Under Virtual Server Management, click Delete site collection.
e.Type http://Companyweb/Sites/Restoredsite, click OK, and then click
Delete.

10.To delete the content database:

a.Under Virtual Server Management, click Manage content databases.
b.Click STS_RESTORE.
c.Under Remove Content Database, select remove content database, and then
click OK.
d.Click Start, click Command Prompt, and then type osql -E -S
SERVERNAME\SharePoint -Q "drop database sts_restore", where SERVERNAME is
the name of the server running Windows Small Business Server 2003. You must
include the quotation marks. Press ENTER.

DPM looks like a really nice tool if you have an all MS network. Exchange,
SQL, SP and your Windows servers and clients all backed up almost in
realtime with baremetal recovery available too. I am currently looking at
replacing our standard backup option and this might be a runner.

Cheers,

Jarryd

<galvin.paul@gmail.com> wrote in message
news:d643315e-8000-402a-b0f1-d04fcd4d04a0@m3g2000hsc.googlegroups.com...
On Jun 12, 6:34 am, "Jarryd" <jar...@community.nospam> wrote:
> Hi,
>
> Can someone please tell me how you restore a single file that is stored in
> a
> SharePoint database. I know about the Deleted Items folder, but I am more
> concerned about a corrupt file. I would like to move to Sharepoint
> replacing our current shared folders, but I need to know that restoring
> files is achievable without too much effort.
>
> TIA,
>
> Jarryd

I would look into a tool like Data Protection Manager for an out-of-
the-box solution to this kind of problem.

Inherently, WSS provides a 2-stage recycle bin, but like you say, that
won't necessarily help with corrupt files. Do you have a big problem
with corrupted files?

Versioning could also serve as a sort of backup process, though it's
maybe a little coarse.

--Paul Galvin, Conchango
RSS @ http://feeds.feedburner.com/PaulGalvinsSharepointSpace
Web site @ http://paulgalvin.spaces.live.com
Twitter @ http://twitter.com/pagalvin (I follow anyone who follows
me)



Re: Restore individual files in sharepoint by Mike

Mike
Thu Jun 12 11:10:43 CDT 2008

I think we all were assuming that when you refered to the "Deleted Items
folder" you actually meant the SharePoint recycle bins.

That in turn meant that we assumed you had either WSS 3.0 or MOSS 2007.

As you mention SBS 2003, can we assume that you actually are using WSS 2.0 ?

Mike Walsh
WSS FAQ http://www.wssfaq.com / http://wss.collutions.com
no questions by e-mail please



Jarryd wrote:
> Hi Paul,
>
> Excellent reply. Thanks. Perhaps I am just being a little paranoid as I
> hardly ever (knock on wood) have to reach for the tapes, but one does have
> to be careful.
>
> I checked out DPM. Looks radical. As for SP it seems as though you do
> still need to have a spare recovery farm to recover a single item. From
> what I understand DPM recovers the entire content database and then copies
> the item to the live SP server. Its nice and automated, but I did find this
> on a web page I googled that offers this level of backup/restore, but it
> does require more elbow grease when restoring:
> To enable recovery of individual SharePoint files
>
>
> Use the following procedure to schedule a task to enable you to restore
> SharePoint files:
>
> 1.Click Start, click Control Panel, click Scheduled Tasks, and then click
> Add Scheduled Task.
>
> 2.Click Next on the first page of the Scheduled Task Wizard.
>
> 3.Click Browse, go to %SystemDrive%\Program Files\Common Files\Microsoft
> Shared\Web server extensions\60\Bin, and then double-click Stsadm.exe.
>
> 4.Select how often you want this task to run, and then click Next.
>
> 5.Select a time to run the schedule, and then click Next.
>
> 6.Enter administrator credentials, and then click Next.
>
> 7.Select the Open advanced properties when I click finish check box, and
> then click Finish. A dialog box appears.
>
> 8.Click the Task tab, and then in the Run box, type "%SystemDrive%\Program
> files\Common files\Microsoft shared\Web server
> extensions\60\Bin\Stsadm.exe" -o backup -url http://Companyweb -filename
> target path -overwrite, where target path is where you save the backup of
> your internal Web site. You must type the quotation marks. Click OK.
>
> After you click OK, a dialog box appears, prompting you to enter
> administrator credentials.
>
> Note
>
> If you do not want a duplicate of your SharePoint database in your backup,
> you can exclude the location of the database by using the Backup
> Configuration Wizard. Excluding the SharePoint database from your backup
> does not allow you to restore a previous version of the database that is
> more than one day old.
>
>
> To restore SharePoint files
>
> From the server:
>
> 1.Click Start, click Command Prompt, and then type "%SystemDrive%\Program
> files\Common files\Microsoft shared\Web server
> extensions\60\Bin\Stsadm.exe" -o createsiteinnewdb -url
> http://companyweb/sites/RestoredSite -ownerlogin
> DOMAIN\administrator -owneremail administrator@DOMAIN.local -databasename
> STS_RESTORE, where DOMAIN is your server domain and
> administrator@DOMAIN.local is your administrator's e-mail address. Include
> the quotation marks as part of the path. Press ENTER.
>
> 2.Type "%SystemDrive%\Program files\Common files\Microsoft shared\Web server
> extensions\60\Bin\Stsadm.exe" -o restore -url
> http://Companyweb/Sites/Restoredsite -filename target path -overwrite, where
> target path is the location where you chose to save your SharePoint backup.
> Include the quotation marks as part of the path. Press ENTER.
>
> 3.Open Internet Explorer. In the address bar, type
> http://Companyweb/Sites/Restoredsite. The site that appears is the same as
> your company Web site.
>
> 4.In the restored site, navigate to the missing file.
>
> 5.Right-click the file, select Save Target As, and then select a location to
> which to save the file.
>
> 6.Repeat steps 4 and 5 for all missing files.
>
> 7.Open your company Web site, navigate to the location where the missing
> files should be, and then on the SharePoint toolbar, click
> Upload Document.
>
> Note
>
> You cannot upload multiple files at the same time using the remainder of the
> steps in this procedure. If you have a large number of files to restore to
> the same location, click Start, click Server Management, click Internal Web
> Site, and then click Import Files.
>
> 8.Type the path or browse to the location where you saved the file, and then
> on the SharePoint toolbar, click Save and Close.
>
> 9.To delete the restored subsite:
>
> a.Click Start, click Server Management, click Internal Web Site, and then
> click Central Administration.
> b.Under Virtual Server Configuration, click Configure Virtual Server
> Settings.
> c.Click companyweb.
> d.Under Virtual Server Management, click Delete site collection.
> e.Type http://Companyweb/Sites/Restoredsite, click OK, and then click
> Delete.
>
> 10.To delete the content database:
>
> a.Under Virtual Server Management, click Manage content databases.
> b.Click STS_RESTORE.
> c.Under Remove Content Database, select remove content database, and then
> click OK.
> d.Click Start, click Command Prompt, and then type osql -E -S
> SERVERNAME\SharePoint -Q "drop database sts_restore", where SERVERNAME is
> the name of the server running Windows Small Business Server 2003. You must
> include the quotation marks. Press ENTER.
>
> DPM looks like a really nice tool if you have an all MS network. Exchange,
> SQL, SP and your Windows servers and clients all backed up almost in
> realtime with baremetal recovery available too. I am currently looking at
> replacing our standard backup option and this might be a runner.
>
> Cheers,
>
> Jarryd
>
> <galvin.paul@gmail.com> wrote in message
> news:d643315e-8000-402a-b0f1-d04fcd4d04a0@m3g2000hsc.googlegroups.com...
> On Jun 12, 6:34 am, "Jarryd" <jar...@community.nospam> wrote:
>> Hi,
>>
>> Can someone please tell me how you restore a single file that is stored in
>> a
>> SharePoint database. I know about the Deleted Items folder, but I am more
>> concerned about a corrupt file. I would like to move to Sharepoint
>> replacing our current shared folders, but I need to know that restoring
>> files is achievable without too much effort.
>>
>> TIA,
>>
>> Jarryd
>
> I would look into a tool like Data Protection Manager for an out-of-
> the-box solution to this kind of problem.
>
> Inherently, WSS provides a 2-stage recycle bin, but like you say, that
> won't necessarily help with corrupt files. Do you have a big problem
> with corrupted files?
>
> Versioning could also serve as a sort of backup process, though it's
> maybe a little coarse.
>
> --Paul Galvin, Conchango
> RSS @ http://feeds.feedburner.com/PaulGalvinsSharepointSpace
> Web site @ http://paulgalvin.spaces.live.com
> Twitter @ http://twitter.com/pagalvin (I follow anyone who follows
> me)
>
>

Re: Restore individual files in sharepoint by Jarryd

Jarryd
Thu Jun 12 11:46:34 CDT 2008

Hi Mike, I didn't mentionin SBS 2003 myself. The person who wrote a "noddy"
guide on the internet that I found and copy/pasted into my last post did. I
currently run Windows Server 2003 SE with WSS 3.0. I have since watched the
webcast on how DPM actually restores this data and it seems that you simply
need one server as the recovery farm server (that can even be run on a VM)
and this is used to inject the data back in to the content server and update
the production farm server. I aslo watched another more up to date webcast
on DPM. I really like the look of the product. I was going to opt for the
Sonicwall CDP 3440i, which I have not yet discounted, but as I use all MS
products the DPM would appear to be more useful to me. Of course I hvae no
idea what the coset would be as to licencing and hardware required to make
it provide the same level of backup capacity so that is my next step.

Are the steps I found only for WSS2.0? If so, oops, sorry.

Thanks again everyone.

Regards,

Jarryd


"Mike Walsh" <englantilainen@hotmail.com> wrote in message
news:u1qJZbKzIHA.3384@TK2MSFTNGP03.phx.gbl...
>I think we all were assuming that when you refered to the "Deleted Items
>folder" you actually meant the SharePoint recycle bins.
>
> That in turn meant that we assumed you had either WSS 3.0 or MOSS 2007.
>
> As you mention SBS 2003, can we assume that you actually are using WSS 2.0
> ?
>
> Mike Walsh
> WSS FAQ http://www.wssfaq.com / http://wss.collutions.com
> no questions by e-mail please
>
>
>
> Jarryd wrote:
>> Hi Paul,
>>
>> Excellent reply. Thanks. Perhaps I am just being a little paranoid as I
>> hardly ever (knock on wood) have to reach for the tapes, but one does
>> have to be careful.
>>
>> I checked out DPM. Looks radical. As for SP it seems as though you do
>> still need to have a spare recovery farm to recover a single item. From
>> what I understand DPM recovers the entire content database and then
>> copies the item to the live SP server. Its nice and automated, but I did
>> find this on a web page I googled that offers this level of
>> backup/restore, but it does require more elbow grease when restoring:
>> To enable recovery of individual SharePoint files
>>
>>
>> Use the following procedure to schedule a task to enable you to restore
>> SharePoint files:
>>
>> 1.Click Start, click Control Panel, click Scheduled Tasks, and then click
>> Add Scheduled Task.
>>
>> 2.Click Next on the first page of the Scheduled Task Wizard.
>>
>> 3.Click Browse, go to %SystemDrive%\Program Files\Common Files\Microsoft
>> Shared\Web server extensions\60\Bin, and then double-click Stsadm.exe.
>>
>> 4.Select how often you want this task to run, and then click Next.
>>
>> 5.Select a time to run the schedule, and then click Next.
>>
>> 6.Enter administrator credentials, and then click Next.
>>
>> 7.Select the Open advanced properties when I click finish check box, and
>> then click Finish. A dialog box appears.
>>
>> 8.Click the Task tab, and then in the Run box, type
>> "%SystemDrive%\Program files\Common files\Microsoft shared\Web server
>> extensions\60\Bin\Stsadm.exe" -o backup -url http://Companyweb -filename
>> target path -overwrite, where target path is where you save the backup of
>> your internal Web site. You must type the quotation marks. Click OK.
>>
>> After you click OK, a dialog box appears, prompting you to enter
>> administrator credentials.
>>
>> Note
>>
>> If you do not want a duplicate of your SharePoint database in your
>> backup, you can exclude the location of the database by using the Backup
>> Configuration Wizard. Excluding the SharePoint database from your backup
>> does not allow you to restore a previous version of the database that is
>> more than one day old.
>>
>>
>> To restore SharePoint files
>>
>> From the server:
>>
>> 1.Click Start, click Command Prompt, and then type "%SystemDrive%\Program
>> files\Common files\Microsoft shared\Web server
>> extensions\60\Bin\Stsadm.exe" -o createsiteinnewdb -url
>> http://companyweb/sites/RestoredSite -ownerlogin
>> DOMAIN\administrator -owneremail administrator@DOMAIN.local -databasename
>> STS_RESTORE, where DOMAIN is your server domain and
>> administrator@DOMAIN.local is your administrator's e-mail address.
>> Include the quotation marks as part of the path. Press ENTER.
>>
>> 2.Type "%SystemDrive%\Program files\Common files\Microsoft shared\Web
>> server extensions\60\Bin\Stsadm.exe" -o restore -url
>> http://Companyweb/Sites/Restoredsite -filename target path -overwrite,
>> where target path is the location where you chose to save your SharePoint
>> backup. Include the quotation marks as part of the path. Press ENTER.
>>
>> 3.Open Internet Explorer. In the address bar, type
>> http://Companyweb/Sites/Restoredsite. The site that appears is the same
>> as your company Web site.
>>
>> 4.In the restored site, navigate to the missing file.
>>
>> 5.Right-click the file, select Save Target As, and then select a location
>> to which to save the file.
>>
>> 6.Repeat steps 4 and 5 for all missing files.
>>
>> 7.Open your company Web site, navigate to the location where the missing
>> files should be, and then on the SharePoint toolbar, click
>> Upload Document.
>>
>> Note
>>
>> You cannot upload multiple files at the same time using the remainder of
>> the steps in this procedure. If you have a large number of files to
>> restore to the same location, click Start, click Server Management, click
>> Internal Web Site, and then click Import Files.
>>
>> 8.Type the path or browse to the location where you saved the file, and
>> then on the SharePoint toolbar, click Save and Close.
>>
>> 9.To delete the restored subsite:
>>
>> a.Click Start, click Server Management, click Internal Web Site, and
>> then click Central Administration.
>> b.Under Virtual Server Configuration, click Configure Virtual Server
>> Settings.
>> c.Click companyweb.
>> d.Under Virtual Server Management, click Delete site collection.
>> e.Type http://Companyweb/Sites/Restoredsite, click OK, and then click
>> Delete.
>>
>> 10.To delete the content database:
>>
>> a.Under Virtual Server Management, click Manage content databases.
>> b.Click STS_RESTORE.
>> c.Under Remove Content Database, select remove content database, and
>> then click OK.
>> d.Click Start, click Command Prompt, and then type osql -E -S
>> SERVERNAME\SharePoint -Q "drop database sts_restore", where SERVERNAME is
>> the name of the server running Windows Small Business Server 2003. You
>> must include the quotation marks. Press ENTER.
>>
>> DPM looks like a really nice tool if you have an all MS network.
>> Exchange, SQL, SP and your Windows servers and clients all backed up
>> almost in realtime with baremetal recovery available too. I am currently
>> looking at replacing our standard backup option and this might be a
>> runner.
>>
>> Cheers,
>>
>> Jarryd
>>
>> <galvin.paul@gmail.com> wrote in message
>> news:d643315e-8000-402a-b0f1-d04fcd4d04a0@m3g2000hsc.googlegroups.com...
>> On Jun 12, 6:34 am, "Jarryd" <jar...@community.nospam> wrote:
>>> Hi,
>>>
>>> Can someone please tell me how you restore a single file that is stored
>>> in a
>>> SharePoint database. I know about the Deleted Items folder, but I am
>>> more
>>> concerned about a corrupt file. I would like to move to Sharepoint
>>> replacing our current shared folders, but I need to know that restoring
>>> files is achievable without too much effort.
>>>
>>> TIA,
>>>
>>> Jarryd
>>
>> I would look into a tool like Data Protection Manager for an out-of-
>> the-box solution to this kind of problem.
>>
>> Inherently, WSS provides a 2-stage recycle bin, but like you say, that
>> won't necessarily help with corrupt files. Do you have a big problem
>> with corrupted files?
>>
>> Versioning could also serve as a sort of backup process, though it's
>> maybe a little coarse.
>>
>> --Paul Galvin, Conchango
>> RSS @ http://feeds.feedburner.com/PaulGalvinsSharepointSpace
>> Web site @ http://paulgalvin.spaces.live.com
>> Twitter @ http://twitter.com/pagalvin (I follow anyone who follows
>> me)



Re: Restore individual files in sharepoint by galvin

galvin
Thu Jun 12 13:11:44 CDT 2008

On Jun 12, 12:46=A0pm, "Jarryd" <jar...@community.nospam> wrote:
> Hi Mike, I didn't mentionin SBS 2003 myself. =A0The person who wrote a "no=
ddy"
> guide on the internet that I found and copy/pasted into my last post did. =
=A0I
> currently run Windows Server 2003 SE with WSS 3.0. =A0I have since watched=
the
> webcast on how DPM actually restores this data and it seems that you simpl=
y
> need one server as the recovery farm server (that can even be run on a VM)=

> and this is used to inject the data back in to the content server and upda=
te
> the production farm server. =A0I aslo watched another more up to date webc=
ast
> on DPM. =A0I really like the look of the product. =A0I was going to opt fo=
r the
> Sonicwall CDP 3440i, which I have not yet discounted, but as I use all MS
> products the DPM would appear to be more useful to me. =A0Of course I hvae=
no
> idea what the coset would be as to licencing and hardware required to make=

> it provide the same level of backup capacity so that is my next step.
>
> Are the steps I found only for WSS2.0? =A0If so, oops, sorry.
>
> Thanks again everyone.
>
> Regards,
>
> Jarryd
>
> "Mike Walsh" <englantilai...@hotmail.com> wrote in message
>
> news:u1qJZbKzIHA.3384@TK2MSFTNGP03.phx.gbl...
>
>
>
> >I think we all were assuming that when you refered to the "Deleted Items
> >folder" you actually meant the SharePoint recycle bins.
>
> > That in turn meant that we assumed you had either WSS 3.0 or MOSS 2007.
>
> > As you mention SBS 2003, can we assume that you actually are using WSS 2=
.0
> > ?
>
> > Mike Walsh
> > WSS FAQhttp://www.wssfaq.com/http://wss.collutions.com
> > no questions by e-mail please
>
> > Jarryd wrote:
> >> Hi Paul,
>
> >> Excellent reply. =A0Thanks. =A0Perhaps I am just being a little paranoi=
d as I
> >> hardly ever (knock on wood) have to reach for the tapes, but one does
> >> have to be careful.
>
> >> I checked out DPM. =A0Looks radical. =A0As for SP it seems as though yo=
u do
> >> still need to have a spare recovery farm to recover a single item. =A0F=
rom
> >> what I understand DPM recovers the entire content database and then
> >> copies the item to the live SP server. =A0Its nice and automated, but I=
did
> >> find this on a web page I googled that offers this level of
> >> backup/restore, but it does require more elbow grease when restoring:
> >> To enable recovery of individual SharePoint files
>
> >> Use the following procedure to schedule a task to enable you to restore=

> >> SharePoint files:
>
> >> 1.Click Start, click Control Panel, click Scheduled Tasks, and then cli=
ck
> >> Add Scheduled Task.
>
> >> 2.Click Next on the first page of the Scheduled Task Wizard.
>
> >> 3.Click Browse, go to %SystemDrive%\Program Files\Common Files\Microsof=
t
> >> Shared\Web server extensions\60\Bin, and then double-click Stsadm.exe.
>
> >> 4.Select how often you want this task to run, and then click Next.
>
> >> 5.Select a time to run the schedule, and then click Next.
>
> >> 6.Enter administrator credentials, and then click Next.
>
> >> 7.Select the Open advanced properties when I click finish check box, an=
d
> >> then click Finish. A dialog box appears.
>
> >> 8.Click the Task tab, and then in the Run box, type
> >> "%SystemDrive%\Program files\Common files\Microsoft shared\Web server
> >> extensions\60\Bin\Stsadm.exe" -o backup -urlhttp://Companyweb-filename
> >> target path -overwrite, where target path is where you save the backup =
of
> >> your internal Web site. You must type the quotation marks. Click OK.
>
> >> After you click OK, a dialog box appears, prompting you to enter
> >> administrator credentials.
>
> >> Note
>
> >> If you do not want a duplicate of your SharePoint database in your
> >> backup, you can exclude the location of the database by using the Backu=
p
> >> Configuration Wizard. Excluding the SharePoint database from your backu=
p
> >> does not allow you to restore a previous version of the database that i=
s
> >> more than one day old.
>
> >> To restore SharePoint files
>
> >> From the server:
>
> >> 1.Click Start, click Command Prompt, and then type "%SystemDrive%\Progr=
am
> >> files\Common files\Microsoft shared\Web server
> >> extensions\60\Bin\Stsadm.exe" -o createsiteinnewdb -url
> >>http://companyweb/sites/RestoredSite-ownerlogin
> >> DOMAIN\administrator -owneremail administra...@DOMAIN.local -databasena=
me
> >> STS_RESTORE, where DOMAIN is your server domain and
> >> administra...@DOMAIN.local is your administrator's e-mail address.
> >> Include the quotation marks as part of the path. Press ENTER.
>
> >> 2.Type "%SystemDrive%\Program files\Common files\Microsoft shared\Web
> >> server extensions\60\Bin\Stsadm.exe" -o restore -url
> >>http://Companyweb/Sites/Restoredsite-filename target path -overwrite,
> >> where target path is the location where you chose to save your SharePoi=
nt
> >> backup. Include the quotation marks as part of the path. Press ENTER.
>
> >> 3.Open Internet Explorer. In the address bar, type
> >>http://Companyweb/Sites/Restoredsite. The site that appears is the same
> >> as your company Web site.
>
> >> 4.In the restored site, navigate to the missing file.
>
> >> 5.Right-click the file, select Save Target As, and then select a locati=
on
> >> to which to save the file.
>
> >> 6.Repeat steps 4 and 5 for all missing files.
>
> >> 7.Open your company Web site, navigate to the location where the missin=
g
> >> files should be, and then on the SharePoint toolbar, click
> >> Upload Document.
>
> >> Note
>
> >> You cannot upload multiple files at the same time using the remainder o=
f
> >> the steps in this procedure. If you have a large number of files to
> >> restore to the same location, click Start, click Server Management, cli=
ck
> >> Internal Web Site, and then click Import Files.
>
> >> 8.Type the path or browse to the location where you saved the file, and=

> >> then on the SharePoint toolbar, click Save and Close.
>
> >> 9.To delete the restored subsite:
>
> >> =A0 a.Click Start, click Server Management, click Internal Web Site, an=
d
> >> then click Central Administration.
> >> =A0 b.Under Virtual Server Configuration, click Configure Virtual Serve=
r
> >> Settings.
> >> =A0 c.Click companyweb.
> >> =A0 d.Under Virtual Server Management, click Delete site collection.
> >> =A0 e.Typehttp://Companyweb/Sites/Restoredsite, click OK, and then clic=
k
> >> Delete.
>
> >> 10.To delete the content database:
>
> >> =A0 a.Under Virtual Server Management, click Manage content databases.
> >> =A0 b.Click STS_RESTORE.
> >> =A0 c.Under Remove Content Database, select remove content database, an=
d
> >> then click OK.
> >> =A0 d.Click Start, click Command Prompt, and then type osql -E -S
> >> SERVERNAME\SharePoint -Q "drop database sts_restore", where SERVERNAME =
is
> >> the name of the server running Windows Small Business Server 2003. You
> >> must include the quotation marks. Press ENTER.
>
> >> DPM looks like a really nice tool if you have an all MS network.
> >> Exchange, SQL, SP and your Windows servers and clients all backed up
> >> almost in realtime with baremetal recovery available too. =A0I am curre=
ntly
> >> looking at replacing our standard backup option and this might be a
> >> runner.
>
> >> Cheers,
>
> >> Jarryd
>
> >> <galvin.p...@gmail.com> wrote in message
> >>news:d643315e-8000-402a-b0f1-d04fcd4d04a0@m3g2000hsc.googlegroups.com...=

> >> On Jun 12, 6:34 am, "Jarryd" <jar...@community.nospam> wrote:
> >>> Hi,
>
> >>> Can someone please tell me how you restore a single file that is store=
d
> >>> in a
> >>> SharePoint database. I know about the Deleted Items folder, but I am
> >>> more
> >>> concerned about a corrupt file. I would like to move to Sharepoint
> >>> replacing our current shared folders, but I need to know that restorin=
g
> >>> files is achievable without too much effort.
>
> >>> TIA,
>
> >>> Jarryd
>
> >> I would look into a tool like Data Protection Manager for an out-of-
> >> the-box solution to this kind of problem.
>
> >> Inherently, WSS provides a 2-stage recycle bin, but like you say, that
> >> won't necessarily help with corrupt files. =A0Do you have a big problem=

> >> with corrupted files?
>
> >> Versioning could also serve as a sort of backup process, though it's
> >> maybe a little coarse.
>
> >> --Paul Galvin, Conchango
> >> =A0 RSS @http://feeds.feedburner.com/PaulGalvinsSharepointSpace
> >> =A0 Web site @http://paulgalvin.spaces.live.com
> >> =A0 Twitter @http://twitter.com/pagalvin(I follow anyone who follows
> >> me)- Hide quoted text -
>
> - Show quoted text -

I mentioned DPM because I saw MSFT present it at a user group meeting
in New Jersey. I blogged about it here, along with some pricing they
quoted at the meeting: http://paulgalvin.spaces.live.com/Blog/cns!1CC1EDB3DA=
A9B8AA!975.entry

--Paul G