How do I backup Companyweb if I do not have a full version of SQL installed?

When dealing with Companyweb database issues, this is a very common question. Unfortunately the conversation usually takes place after replacement SharePoint databases cannot be accessed or the data found in these databases is missing or corrupt. Often the only type of “backup” a customer may have are copies of the Companyweb databases that have been saved either through NTBackup or some other backup application. In cases that deal with corrupt databases, having copies of these databases is better than nothing, however backing up SharePoint databases should not be considered a “Best Practice” when considering a backup solution for Companyweb data.

What is STSADM.exe

The STSADM.exe tool is specifically designed to backup and restore SharePoint websites and their sub-sites among other things. This tool provides a method for performing SharePoint administration tasks at the command line or by using batch files or scripts. This command-line tool allows you to perform the same tasks found in the Central Administration website, along with other operations and certain parameters that are only available by using the Stsadm command-line tool (these options will not be covered in this particular blog).

Before we Proceed:

If you are using a full version of SQL Server 2000 or SQL Server 2005, using the stsadm.exe utility as the primary backup and restore solution for Windows SharePoint Services is not recommended. Instead, it is recommended that you use the backup tools included with SQL Server for your SharePoint backups.

STSADM.exe – using the Backup and Restore function:

1. The STSADM.exe utility, gives the Administrator the ability to back up and restore individual Web sites hosted on Small Business Server 2003.

2. The tool is used/executed through the command-line and can be found in the \Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\bin (%COMMONPROGRAMFILES%\microsoft shared\web server extensions\60\bin).

3. You must be a member of the server computer's administrators group or a member of the SharePoint administrators group to be able to back up or restore a site.

What does STSADM.exe backup?

1. The content database for the site.

2. All pages in the site.

3. Files in document libraries or lists.

4. Security and permission settings.

5. Feature settings.

Benefits of STSADM.exe

1. The STSADM.exe backup and restore method allows you to replace a site that has become corrupt, or that contains changes that need to be rolled back.
2. You can then restore your site to either the same location or to a new location. (Do not confuse this with the migration of SharePoint sites. Smigrate is still the recommended tool for migration situations)
3. The backup file for a top-level Web site includes any sub-sites of that site.
4. This backup and restore method is not dependent on the type of database you are using.
   1. You can perform this backup and restore method even if you are running Microsoft SQL Server 2000 Desktop Engine (Windows) (WMSDE) instead of Microsoft SQL Server 2000 or SQL Server 2005.
5. If you need to back up a specific site, rather than a whole installation of Windows SharePoint Services, you can do so by using the backup and restore operations with the Stsadm.exe command-line tool.
6. You can automate the backup process by using a batch file, a script, or the Scheduled Tasks item on Microsoft Windows Control Panel.

Things to consider before starting/creating a backup job.

1. STSADM backup and restore are not designed to be used when the server is under active load.
2. The process of backing up and restoring sites takes up both memory and processing power on your server.
3. If a site is in use when the backup operation is run, the data in that site may continue to change throughout the operation. The resulting backup file may be inconsistent with the actual state of the site and, if you restore this file, the restored site or database will be inconsistent as well.
4. To avoid possible inconsistencies, lock the site collection prior to backing to starting the backup.
5. After the backup is complete, set the lock back to "Not locked". For information about locking and unlocking a site collection, see the Managing Locks section of the Configuring Site Collection Quotas and Locks (Windows SharePoint Services 2.0) topic.
6. The process of backing up and restoring sites takes up both memory and processing power on your server. In addition, if you have many sites, or a large amount of data in your sites, the backup process can take a long time, and might result in access errors for your users

Creating a “Manual” backup using STSadm.exe:

1. Create the folder or share where you would like to store the Sharepoint Backups

2. Start\Run\Cmd.exe

3. From a command prompt navigate to the \Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\bin (%COMMONPROGRAMFILES%\microsoft shared\web server extensions\60\bin folder

4. Enter the command stsadm.exe -o backup -url http://companyweb -filename c:\backup\backup.dat -overwrite

5. Enter

6. Insure the backup has been created

Creating a “Scheduled” backup using STSadm.exe with a .vbs script - KB829112:

Here is the .vbs script found in KB829112.  The script was written by David Copeland, who also wrote the "Small Business Server Best Practices Analyzer".   If your not using this already, "Shame on You" :). This utility can cut down on hours of Troubleshooting, and should be in every Small Business Server consultants "toolbox". http://www.microsoft.com/downloadS/details.aspx?familyid=3874527A-DE19-49BB-800F-352F3B6F2922&displaylang=en

Here's David's script:

dim dayweek
dim strBackup
dayweek = datepart("w",(date))
strBackup = """C:\Program Files\Common Files\Microsoft Shared\web server extensions\60\BIN\stsadm""" + _
"-o backup -url http://companyweb -filename x:\backups\companyweb" + cstr(dayweek) + ".dat -overwrite"
Set WshShell = WScript.CreateObject("WScript.Shell")
Return = WshShell.Run(strBackup, 0, true)
Set WshShell = Nothing

Creating a “Scheduled” backup using a batch file:

1. Create a new .txt file in the \Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\bin path

2. Copy the script below into the .txt file - DOS Script

If you are not as familiar with .vbs scripting as you would like to be, here is a DOS script that will help you create the backup as well.

@echo off

echo ===================================

echo Backup Script For Http://companyweb

echo ===================================

cd \program files\common files\microsoft shared\web server extensions\60\bin

@echo off

stsadm.exe -o backup -url http://companyweb -filename c:\backup\backup.dat -overwrite

@echo off

echo completed

3. If using the DOS script, save the .txt file as CompanywebBackupScript.bat.  If using David's script please save it with a .vbs extension. 

4. Verify the CompanywebBackupScript.bat file is in the \Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\bin folder

5. Create a scheduled task to execute the backup script

6. Start\All Programs\Accessories\System Tools\Scheduled Tasks\Add Scheduled task

7. Next

8. Select Browse

9. Browse to \Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\bin\ CompanywebBackupScript.bat

10. Select Open

11. Type a name for the task.

12. Select the frequency you would like the task to run - Next

13. Select Start time and Start date – Next

14. Enter in an account that the process can run under – preferably an administrator account if possible

15. Next – Finish

16. Test the Scheduled task

17. Rt-Click the newly created task – select run

18. Insure the backup was created – Review the backup folder

19. Insure the Backup.dat file is created successfully at the next scheduled execution time.

How do I restore an STSADM.exe backup

1. Move the \Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\bin folder

2. Enter the following command: stsadm.exe -o backup -url http://companyweb -filename c:\backup\backup.dat -overwrite

3. It should return that the "Operation completed successfully".

Thanks,

edwalt

You see the following error "Server Error in '/' Application. Access to the registry key 'Global' is denied" when opening the Web Console in SCOM 2007.   This can also sometimes be seen with the word "Error" only.

Symptoms:

The console works initially, but after a few hours, days or weeks, the console returns the error.

Running IISRESET will also bring the Console back into a working condition.

FIX:

Performance monitoring group was missing the Aspnet and the SCOM Action Account  - Add these groups/accounts - full control.

Gave Network Service account full permissions on the following two folders: c:\windows\system32\inetsvr and c:\windows\debug\usermode.

Modify the permissions for the following:
C:\Windows\Debug\UserMode - Full Perm - Network Service
C:\Windows\System32\InetSrv - Full Perm - Network Service

HKCR\Installer\Assemblies\Global - Full Perm - Network Service and aspnet - Full Perm

>edwalt

There have been several questions/calls concerning issues with opening the WSUS UI after downloading the last update.  Here's the nitty...

http://blogs.technet.com/wsus/archive/2007/11/13/unexpected-ui-errors-in-wsus.aspx

Unexpected UI errors in WSUS

Hi Folks,

We have been hearing reports from some customers who use WSUS that they have been having trouble accessing their administration consoles. We have confirmed the cause of this issue and fixed it on our servers, which will automatically fix the issue for most customers on their next synchronization cycle.  This post will explain the issue in detail and provide steps customers can take to get WSUS working again even sooner.

The cause of this issue is that, on Sunday evening, Microsoft renamed a product category entry for Forefront to clarify the scope of updates that will be included in the future. Unfortunately the category name that was used included the word Nitrogen in double quotes (appearing as “Nitrogen”). A double quote is a restricted character within WSUS, which created an error condition on the administration console.  This issue occurred on many WSUS servers that synchronized with Microsoft servers between 5pm Sunday and 11am Monday Pacific Time.

We renamed the category to eliminate the double quotes on Monday morning at 11am after investigating and validating the problem.  This will fix the issue for any impacted WSUS server the next time it synchronizes with Microsoft’s servers.  We are also improving our publishing tools to make sure that issues like this are caught during the publishing process, before they impact customers.

It’s important to note that WSUS customers whose servers did not synchronize during this time, or end users connecting directly with Windows Update, Microsoft Update, or Automatic Updates are not impacted by this issue.

Impacted WSUS 2.0 or 3.0 customers that did synchronize their servers during the 18-hours the renamed category was live follow one of the steps below to wait for, or address this issue depending on thier WSUS version and UI access: 

1. Wait until the next scheduled synchronization time for the fix to apply automatically

2. If the administration console is operational, perform a manual synchronization in either WSUS 2.0 or 3.0

3. If the administration console is not operational on WSUS 3.0, force a manual synchronization through the WSUS configuration or “OOBE wizard” following these steps:

a. Go to Program Files => Update Services =>administrationsnapin=> run microsoft.updateservices.ui.oobewizard

b. Select next through screens 1-2

c. Select synchronize from Microsoft update (3^rd screen)

d. Select next through 4^th screen

e. Click “Start Connecting” (5^th screen)

f. After connection and synch are complete – either cancel out of wizard (or complete)

4. If the administration console is not operational on WSUS 2.0, force a manual synchronization by running a batch file much like this sample from the command prompt:

Sample:

REM Important: This sample script would work only in a WSUS 2.0 environment

REM This sample script causes the WSUS server to sync from Microsoft Update or its parent WSUS server.

REM This sample script  should be run from the machine where the WSUS server is installed.

FOR /F "tokens=3" %%i in ('reg query "HKLM\SOFTWARE\Microsoft\Update Services\Server\Setup" /v SqlServerName ') do SET WSUSSQLSERVER=%%i

SET STARTSYNCOSQLCMD="%programfiles%\Update Services\Tools\osql\osql.exe" -E -S %WSUSSQLSERVER% -Q "USE SUSDB; BEGIN TRAN; EXEC dbo.spStartCatalogSync; COMMIT TRAN"

echo Running %STARTSYNCOSQLCMD%

%STARTSYNCOSQLCMD%

We sincerely apologize for any inconvenience this may have caused to our customers, and encourage anyone still experiencing difficulties to contact Microsoft support at http://www.support.microsoft.com.  

Bobbie Harder

WSUS, Sr. Program Manager

>edwalt

http://www.microsoft.com/downloads/details.aspx?FamilyId=1A83E112-8677-4E03-83C3-F1B7EBFC3A4B&displaylang=en

>edwalt

This post comes from:

http://blogs.technet.com/cliveeastwood/archive/2007/09/28/system-center-essentials-post-rtm-hotfix-rollup-released-to-the-web.aspx

Please visit the link for additional information and screen-shots.... Thanks Clive!!!!!!!!!

In an aid to specifically resolve the issue http://support.microsoft.com/kb/936481/en-us (The installation of System Center Essentials 2007 fails during the Reporting part of Setup and the following information is logged: "The specified domain does not exist or cannot be contacted") in which the whole installation of System Center Essentials 2007 will roll back (fail), and to allow address several other top issues (see below), a hotfix rollup package has been released and is available here http://www.microsoft.com/downloads/details.aspx?FamilyID=c9f977e4-d26f-4038-88b7-b70b13aa8e3d&DisplayLang=en

What specifically this rollup package fixes:

• 936481 You cannot install the System Center Operations Manager 2007 Reporting feature in a disjointed namespace environment
• 936339 Windows-based computers are not displayed in the Network Topology diagram view in System Center Essentials 2007, and WSUS component parts fail on the Essentials 2007 agents after you deploy the agents
• 937467 Update files not getting downloaded to the Essentials 2007 server when importing updates from a partner catalog

More information on the rollup package will be available shortly in the form of a KB article which, when available (I'll post an update here), will be on http://support.microsoft.com/943111/en-us

Does the hotfix rollup apply to you?

If you already have Essentials installed this hotfix rollup does not apply to you.

If you already have Essentials installed and you experience the symptoms referred to in KB936339 or KB937467 please refer to those KB articles on how to obtain the hotfixes separately so that you can apply them in your environment.

If you currently don't have Essentials installed and believe you will be affected by symptoms referred to in KB936481, KB936339 or KB937467 then this rollup package can certainly help you.

Also for those users registering to download the 90-day evaluation version here http://technet.microsoft.com/en-us/bb738028.aspx , the English downloads (aka US English) include a download of the rollup.

>edwalt