Results 1 to 3 of 3
  1. #1
    Newcomer
    Join Date
    Jan 2003
    Location
    Atlanta, GA
    Posts
    2
    Thanks
    1
    Thanked 0 Times in 0 Posts

    Question Dedup issue on only one DB?

    I have a single database, and not one you might think, that won't client-side dedup like it should. After a full happens, I send another, and the full transmission happens again. I'll freely admit the DB is on the large side, but could that be the factor? All the other databases on this SQL server are deduping just fine!

    This log is from the most recent full backup that was attempted.

    Type: SQL Server
    Action: Legacy Backup
    Components: [redacted DB name, 28 characters long]
    Status: Successful

    Total SQL backups selected: 1
    Total SQL backups attempted: 1
    Total SQL backups completed: 1
    Total SQL backups excluded: 0
    Total SQL backups inactivated: 0
    Total SQL backups deduplicated: 1

    Throughput rate: 25,891.50 Kb/Sec
    Total bytes inspected: 664,055,230,336
    Total bytes transferred: 664,055,230,336
    Total LanFree bytes transferred: 0
    Total bytes before deduplication: 23,936
    Total bytes after deduplication: 23,936
    Data compressed by: 0%
    Deduplication reduction: 0.00%
    Total data reduction ratio: 0.00%
    Elapsed processing time: 25,046.49 Secs

    Any guesses?

  2. #2
    Member
    Join Date
    May 2006
    Posts
    199
    Thanks
    3
    Thanked 6 Times in 5 Posts

    Default

    There is a setting CLIENTDEDUPTXNLIMIT which I read defaults to 50GB. I suspect you are running up against that.

    The CLIENTDEDUPTXNLIMIT option specifies the maximum size of a transaction when client-side deduplicated data is backed up or archived.

    You may be able to work around this by backing up the DB with multiple streams so that each stream sends less than the maximum.

    -Rowl

  3. The Following User Says Thank You to rowl For This Useful Post:

    david_stabler (01-04-2012)

  4. #3
    Newcomer
    Join Date
    Jan 2003
    Location
    Atlanta, GA
    Posts
    2
    Thanks
    1
    Thanked 0 Times in 0 Posts

    Default

    I used SETOPT to update the option file (didn't work), then just restarted TSM. After I did, the next backup came in just fine with a very nice dedup rate (strangely, after doing a few fulls in a row, I got this result:

    Total bytes before deduplication: 658,224,118,656
    Total bytes after deduplication: 28,760,376,005
    Data compressed by: 0%
    Deduplication reduction: 95.64%
    Total data reduction ratio: 95.64%
    Elapsed processing time: 16,363.29 Secs

    Much Better! Thanks!

    )

Similar Threads

  1. Dedup - Is it working?
    By totalstu in forum TSM Installation, Upgrade and Configuration
    Replies: 3
    Last Post: 05-13-2011, 08:17 AM
  2. TSM 6.x dedup
    By rwhtmv in forum TSM Server
    Replies: 9
    Last Post: 04-15-2011, 05:02 PM
  3. Dedup on TSM 6.2
    By javajockey in forum TSM Installation, Upgrade and Configuration
    Replies: 8
    Last Post: 11-16-2010, 01:26 PM
  4. Dedup volumes by OS?
    By Stephan in forum TSM Server
    Replies: 2
    Last Post: 08-02-2010, 01:12 PM
  5. Dedup reporting
    By chriscain in forum TSM Reporting & Monitoring
    Replies: 1
    Last Post: 06-28-2010, 03:40 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •