Backup of a WSS site with STSADM.EXE

I want to backup an entire site in WSS 2.0 (including subsites and published
web parts and documents).
I haven't founded the documentation related that explains the use of the
various options of STSADM command.
Is it correct this statement?
"C:\Programmi\File comuni\Microsoft Shared\web server
extensions\60\BIN\STSADM" -o backup -url http://localhost -filename
"D:\BACKUP PORTALE\PortaleRia.BAK" -overwrite
Does exist the documentation that illustrates the use of the parameters of
STSADM command?
Many thanks for your helps.I think you sent this to the wrong newsgroup. This is for Reporting
Services. You might want to post to
microsoft.public.sharepoint.windowsservices instead.
But anyway, to answer your question, you can find more information about
backup and restore of WSS 2.0 at
"Backing Up and Restoring Web Sites"
http://www.microsoft.com/resources/documentation/wss/2/all/adminguide/en-us/stsf20.mspx?mfr=true
This article gives you some examples for using stsadm for backup and
restore, describing the parameters and what to do.
If you need more info, you'll probably get more responses in that other
newsgroup. :)
Kaisa M. Lindahl Lervik
"Pasquale" <Pasquale@.discussions.microsoft.com> wrote in message
news:CF13615B-6C76-4554-BC16-8658A60CB471@.microsoft.com...
>I want to backup an entire site in WSS 2.0 (including subsites and
>published
> web parts and documents).
> I haven't founded the documentation related that explains the use of the
> various options of STSADM command.
> Is it correct this statement?
> "C:\Programmi\File comuni\Microsoft Shared\web server
> extensions\60\BIN\STSADM" -o backup -url http://localhost -filename
> "D:\BACKUP PORTALE\PortaleRia.BAK" -overwrite
> Does exist the documentation that illustrates the use of the parameters of
> STSADM command?
> Many thanks for your helps.
>

Backup of 9Gb Database

Hello all,
i was wandering if there are any documentation/suggestions on how to implement a backup that will not interrupt usage of database?
Basically we have a application that need to be available 24/7.
We have 2 servers, one is a primary, second using the log shipping function in case primary server dies. Howerver once a day when we perform full database backup system become non-responsive for 30-45 minutes.
Is there any ways around it? what are the best practice? We are thinking of creating the cluster of 2-3 SQL servers, however from what i have read, there is still going to be the same issue with backup on clusters.
Thanks.

To limit the time, you can use tools like SQL Litespeed. This will bring the dump size down to about 25% to 30% of the original size. Also the amount of I/O will be less, because the OS has to read the same amount of I/O from the database, but less amount of I/O to the dump-file. Also the time needed to complete the dump is about 25% to 30% less than normal dumps.

Second option to consider is the snapshot option. Create a snapshot of the database and make a dump of the snapshot database (if that is possible)

|||

Hi Kiryl,

MSSQL utilises "hot backups" that should not in any way cause interruption to service - most certainly not to the magnitude of 40 mins!

When you say "unresponsive", what form is this taking? Blocking, locking, cpu flat-line etc?

Cheers

Rob

Backup of 9Gb Database

Hello all,
i was wandering if there are any documentation/suggestions on how to implement a backup that will not interrupt usage of database?
Basically we have a application that need to be available 24/7.
We have 2 servers, one is a primary, second using the log shipping function in case primary server dies. Howerver once a day when we perform full database backup system become non-responsive for 30-45 minutes.
Is there any ways around it? what are the best practice? We are thinking of creating the cluster of 2-3 SQL servers, however from what i have read, there is still going to be the same issue with backup on clusters.
Thanks.

To limit the time, you can use tools like SQL Litespeed. This will bring the dump size down to about 25% to 30% of the original size. Also the amount of I/O will be less, because the OS has to read the same amount of I/O from the database, but less amount of I/O to the dump-file. Also the time needed to complete the dump is about 25% to 30% less than normal dumps.

Second option to consider is the snapshot option. Create a snapshot of the database and make a dump of the snapshot database (if that is possible)

|||

Hi Kiryl,

MSSQL utilises "hot backups" that should not in any way cause interruption to service - most certainly not to the magnitude of 40 mins!

When you say "unresponsive", what form is this taking? Blocking, locking, cpu flat-line etc?

Cheers

Rob

Backup format

Hi,

Does anyone know of any documentation/web page that details SQL SERVER 7
backup format? Thanks.

Jon.Jon <jonov@.iprimus.com.au> wrote in message news:<4008f085_1@.news.iprimus.com.au>...
> Hi,
> Does anyone know of any documentation/web page that details SQL SERVER 7
> backup format? Thanks.
> Jon.

As far as I'm aware, the backup format is not documented. There are
third party backup products that seem to be based on a knowledge of
the format (eg. restore a single object without restoring the whole
backup), but if so, I'd guess they were developed under NDA.

Simon