MOSS 2007/WSS 3.0 Backup & Restore – Limitations

17 03 2009

Hi all,

I realise I have not blog posted for a while now, I have been very busy working on moving and restructuring a load of WSS 3.0 sites & subsites. Whilst doing this I have run into a number of problems so thought I would post my findings here:

  • The STSADM –o backup and STSADM –o restore commands do not work with individual subsites. You can only backup a top-level site collection and restore this. It does backup child subsites beneath the site collection however.
    • Using STSADM –o import and STSADM –o export works for backing up an individual subsite but it does not keep any of the Metadata. This means that the ‘Modified By’ and ‘Modified Date’ are lost for all documents on the site, these columns are simply set to the System Account and the date that the import occurred. It seems that SharePoint treats this command almost like a copy on a file system.
    • Subsites/Site Collections can be backed up and restored using SharePoint Designer but this again does not retain any of the Metadata.

In addition to the above, we ran into a problem when first trying the export and import of a subsite, we received an error message saying –

“Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)”

This is a well documented error, to fix it we had to edit the ‘Fields.xml’ and ‘CTypes.xml’ files in the directory C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES\TSATypes”.

It suggests that the above two XML files contain illegal curly brackets.

We made a backup of the Fields.xml and CTypes.xml files and used notepad to replace ID=”{ with ID=” and }” with “. After editing the files we performed an IISRESET and voila, we could successfully import and export sites.

Hope this helps other people and answers some questions! 🙂

Advertisements

Actions

Information

4 responses

13 05 2009
Sharepoint | Retain List Field Value Assignment « Fides et Ratio

[…] understand when to use export/import vs backup/restore logic, look here : https://sharepointcoding.wordpress.com/2009/03/17/moss-2007wss-30-backup-restore-limitations/ 0 Comments No Comments so far Leave a comment RSS feed for comments on this post. TrackBack […]

25 11 2009
cynthia

[ Using STSADM –o import and STSADM –o export works for backing up an individual subsite but it does not keep any of the Metadata. This means that the ‘Modified By’ and ‘Modified Date’ are lost for all documents on the site, these columns are simply set to the System Account and the date that the import occurred. It seems that SharePoint treats this command almost like a copy on a file system.]

Did anyone find an althernative solution? I ran into the same problem lost “Modified By’ and ;Modified Date’. What can be done? How did you handle this limitation???

3 05 2010
akash

good info for the admins

thanks

3 05 2010
akash

what is the method to over come the not coping of the metadata part….
our company has bought metavis tool , but i dont know if it will solve it

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s




%d bloggers like this: