Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 348
  • Last Modified:

Backup to Device (tape) - Hardware Compression?

Hi Guys,

We have an SQL Server 2K database that was approximately 198GB.
- This was backed up to an LTO1 tape drive (Dell PowerVault 110T) and fit on 1 tape - Done through SQL Enterprise Manager.

The database was reaching the full capacity of LTO1 tapes. We upgraded to an LTO2 drive (Dell PowerVault 122T Auto-loader) which has twice the capacity. (200gb native, 400gb compressed)

The database is now at around 203GB, and when we go to do a backup through Enterprise Manager the data has to be spanned across two LTO2 tapes. Im wondering why this is happening and can only guess that there is no hardware compression taking place?

It should easily fit onto 1 LTO2 tape, considering the database is only 5gb larger than when we were using LTO1. With the LTO2 it would get about 98% of the way thorugh the backup before asking for another tape.

I have spoken to Dell who could not recommend anything other than installing BackupExec SQL Agent..They also told me there are no options on the device itself to set any sort of configuration for this.

I know this is a bit borderline Hardware/SQL but i thought this would be a good place to start.

500 points for this one, its rather urgent to us
0
aaron-
Asked:
aaron-
  • 2
1 Solution
 
muzzy2003Commented:
Right, my understanding is that SQL Server BACKUP automatically uses hardware compression if the tape device supports it. Dell's site confirms that the backup software is responsible for setting whether or not hardward compression is enabled. The only thing I can think you might check is this:

DBCC TRACESTATUS (3205)

If this trace flag is on, it specifically disabled the use of hardward compression by BACKUP. It's a long shot, as I would think you'd know this was set if it was, but worth checking. If it is on, then:

DBCC TRACEOFF (3205)

will clear it.
0
 
aaron-Author Commented:
Getting this when attepting the TRACESTATUS:

Trace option(s) not enabled for this connection. Use 'DBCC TRACEON()'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

Im not a real database guru so excuse my ignorance..
0
 
muzzy2003Commented:
OK - just checked, you can't use DBCC TRACESTATUS until you've used a DBCC TRACEON command first. Run these two:

DBCC TRACEON(3205)

then

DBCC TRACEOFF(3205)

See if this sorts out the compression problem. Like I said, it's sort of a long shot, but the only setting I can think of that might allow you to do this with SQL backup.
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now