1. Please help support our sponsors by considering their products and services.
    Our sponsors enable us to maintain high-speed Internet connection and fast webservers.
    They support this free information and knowledge exchange forum service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions

Updated all nodes

Discussion in 'TSM Operation' started by moon-buddy, Nov 9, 2017.

  1. moon-buddy

    moon-buddy ADSM.ORG Moderator

    Joined:
    Aug 24, 2005
    Messages:
    6,849
    Likes Received:
    363
    Occupation:
    Electronics Engineer, Security Professional
    Location:
    Somewhere in the US
    By mistake I updated all nodes and pointed all to one domain.

    Easily fixed, I thought. Restored to the last DB backup and when I looked into it, the nodes are still pointing to the single domain!

    Running 7.1.7.1 on Redhat.

    Am I wrong on concluding that the domain should go back to what it was used to be? If not, this blows away all of my 'understanding of how things work'! A bug?
     
    Last edited: Nov 9, 2017
  2.  
  3. marclant

    marclant ADSM.ORG Moderator

    Joined:
    Jun 16, 2006
    Messages:
    2,606
    Likes Received:
    370
    Occupation:
    Accelerated Value Specialist for Spectrum Protect
    Location:
    Canada
    Probably did a most recent state restore. The logs rollforward and all the transactions after the DB backup got replayed. You'd have to do a PIT restore to avoid rolling forward the logs.
     
  4. moon-buddy

    moon-buddy ADSM.ORG Moderator

    Joined:
    Aug 24, 2005
    Messages:
    6,849
    Likes Received:
    363
    Occupation:
    Electronics Engineer, Security Professional
    Location:
    Somewhere in the US
    I deleted the TSM DB and did just a plain restore db. I should have done a point in time?
     
  5. marclant

    marclant ADSM.ORG Moderator

    Joined:
    Jun 16, 2006
    Messages:
    2,606
    Likes Received:
    370
    Occupation:
    Accelerated Value Specialist for Spectrum Protect
    Location:
    Canada
    If the archive log directory is there and contains the logs since the last backup, it will roll them forward. That's what's called "restore to must current state". Need a PIT to restore to a point in time, in case, that time is your last DB backup. You can do PITD=now and it will take the most recent backup and will NOT replay the logs.
     
  6. moon-buddy

    moon-buddy ADSM.ORG Moderator

    Joined:
    Aug 24, 2005
    Messages:
    6,849
    Likes Received:
    363
    Occupation:
    Electronics Engineer, Security Professional
    Location:
    Somewhere in the US
    Doing restore db todate=11/09/2017 totime=06:00:00 and should work
     
  7. marclant

    marclant ADSM.ORG Moderator

    Joined:
    Jun 16, 2006
    Messages:
    2,606
    Likes Received:
    370
    Occupation:
    Accelerated Value Specialist for Spectrum Protect
    Location:
    Canada
    Assuming your DB backup started before 6AM. I'd put the time as now just to make sure you get the latest, and not the one prior. It will take the most recent backup that occurred before the date/time you provide.
     
  8. moon-buddy

    moon-buddy ADSM.ORG Moderator

    Joined:
    Aug 24, 2005
    Messages:
    6,849
    Likes Received:
    363
    Occupation:
    Electronics Engineer, Security Professional
    Location:
    Somewhere in the US
    All good now - I know what went wrong.

    I never use PIT but I do delete the TSM DB and clear the LOGS. I use a script to do this and there was a misstep on the script - it did not clear the LOGS.
     

Share This Page