Search:

Well... much has changed since I started this thread... but here are my findings:

For our storage purchase we decided to buy a pure EMC CX4 sata frame and leverage client side dedupe and...

I'm back.... after a few days of testing and tracing I have it all figured out. Bottom line... dedupe doesn't really work for crap on databases!

I have a 320GB database that will compress down...

So.... after some searching I found the trace values required to determine whether client side dedupe is working for the SQL TDP.

I launched the trace and reviewed the log but am a little cloudy...

I "think" I'm still missing something with my client side configuration.....

How can you tell that your client side dedupe is working? Does the ACT log session report provide dedupe stats? If so...

After nearly two years....I'd like to bring this back as hopefully more people are familiar with dedup operations and such.

We recently shifted to occupancy based licensing providing us unlimited...

Revisiting this because of some testing I did. Prior to using the TDP our DBAs used LiteSpeed. Well lite speed has a GUI that uses the API to backup live data directly to TSM just as the TDP does. ...

So I am still playing around with this..... below is a cut-n-paste of my DSM.OPT file located in the TDPSQL folder:

CLUSTERNODE NO
TCPServeraddress SERVER10.sentry.com
TCPport 1501...

What error are you getting?

Looks like you are sending your DBB to the primary pool. We send ours to the off-site copy pool but that shouldn't matter.

Jeff

Well... here are some of the nuts and bolts... this is how I define both our primary and copy storage. This works for me.

def devc pri_sata_devc devtype=file maxcap=25g...

Neo.. what do you really need? Most of our newer TSM servers backup entirely to SATA disk. They have a smaller diskpool but our DB backup directory is actually sata at a cross town DR site. Works...

I have a TDP mgmt class that binds to a 10 day 10 version retention policy. For the most part my DBA's are very happy with TDP backups however they want a few things that I haven't been able to find...

Taco tuesday bump

I have two SQL servers:

DIX-T-REIDBS-02 (test server) and DIX-Q-REIDBS-02 (qual server)

Both servers have two databases on them. I want to restore database DIX-T-REIDBS-02\SQLDBA1 to...

EDIT: Nevermind I see they are listed in the first thread. Thanks.
TSM server 6.2.2.3 and our Windows BA Cleints are 6.2.3, TDP SQL are 5.5.4

Hmmm.... are they doing full flat file backups to disk or are they doing full TDP with dedup enabled?

Are you using client side dedupe?

We are finally deploying SQL databases that are large enought to require the TDP. I'd like to try client side dedup via the TDP and back it up to our sata file device class.

Do any of you have...

If TSM backs up and moves only data that has changed..... how can that be considered too much? The only way to reduce that is to not run backups as often.

TSM offers both client side...

TSM only knows about what it sent to the device..... if you are using hardward dedup or compression the numbers will not align with the what TSM thinks it can stick on a volume.

^ THIS!

Bravo!

^^LOL^^

So you would delete all versions of your system state.... now that's funny!

Well then you should ask why you are attempting to do it in the first place.

What is the value of this special full backup?

Couldn't you just set up a script inside of the windows scheduler to run the full backup?

I am using the built in tools to back itself up then I use the normal TSM agent to backup the internal backup. I have tested this and actually done the same thing as your customer by migrating to a...

Off topic but.... Isn't keeping only one copy a bit risky? I mean if a problem isn't detected in 24 hours you will lose the only good copy of your system state. With all that can go wrong with...

Just a something to be aware of.... Your mileage may vary when it comes to database size as the cpu, bus, and disk layout plays a MAJOR role in how the DB will perform. We recently grew one of our...

FYI - With new EFI hardware... I started running into this issue with 2008 R2 64BIT and the 6.2.2 client:
http://www-01.ibm.com/support/docview.wss?uid=swg1IC74293

So now version 6.2.3 is...

You are stuck with that approach but you don't have to run it 24/7. You can " can proc" the process then run it only after your daily operations are complete.

That is for the most part correct. We had agents of all shapes and sizes. All are being upgraded to client 6.2.2. In the mean time we also upgraded all of our TSM servers to 5.5.4 (quick and easy...

We have been deploying only 6.2.2 for the last couple of months. I have not run into any problems with this level of agent. The initial system state backup will still capture 50-60k files but...

Even if it costs more.... TSM works and that is my number one concern. I have never worked with another product as powerful and relieable as TSM. It is my feeling that our TSM agents give every...

What are you using to protect your SP environment? We are using TSM for SharePoint and simply select the root of the farm. You can also make two backup plans one to back up A-P and the other to...

Is there an external legal reason to keep the ACT log that long? I work for an insurance company and we haven't been directed to retain our logs for any particular amount of time. We keep 30 days...

I know right!

The good news is it fixes the OCC problem for new and existing servers.

To start off I upgraded a handful of 5.5.3 servers and watched each day as the SS OCC dropped.
...

I did some extensive testing with the 6.2.1.03 client and have since moved to it. The 6.2 code greatly reduces the system state occupancy.

Our servers are still at 5.5.4.

It uses VSS so no it doesn't lock the system.

^ Same here. We have several file servers with millions of files that would take days to recover via incr restore. We run image backups of each data drive to expedite recovery in the event of data...

Why would you want to fall back into old school mode of doing a full vm backup everyday? Doesn't that defeat the purpose of the progressive backup?

We see these from time to time on our file servers. It usually happens on folders with large files. Normally we do nothing but rerun the job and it works fine. I suppose you could try memory...

What checks are required? Why not create a report?

Are you excluding data such as the page file?

Bump....

I have an IBM 3584 library controlled via library manager. This library has 12 drives. When defining newly added drives I accidently criss crossed drive serial numbers for drive5 and...

I guess I misunderstood your licensing concern in the original post. Sorry about that.

Why aren't you streaming large DB backups to tape at your primary site? We have VTL, SATA, and physical...

Are you sure TSM extended edition is really that expensive? Have a sit down with your IBM rep, tell them your concerns and intentions unless they can move on the licensing fees. Everything is...

I'm still confused by the whole VM image backup thing..... one of the largest TSM perks is the incremental forever backup. Now why on earth would you want to change direction and take an image...

We are still on 5.5 so no dedupe for us. We use client side compression on file device type nodes and drive level compression for VTL/Tape. An average of 1400 nodes indicates we get a 40% reduction...