WSS 3.0 Backup Problems - Carl

I have a bunch of questions/problems with WSS 3.0 backup, so any help
would really be appreciated.  I'm using WSS 3.0 on Windows Server 2003
with the built-in WID/SQL Embedded database.  I have two site
collections, one of which is still at the absolute default, and the
other one I've added a few subsites and documents.

1.  Backups started from the Central Admin web interface never start.
I'm trying to backup my farm (any part at all) to a local drive (d:
\sharepointbackups) via the Central Admin "Perform a backup"
function.  The backups just sit in "Preparing current backup/restore
job" status forever.  No log is ever created.  The local directory has
Everyone - Full Control permission.  I've logged into WSS as a Domain
Admin, which is also a Site Admin of my two sites.  I've tried
creating a share and using a UNC path instead, but the backup just
hangs at "Preparing".  I can make backups to that directory using
either STSADM or the SQL Management Studio.  Any ideas here?
2. Microsoft's backup/restore documentation is unclear on whether
STSADM is enough to restore a site to a new server.  These two
documents:
http://www.microsoft.com/resources/documentation/wss/2/all/adminguide/en-us/stsf20.mspx?mfr=true
http://www.microsoft.com/resources/documentation/wss/2/all/adminguide/en-us/stsf19.mspx?mfr=true
have given me the impression that I need both the STSADM backup AND
the configuration database to restore a site to a new server.  The
text from those documents says:
******
This [backup and restore] process is not intended for moving a site to
a new server.  If you want to move a site, use the Microsoft
SharePoint Migration Tool (smigrate.exe) instead.  [SMigrate doesn't
move permissions, so it's not useful to me as a disaster recovery
tool.]
AND
You have three options for restoring sites from a backup.
a. You can restore a site over an existing site.
b. You can restore a site to a new site on the same server.
[Confusing statement:] c. You can restore a site to a separate server,
with a separate installation of Windows SharePoint Services that uses
a copy of the original server's configuration database.
*****
3. I can't figure out a way to backup more than a single database at a
time from the WID/SQL Embedded database engine.  I also can't figure
out how to overwrite databases after x number of days.  I could solve
this by creating an individual job for each database on each day, but
there are six databases and seven days in the week,  meaning I'd have
to manage 42 separate jobs.
4. I can't back the databases up remotely with Backup Exec because I
can't figure out how to enable remote access to the WID/SQL Embedded
database engine.  It appears that you can run the SQL Surface Area
configuration tool with SQL Exrpess, but I can't find a download of
this tool for WID/SQL Embedded.  Is it possible to configure remote
access to WID/SQL Embedded?
5. How are other people backing up WSS 3.0 with WID/SQL Embedded?
6. Is the STSADM backup enough to completely restore a site to a new
server, or do you also need the configuration database?
7. Can anyone point me to documentation on exactly what needs to be
done to restore a DB to a new server?

Sorry for all the questions, but I can't deploy WSS until I'm
confident that I have a way to recover it.  Maybe it's just me, but
I'm REALLY disappointed in the documentation that's been provided.
Thanks in advance.

Carl,Have you waited at least an hour for the backup to start? - Marty

Carl,

Have you waited at least an hour for the backup to start? There are also
issues appearing now with the SharePoint Timer Service and Daylight Saving
Time. My backup used to take 10 minutes. It now takes 4 hours. Sharepoint
seems to be full of some major bugs. Please see the following, you may also
be experiencing this problem.

http://support.microsoft.com/kb/932563/en-us

http://www.microsoft.com/technet/community/newsgroups/managed/dgbrowser/en-us/default.mspx?pg=3&guid=&sloc=en-US&dg=microsoft.public.sharepoint.portalserver&fltr=


--
Marty Petroski
Reading, PA, USA

Marty,Thank you for the info. - Carl

Marty,

Thank you for the info.  It seems that waiting a REALLY long time does
seem to be the issue with backing up from the web interface.

Carl

I found the answers with an assist to Mike Walsh. I was looking atthe WSS 2. - Carl

I found the answers with an assist to Mike Walsh.  I was looking at
the WSS 2.0 documentation, which is different from the docs for the
WSS 3.0 STSADM utility.  The backup and restore documentation for WSS
3.0 is here:
http://technet2.microsoft.com/windowsserver/WSS/en/library/5b36d390-3b11-42eb-9150-95634e9019851033.mspx?mfr=true

A GREAT WSS 3.0 backup script written by Jerry Rasmussen is available
here:
http://blogs.threewill.com/worktogetherbetter/Lists/Posts/Post.aspx?ID=40

Thanks to you both.  Great work.

Carl

I was able to resolve this problem by configureing my SharePoint Server not to - Jerry Rasmussen

I was able to resolve this problem by configureing my SharePoint Server
not to automatically adjust for Day light savings time.

Marty, pretty crazy huh? - Steve Gould

Marty, pretty crazy huh? I have the same issue. Besides the backup starting
1 hour after launching it. My backups prior to the DST time change took 1
minute. Seriously, I looked at the history. Now they are taking 2 hours, not
including the 1 hour start delay.