SHAREPOINTBlogs.com Mirror

MOSS 2007 STSADM: enumsites and backup syntax, ideas

Just a quick post on some work I am doing migrating all the My Sites on my intranet. I was having a tough time outputting the enumerated sites to a text file & finally figured it out, so here is the syntax. My problem was that i was trying to use the -filename toggle instead of ">>", ugh: stsadm -o enumsites -url http://localhost/ >>allsites.txt Then once I had the list, I was able to massage the My Sites list for this type of thing as a big BAT file running Backups: stsadm -o backup -url http://moss-1/personal/name1 -filename c:\mysitebackups\name1.bak stsadm -o backup -url http://moss-1/personal/name2 -filename c:\mysitebackups\name2.bak stsadm -o backup -url http://moss-1/personal/name3 -filename c:\mysitebackups\name3.bak Last, I find this is a nice way to Backup the larger sites with timestamps nested around stsadm backup commands...outputted from a BAT file at the command line. This was good for me to estimate the time it would take for backups / restores in a Test environment in prep for the same thing in Production: time /t stsadm -o backup -url http://moss-1/Sites/Corporate -filename c:\sitebackups\corporate.bak time /t stsadm -o backup -url http://moss-1/Sites/Sales -filename c:\sitebackups\sales.bak time /t Posted on SharePoint Blogs Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks

Backup / Restore

We can need backup/restore our SharePoint for security reasons, or sometimes when we deploy some contents from one server to other one. In SharePoint 2007 we have several choices to save and restore the content. On the Central Administration site we can start backup or restore manually: the Operations page give us possibilities to save our farm, site collection or SSP. We have more freedom if we choose the stsadm command-line tool. Additionally, running these commands as a script, moreover: scheduled...( read more ) Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks

Moving to a new database server (or instance)

There comes a time when SharePoint databases will have to be moved to another database server. The problem is that it is not that easy to just move the databases to a new database server and have everything work. In SharePoint 2003, it was realatively simple to move all the databases, but in 2007 there is alot more involved with communication between the databases making it a more complicated scenario.Outlined below are the steps taken to move a SharePoint farm to a new database server. Perform a farm level backup of the current farm using the SharePoint backup utility in Central Administration. Make sure the backup gets saved to an accesible location either on this server or on the network. Run the SharePoint Products and Technologies Configuration Wizard to disconnect the server from the configuration database. If there is only one server in farm, then all you have to do is that server. If there are multiple servers in the farm, make sure the server running central administration is the last server disconnected from the farm. I don't believe this is a requirement, but I would recommended it anyway. Once all the servers have been removed from the farm. Run the SharePoint Products and Technologies Configuration Wizard on the server to host the central administration site first to create a new SharePoint farm. Once Server is configured, run the configuration wizard on the remaining servers adding them to the new SharePoint farm. Start both the Office SharePoint Services Search...

SharePoint Backup Error - Access to the path 'x' is denied.

To test if the user has access to perform a backup, use the account SharePoint has and run the stsadm utility for a backup. If you see a message like this: C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>stsadm -o backup -backupmethod full -directory " \\vanilla\Backup " Access to the path '\\vanilla\Backup\spbrtoc.xml' is denied. C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN> then you are failing with the permission to access the UNC path. You should get the service account that was used to connect to the database in the original instance (or one with little policy limitations). L og onto the server using this account. The account should be able to access the database server from the SharePoint server running the sts commands, and be able to do the reverse; go from SQL to the SharePoint server. This will give the stsadm utility the service account to use with the connection object. If you can perform the backup procedure of a site you will have found your problem. To fix you will need to check the policies for the account that is registered with SharePoint. If you can execute the stsadm utility and begin the process of backup, then watch the commands that scroll through the window - there will be some SQL statements for the execution of the backup. You can analyse these further to see which part of the connection is failing. And read the log files. Posted on SharePoint Blogs Del.icio.us | Digg It...

A quick note about backup locations in WSS 3.0

As I needed to tamper with a customer site in a virtual lab environment I decided to do a one-off backup of it via the admin GUI. After selecting the farm I decided to back this up to \\sharepointtest\c$\backup - a directory that I as administrator has full access to. To my frustration I got numerous errors that in ways indicated that the SQL databases was broken. Panic ensued until I calmed down and started troubleshooting. It turns out that you can not use the administrative share of C: (or perhaps any path with $ in it, I haven't had time to test yet) in order to make a backup. Once I shared the backup directory on it's own and changed the path to \\sharepointtest\backup the backup went through without a hitch. All the help has to say about backup locations is "The file share must be configured with the correct permissions and be a valid backup location." - something my first choice of backup path lived up to (depending on what a "valid" backup location is, I guess). I guess that there's information about this out there somewhere but it was such a frustrating error that I thought it merited a post of it's own here as well. Posted on SharePoint Blogs Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks

What was the stsadm.exe operation name for a site backup...?

Oh, never mind... I'd rather use AvePoint's DocAve for MOSS2007 anyways! It's really quite a product (an no, I'm not being paid to say that!). You can create multiple backup jobs, each with multiple schedules. You can set retention policies and schedule system archives to clear out old content. You can also preform real-tie SPS2003 to MOSS2007 content migrations. It actually converts the 2003 data in to the new 2007 formats, inserting...

Resolving the "Unable to display this Web Part" problem after SharePoint Designer restore

If you've restored the SharePoint site using commands Site --> Administration --> Restore site and this site had special XSLT data views you may be in for a big surprise! You can receive the following message: Unable to display this Web Part Read More......( read more ) Read More... Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks

SharePoint 2007 : Comment déplacer du contenu SharePoint (partie 2)

Après vous avoir parlé dans le post précédent de backup et restore, de modèle objet et de "web package" pour déplacer du contenu, nous allons maintenant voir d'autre possibilités offertes par SharePoint en la matière : Modèle de Site Utilisez cette f... Mirrored on SharePoint Blogs Posted on SharePoint Blogs...( read more ) Read More... Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks

SharePoint 2007 : Comment déplacer du contenu SharePoint (partie 1)

Une des tâches qui peut vous être demandée lorsque vous travaillez avec SharePoint est de déplacer du contenu (ie : Collection de Sites, Sites, Listes, Documents, etc ...) d'un endroit à un autre pour en faire une copie de sauvegarde ou pour déplacer ... Mirrored on SharePoint Blogs Posted on SharePoint Blogs...( read more ) Read More... Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks

SharePoint Disaster Recovery Tips Using SharePoint and SQL Backups

There are a number of companies out there that utilize SQL transaction log backups for their SharePoint solution. This of course is fine and supported by Microsoft, but if there is a complete disaster then the SharePoint administrator will have to piece everything back together. My recommendation is to run the SharePoint full backup option in conjunction with the SQL Transaction log backups. SharePoint backup / restore (either through the central...