TSM Topics Feed

Sunday, March 02, 2008

Tivoli Storage Manager v5.5...

REPOST: I think this article from Flex is a good one to keep on the front page since TSM 5.5 migrations are only going to continue. Check the comments for solutions to this problem.

Today afternoon I had a little time and tried the brand new v5.5 client on MS Windows platform (x32) and got this error message in the dsmerror.log:
"ANS1009W An error occurred processing the operating system include/exclude statements.
The error was detected while processing: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup\DRM. RC = 13."

I didn't want to believe what I saw. This funny message still exists.
Here is the solution from IBM: ANS1009W DRM FilesNotToBackup RC 13
/* Edit the registry manually... this is the solution in the 21st century... */

Do you have this problem? Here in Hungary, all Windows servers are affected...

I like the TSM concepts itself but I don't even want to think about what ISC 5.5 will be like... ;-)

I really miss the 64bit HSM and Journal on MS Windows (we got only Online image and Open file), where is the IBM 3494 support on HP-UX Itanium (I don't understand why this is a problem for a developer? Someone could really explain it...), on the fly db reorg function (ESTIMATE DBREORGSTAT - What a solution? ), ... but the restartable server-to-server export/import sounds good.

Cheers!

6 comments:

  1. most servers I'm seeing out here in Aus have the same issue. My reading of it (might have been from adsm.org) was that it was a windows issue --> TSM used to ignore the badly formed string in the reg. and not throw errors.. However that caused issues so now we get this stupid little error.

    Agree completely that it's 2007 and just ridiculous that an error like this occurs on every system though..

    ReplyDelete
  2. Why don't they provide a utiliy that scans the registry and asks if you want it modified or not? If so it modifies it for you. I was told over a year ago that the ISC was going to the TSMExpress model (i.e. ISC lite) guess that will not be happening.

    ReplyDelete
  3. it's my regular job when I'm installing a client on w2k3... same in turkey...

    ReplyDelete
  4. More in-depth information can be found here.
    I've tried to visualise this by showing some screendumps.

    http://tsmblog.org/serendipity/index.php?/archives/48-The-case-of-the-DRM-subkey-ANS1009W.html

    When there are some people interested in it (as Chad was asking for a utility) it will not take me too long to write a quick VB2005 tool, that will append the 2nd unicode terminator to the DRM subkey. Let me know :-)

    ReplyDelete
  5. For each windows machine run from cmd:
    reg add \\hostname\HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup /v DRM /t REG_MULTI_SZ /d "C:\Documents and Settings\All Users\DRM\* /s" /f
    Or if you want just for the local machine:
    reg add HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup /v DRM /t REG_MULTI_SZ /d "C:\Documents and Settings\All Users\DRM\* /s" /f

    ReplyDelete
  6. Hi,

    After registry editing do I need to reboot client machines?

    Thanks,
    Igor.

    ReplyDelete