Hi, you could use something like:

-- create table

CREATE TABLE #backupfile_header

(

BackupName nvarchar(128), BackupDescription nvarchar(255), BackupType smallint, ExpirationDate datetime, Compressed tinyint, Position smallint, DeviceType tinyint,

UserName nvarchar(128), ServerName nvarchar(128), DatabaseName nvarchar(128), DatabaseVersion...

Also, if the filename ist allways the same, you should use:

COPY /Y D:\archivo.BAK D:\PRUEBA\archivo.BAK

^

Otherwise the copy-cmd just results in a prompt if overwriting...

What i do is backup TA-logs with truncate and then backup DB1 at 20:00. This backup is then restored on the standby-server.

Also i backup TA-logs every 15 minutes, without cutting...

Difficult to do that. If SQL-Server crashes he probably won't be able to notify you.

You might consider to use Big Brother to monitor your server processes:

http://www.bb4.org/

As far as i know parallel backup does not simply back the same content to different media, it _divides_ the content between the media to speed up the backup.

Therefore you...

What you should do is to

1. get the collation that your commercial app uses

2. change the SQL-Server to that collation, and

3. then use the app to create its database

Karl...

Is 'h:\xxxxxx.bak' always the same file?

Are you appending?

Did you try to delete the file 'h:\xxxxxx.bak' and do the backup afterwards?

Did you try another Filename?

On the SQL-Server, using SQL-Server Network-configuration, is named pipes still activated?

And if your Backups go out of sync you might use something like:

SET QUOTED_IDENTIFIER OFF

GO

SET ANSI_NULLS OFF

GO

/****** Objekt: Benutzerdefinierte Funktion dbo.HexToInt Skriptdatum: 28.06.2004 15:26:53...

Have there been recent changes in your network?

Named pipes are not routable, so perhaps they don't work anymore?

To use UNC-Paths for a backup you have to use T-SQL, its not possible (as far as i know) to use the EnterpriseManager.

Use BACKUP database TO DISK='\\Server\share\path\file' WITH INIT, SKIP,...

An other question: Is he doing the Export with a bulk copy with no_log-option?

The best way would be to not (mis)use the SQL-Server as Fileserver but to use an other Server.

If you must use the SQL-Server, and you want to create the share...

Here is another procedure - is's restoring the TA-logs depending on the current-LSN in the recovery-database:

Note: its restoring logs of an original database named 'SITESQL' -- You should change that...

Perhaps saomething like:

/* Ckange every users password to random number */

/* (c) Karl Klingler 26.03.2004 */

-- Hier muss die richtige Datenbank angewählt werden!!!

use master

-- Variablen deklarieren

declare @seed smallint;

declare @pwd sysname;...