Unfortunately it was decided to move on to MSSQL backups and we tested on
a development dtabase a db of 40Gb with 38GB data takes 37GB on disk !!
Yes, it will. SQL backups aren't compressed and so will take the full space of the data in the DB.
So I thought if it is possible to take bkp on three to four files of 10Gb each it could
help even when tapebkp fails ! We need not have to start the tape backupall over again .
Instead we can identify the files not backed up and start the tape bkp again.
There's no easy way to do that. If the database has 4 filegroups (of 10GB each) you can do filegroup backups, but that's overly complex for this problem. You can stripe a SQL backup over multiple files, but it writes those files in parallel, not serially.
Either get more space on the drive (9GB free is not much), get a new drive that the backups will fit onto, or go back to using the 3rd party tool with backup compression.
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)SQL In The Wild
: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass