Results 1 to 7 of 7
  1. #1
    Senior Member Stephan's Avatar
    Join Date
    Jun 2004
    Location
    Great White North
    Posts
    645
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default Getting a ANR4976W when backing up my DB?

    ANR4976W The device class S2S_DEVCLASS_DBBACKUPREMOTE is not the same as device class S2S_DEVCLASS_DBBACKUP defined for the serverbackup node $$_TSMDBMGR_$$

    I am getting this warning when backing up my TSM DB. My devclass was S2S_DEVCLASS_DBBACKUP but i ended creating a new one (since we can't rename a devclass) that made more sense as far as naming conventions. Now, the backup still runs, but i keep getting this warning.

    How can i get rid of it? Any thoughts?

    Thanks.
    and all that could have been...

  2. #2
    Moderator moon-buddy's Avatar
    Join Date
    Aug 2005
    Location
    Somewhere in the US
    Posts
    5,857
    Thanks
    4
    Thanked 228 Times in 223 Posts

    Default

    Have you deleted the old DEV CLASS and re-pointed to the NEW one? Removed traces of the old DEV CLASS?
    Last edited by moon-buddy; 09-16-2010 at 08:57 PM.
    Ed

  3. #3
    Senior Member
    Join Date
    Dec 2009
    Location
    Sydney, Australia
    Posts
    384
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    You use "set dbrecovery" to assign the devclass for automatic backups. You get the warning on any dbbackup command which doesn't specify the class defined as the "dbrecovery" class. For me thats at least once per day on every instance (i.e. an onsite to "dbrecovery" and an offsite to something else).

    Spurious and a bit annoying :/

  4. #4
    Senior Member Stephan's Avatar
    Join Date
    Jun 2004
    Location
    Great White North
    Posts
    645
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    Ed: Yes, i've removed my original devclass and replaced it with a new one...If i could have just renamed it, i would have but that option is not available.

    Tony: So you think that if i just reset the dbrecovery, that would do the trick?
    and all that could have been...

  5. #5
    Senior Member
    Join Date
    Dec 2009
    Location
    Sydney, Australia
    Posts
    384
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    That'd probably fix some of the problem... if you're anything like me you'll be running 2x dbbackups per day, one to a local tape pool and one to a remote...if they're in different dev classes (as they are here) then you'll still see the warning on one of the backups.

  6. #6
    Senior Member Stephan's Avatar
    Join Date
    Jun 2004
    Location
    Great White North
    Posts
    645
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    Well let's see then...

    if just issued a "Set dbrecovery S2S_DEVCLASS_DBBACKUPREMOTE" on my server without any issues...
    Let's see how the next backup goes...

    Thanks.
    and all that could have been...

  7. #7
    Senior Member Stephan's Avatar
    Join Date
    Jun 2004
    Location
    Great White North
    Posts
    645
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    Update...

    resetting through the set dbrecovery command indeed got rid of my "warning"...Thanks.
    and all that could have been...

Similar Threads

  1. Backing up Clearcase
    By nikki in forum Backup / Archive Discussion
    Replies: 1
    Last Post: 09-18-2009, 09:05 AM
  2. backing up to tape
    By iamme9182 in forum Backup / Archive Discussion
    Replies: 1
    Last Post: 09-23-2005, 03:10 PM
  3. backing up hp
    By juda in forum Backup / Archive Discussion
    Replies: 1
    Last Post: 02-10-2004, 08:33 PM
  4. backing up certain files on C:
    By rpask in forum Backup / Archive Discussion
    Replies: 6
    Last Post: 07-03-2003, 11:05 AM
  5. Anyone backing up Netware 5.0?
    By mtatte in forum TSM Server
    Replies: 2
    Last Post: 06-18-2003, 05:43 PM

Posting Permissions

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