Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Portal "CYA" session

  Asked By: Enrique    Date: Sep 02    Category: Sharepoint    Views: 1278

I'm developing an internal presentation to show internal portal site
collection owners and administrators various ways they can CYA in
the portal. (For those not familiar with the acronym, it stands for
Covering your Backside.) Essentially, I'd like to show them all the
ways they can safeguard their sites against loss of data or major
corruption (as a supplement to the enterprise-level measures).

The list of topics I have include:
- How to backup / restore WSS site collections with FrontPage
- Make copies of .aspx pages before altering them with FrontPage to
provide good recovery points if changes don't work out.
- Use backup / restore in FP to copy your site to the QA platform to
prototype and test major design changes
- Save lists / libaries as templates with / without content. (Along
with the gotchas, limitations and security concerns!)
- Mapping a network place to your portal site to enable quick and
dirty "archiving" of content to a secondary storage location.
- Exporting lists to Excel to make a backup of metadata before
making major alterations (along with gotchas!)
- And, potentially, the power of re-ghosting

Does anyone have any additional ideas I could include? Any serious
warnings to pass along to the audience regarding one of the topics

I'm very willing to share the end result with anyone who contributes!



3 Answers Found

Answer #1    Answered By: Nathaniel Henderson     Answered On: Sep 02

You could use stsadm.exe and spsbackup.exe as these are the normal
backup tools

Answer #2    Answered By: Tanner Moss     Answered On: Sep 02

I think the point here (that Bill is making) the ability (or inability) of
SMigrate or FP GUI interface to backup/restore the site. This backup/restore
does not include  any security  or group permissions and they get dropped out
along with any user personalization (like personal views).

With SPMigrate you will have to re-wire all the security settings where as
with STSADM Backup/Restore they stay in-tact.

Before you start thinking about STSADM, keep in mind that STSADM
backup/restore does not work  at Sub-Site level.

I have just completed a WSS based business critical application roll-out.
This site  is pulling data  from many legacy ERP systems (remember those IBM
terminals?) and augmenting it with additional WSS based functionalities. I
am keeping it under tight control by not allowing the end users to monkey
with any settings at any level like (site/lists/lib/WPart) all they can do
is to update the content  (list items) . I have a sub-site on a separate
Top-Level Site under low SLA where they can do whatever pleases them.

I have a Powerpoint presenations that I can clean and share with the group
but it is quite big in size. Let me know if any one is interested.

Answer #3    Answered By: Bobby Boyd     Answered On: Sep 02

Thanks for the heads up on SMigrate vs. STSADM. I will be sure to
point these out in the presentation.

Didn't find what you were looking for? Find more on Portal "CYA" session Or get search suggestion and latest updates.