We're using AvePoint (http://www.avepoint.com/).  It's a easy to use
product and you can do item level restores etc.  Not sure though if you
want to buy software or use out of the box SharePoint.

 

________________________________

From: [email protected] [mailto:[email protected]] On Behalf Of Brendan
Law
Sent: Wednesday, 21 January 2009 2:24 PM
To: [email protected]
Subject: RE: Farm Backups

 

I generally recommend a full SharePoint Server back-up (System and Data
partitions/Virtual hard disk file) and SQL database maintenance plans
(transaction logs hourly, user databases daily, system databases weekly
and the a daily clean up task).  I've never put all that much trust in
the stsadm backups.

 

- Brendan

 

From: [email protected] [mailto:[email protected]] On Behalf Of Paul
Noone
Sent: Wednesday, 21 January 2009 12:43 PM
To: [email protected]
Subject: Farm Backups

 

I've now been right through every TechNet article on this topic and I am
still the none the wiser as to how to perform a "complete" farm backup
and in-place restore using built-in tools (read STSADM and MSSQL and, in
our case, VM images).

 

I'm trying to develop straight-forward robust solutions for both DR and
more general backup/restore requirements.

 

There are two things which I would still dearly love clarified:

*         Deleting existing site collections before restoring in-place

o        This takes one helluva leap of faith.

o        Is this absolutely required and why?

o        Is there an alternative solution?

*         Custom solutions

o        Does any sort of farm-level backup include the solution store?

o        If so, is it recommended to include this?

o        The only other option of redeploying every solution again seems
a bit painful.

Still looking for a definitive, step-by-step guide to performing these
tasks. I appreciate that there is probably no one-click solution
available. If there is, we certainly can't afford it (R1, AvePoint?).
But if anyone has developed/found one and is willign to share, please
let me know!

 

Kind regards,

Paul

 

________________________________

Support procedure: https://www.codify.com/lists/support
List address: [email protected]

Subscribe: [email protected]

Unsubscribe: [email protected]

List FAQ: http://www.codify.com/lists/ozmoss
<http://www.codify.com/lists/ozmoss> 

Other lists you might want to join: http://www.codify.com/lists
<http://www.codify.com/lists> 

 

________________________________

This email is intended for the named recipient only. The information
contained in this message may be confidential, or commercially
sensitive. If you are not the intended recipient you must not reproduce
or distribute any part of the email, disclose its contents to any other
party, or take any action in reliance on it. If you have received this
email in error, please contact the sender immediately and please delete
this message completely from any systems. Confidentiality and legal
privilege are not waived or lost by reason of mistaken delivery to you.

________________________________

Support procedure: https://www.codify.com/lists/support
List address: [email protected]
Subscribe: [email protected]
Unsubscribe: [email protected]
List FAQ: http://www.codify.com/lists/ozmoss
<http://www.codify.com/lists/ozmoss> 
Other lists you might want to join: http://www.codify.com/lists
<http://www.codify.com/lists> 
--------------------------------------------------------------------------------
Support procedure: http://www.codify.com/lists/support
List address: [email protected]
Subscribe: [email protected]
Unsubscribe: [email protected]
List FAQ: http://www.codify.com/lists/ozmoss
Other lists you might want to join: http://www.codify.com/lists

Reply via email to