Bob,

> Definitely on the backup. The restore was never kicked off due to the
> backup failure. In fact, the backup files were all automatically
> deleted after failure.
>
> A slightly larger exerpt of the backup log:
>
> gbak: 1280000 records written
> gbak: 1300000 records written
> gbak: 1320000 records written
> gbak: 1340000 records written
> gbak: 1360000 records written
> gbak: ERROR: free disk space exhausted
> gbak: Exiting before completion due to errors

This error indicates that the target/destination folder/device does not
have enough free disk space for the backup.

> The command line looks like this:
>
> %BinDir%\gbak -b -user %DBUser% -pas %DBPwd% -ig -nt -v -y
> %LogDir%\%BackupLogFile% %DBServerName%:%DBDir%\%DBName%
> %BackupDir%\01%DBName%.Bak 2000000000 %BackupDir%\02%DBName%.Bak
> 2000000000 %BackupDir%\03%DBName%.Bak 2000000000
> %BackupDir%\04%DBName%.Bak 2000000000 %BackupDir%\05%DBName%.Bak
> 2000000000 %BackupDir%\06%DBName%.Bak 2000000000
> %BackupDir%\07%DBName%.Bak 2000000000 %BackupDir%\08%DBName%.Bak
> 2000000000 %BackupDir%\09%DBName%.Bak 2000000000
> %BackupDir%\10%DBName%.Bak
>
> When this script was written in the old days, we were trying to keep
> the backup files under 2GB. Now, we get 9 of those, and one big
> whopper at the end. I guess we could eliminate all of the backup
> files but the last one, however, I doubt that is directly related to
> our problem.

Why are you creating multiple/separate backup files?


Sean