Can't backup Windows Server 2008 R2 (X64 Enterprise) with BA client

[Macnbaish]

Opened a PMR with IBM about this.. apparently exclude/include statements have no effect on systemstate backups... it's all or nothing and you cannot exclude individual files.

Based on this my only option is to set the virus scanner to allow access.. McAfee EPO has an option that will allow certain executables to have access to tftp.exe.

Tested it and it's still not working... I'll let you know if I get a McAfee setting that works.

[TykneeTym]

A systemstate backup is done by Windows, not TSM. So TSM excludes don't effect a systemstate backup at all (with the exeception of certain objects, like you can exclude the entire RSM database if you wish).

What I did was just delete tftp.exe (and you'll have to remove it from the system protected files first so it just doesn't copy it back). You'll need to disable (not remove, just disable) McCafee while you're doing this.

We had the same exact problem with several Windows 2003 servers and McCafee

[Macnbaish]

Our McAfee guy was finally able to get a setting set on the EPO server so that McAfee allowed access to TFTP.EXE on this specific server. That fixed the problem. I guess we'll have to do the same on all 2008 R2 Enterprise x64 machines from this point on.

[MartINC]

Hi guys,

About the TSM System State problem that we had (read previous messages; FSRM part), TSM BA Client v 6.1.3.1 is solving it. It add a TESTFLAG SKIPLPM that skips 'missing' system state component in a cluster environment (i.e. some cluster ressources are on NodeA , others on NodeB , TSM whine about some missing 'drives' when backuping System State.)

http://www-01.ibm.com/support/docvie...id=swg21403384

Read fixed Appars for TSM BA Client v. 6.1.3.1

[Jeff_Jeske]

So.... you fellas have no issues running 6.1.*.* client code when the server may be 5.5?

I wonder why IBM continues to update the 5.5 client code rather than focus efforts on 6.1.

We have the same problems on our 2K8 64bit clients (most of which are VMs)

[tanwk3]

Has anyone got this resolved?

I have windows 2008 on cluster. TSM systemstate failed as it does not exclude what I have placed in the registry for Systemstatebackup via windows 2008 backup server feature.

Window backup feature works after this hotfix from http://support.microsoft.com/default...b;EN-US;980794 is applied however TSM systemstate still pick up all those invalid path.

All my invalid paths are on shared cluster disk in such those on passive node will fail.

Anyone have managed to get tsm to backup systemstate successfully? Am running ba client 6.2.2 on Windows 2008 64bit sp2.

TSM Server is 6.2.2 running on windows 2008 Std 64bit sp2.

[tsmdumber]

Hello Folks!

Has anyone got this issue fixed? I have the same error! going to Microsoft is not really an option for me simply because I cant or my windows system-admin wont rather.

Please refer the error below

08/03/2011 12:06:33 psfssub.cpp (4093): psIsHardLink(): Failed to get link information for file <\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy16\ Windows\winsxs\x86_ntprint.inf.resources_31bf3856a d364e35_6.0.6001.18000_en-us_0837c78311803b3e\PCL4RES.DLL.mui>. rc is 5
08/03/2011 12:06:33 ANS1228E Sending of object 'xxxxxxx\SystemState\NULL\System State\SystemState' failed
08/03/2011 12:06:33 ANS4007E Error processing 'xxxxxxx\SystemState\NULL\System State\SystemState': access to the object is denied

Regards,
TSMDumber

[softlover]

Hey, I solved the issue by trying easeus todo backup server half a year ago. And it never happaned from that time on...