• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.

  • Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)

    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

Restore data with SESSIONINITiation=serveronly option set

combato

ADSM.ORG Member
#1
Hi Pro's

I have checked if I shall start to use the SESSIONINITiation=serveronly option for some nodes located in our DMZ.
The only way I have found how to restore data is to create a schedule with the "action=restore". I believe this is not a very flexible way to do a restore due I can't find how to use pitd and pitt if I restore within a schedule.

-Is there any better and more granular way to do restores?
-Is it possible to use pitt and pitd?

/C
 

combato

ADSM.ORG Member
#4
OK, sound good! I have to try that.
Thanks!

/C
Forgot to ask...:

-Are you able to "browse" the node data before you restore and check which versions that exist in the backup?
-Are you able to relocate the data to another dir when restoring?

/C
 

marclant

ADSM.ORG Moderator
#5
-Are you able to "browse" the node data before you restore and check which versions that exist in the backup?
Kind of, but you need a 3rd machine that is on the same side of the firewall as the Spectrum Protect Server. Start the client from a Windows Command Prompt:
cd "c:\program files\tivoli\tsm\baclient"
dsm -virtualnodename={dmz_node}
Note that you will need to know the password for that node. You will be able to click on Restore on that machine and browse the files. I guess you could do the restore on that machine and then manually copy the files over to the original machine.

-Are you able to relocate the data to another dir when restoring?
I don't believe so. When you restore from the command line, you pass the source and destination, but there's no option for that, it's just based on the position in the command.
 

combato

ADSM.ORG Member
#6
Kind of, but you need a 3rd machine that is on the same side of the firewall as the Spectrum Protect Server. Start the client from a Windows Command Prompt:
cd "c:\program files\tivoli\tsm\baclient"
dsm -virtualnodename={dmz_node}
Note that you will need to know the password for that node. You will be able to click on Restore on that machine and browse the files. I guess you could do the restore on that machine and then manually copy the files over to the original machine.


I don't believe so. When you restore from the command line, you pass the source and destination, but there's no option for that, it's just based on the position in the command.
Ok, thanks! Maybe this kind of config isn't so bad after all. First I thought that SESSIONINITiation=serveronly was difficult to use in daily restores but your answers gave me new hope! Thanks!
 

combato

ADSM.ORG Member
#7
Have now tried to setup a node with sessioninition=serveronly (upd node nodename SESSIONINITiation=serveronly HLA=192.168.0.25 LLA=1500)

I then added these options in dsm.sys file:

sessioninitiation serveronly
schedmode prompted
tcpclientaddress 192.168.0.25
tcpclientport 1500 (or does this port have to be something else than the same as TCPPort)?

Is this correct done, or do I need to configure anything else for the communication to work?
And, how the "h_ll" do I start a scheduled backup? I thought that I could use a client schedule but I don't get that to work.

/C
 

marclant

ADSM.ORG Moderator
#8
tcpclientport 1500 (or does this port have to be something else than the same as TCPPort)?
Something different, default is 1501, you can use anything, as long as the firewall ports are opened.

You need to update the LLA on the node to match the tcpclientport.

Is this correct done, or do I need to configure anything else for the communication to work?
Did you store the client password on the client? You'd use DSMC SET PASSWORD for that.

Once you fix the LLA, TCPClientport and set the password, you should be good to go. Define a schedule as normal, and associate the node to that schedule.
 

combato

ADSM.ORG Member
#9
Something different, default is 1501, you can use anything, as long as the firewall ports are opened.

You need to update the LLA on the node to match the tcpclientport.


Did you store the client password on the client? You'd use DSMC SET PASSWORD for that.

Once you fix the LLA, TCPClientport and set the password, you should be good to go. Define a schedule as normal, and associate the node to that schedule.
Unfortunately I don't get this to work. Could not set password on the node:

[[email protected]]# dsmc set password

IBM Tivoli Storage Manager
Command Line Backup-Archive Client Interface
Client Version 7, Release 1, Level 6.3
Client date/time: 11/24/2017 06:41:37
(c) Copyright by IBM Corporation and other(s) 1990, 2016. All Rights Reserved.

Please enter password for node "node1":
Please enter a new password:
Enter new password for verification:
ANS5844E Unable to update password

And I can see in actlog that the inititation starts but get I communiacation problems:
2017-11-24 11:31:22 ANR8213W Session open with 192.168.0.25 timed out.
2017-11-24 11:31:22 ANR2716E Schedule prompter was not able to contact client
node1 using type 1 (192.168.0.25 1501).
2017-11-24 11:32:13 ANR8213W Session open with 192.168.0.25 timed out

dsm.sys on client "node1":

servername tsmsrv1
COMMMethod TCPip
TCPPort 1500
TCPServeraddress tsmsrv1.domain.company.com
nodename node1
schedmode prompted
tcpclientaddress 192.168.0.25
tcpclientport 1501
sessioninitiation serveronly
PASSWORDACC GENERATE

q node node1 on tsmsrv1:

Protect: TSMSRV1>q node node1 f=d

Node Name: node1
Platform: (?)
Client OS Level: (?)
Client Version: (?)
Application Version: Version 0, release 0, level 0.0
Policy Domain Name: standard-01
Last Access Date/Time: 2017-10-04 15:04:48
Days Since Last Access: 51
Password Set Date/Time: 2017-10-27 08:59:20
Days Since Password Set: 28
Invalid Sign-on Count: 0
Locked?: No
Contact: IT dep
Compression: Client
Archive Delete Allowed?: Yes
Backup Delete Allowed?: No
Registration Date/Time: 2017-10-04 15:04:48
Registering Administrator: admin
Last Communication Method Used:
Bytes Received Last Session: 0
Bytes Sent Last Session: 0
Duration of Last Session: 0.00
Pct. Idle Wait Last Session: 0.00
Pct. Comm. Wait Last Session: 0.00
Pct. Media Wait Last Session: 0.00
Optionset:
URL:
Node Type: Client
Password Expiration Period: 0 Day(s)
Keep Mount Point?: No
Maximum Mount Points Allowed: 1
Auto Filespace Rename : No
Validate Protocol: No
TCP/IP Name:
TCP/IP Address:
Globally Unique ID:
Transaction Group Max: 0
Data Write Path: ANY
Data Read Path: ANY
Session Initiation: ServerOnly
High-level Address: 192.168.0.25
Low-level Address: 1501
Collocation Group Name:
Proxynode Target:
Proxynode Agent:
Node Groups:
Email Address:
Deduplication: ClientOrServer
Users allowed to back up: All
Role:
Role Override: UseReported
Processor Vendor:
Processor Brand:
Processor Type:
Processor Model:
Processor Count:
Hypervisor:
API Application:
Scan Error:
MAC Address:
Replication State: None
Replication Mode: None
Backup Replication Rule: DEFAULT
Archive Replication Rule: DEFAULT
Space Management Replication Rule: DEFAULT
Replication Primary Server:
Last Replicated to Server:
Client OS Name:
Client Processor Architecture:
Client Products Installed:
Client Target Version: (?)
Authentication: Local
SSL Required: Default
Session Security: Transitional
Transport Method: (?)
Split Large Objects: Yes
At-risk type: Default interval
At-risk interval:
Utility URL:
Replication Recovery of Damaged Files: Yes
Decommissioned:
Decommissioned Date:

Protect: TSMSRV1>

/C
 

combato

ADSM.ORG Member
#11
You need to specify the password and use « -validate=no ». You’re just storing the password locally, you can’t login to confirm it.
Same error:


[[email protected] ~]# dsmc set password -validate=no

IBM Tivoli Storage Manager

Command Line Backup-Archive Client Interface

Client Version 7, Release 1, Level 6.3

Client date/time: 12/01/2017 07:38:25

(c) Copyright by IBM Corporation and other(s) 1990, 2016. All Rights Reserved.


Please enter password for node "NODE1":

Please enter a new password:

Enter new password for verification:

ANS5844E Unable to update password.
 

marclant

ADSM.ORG Moderator
#12
I got it to work with passwordaccess generate, but it's not pretty.

  1. I started the scheduler in the foreground: "dsmc sched".
  2. Then on the server, I defined a client action to backup just one file: define clientaction NODE action=incremental object=/smit.log (pick any single small file, doesn't matter)
  3. Go back on the client and wait for the server to contact the scheduler, it can take up to 5 minutes. When prompted for the password, enter it.
  4. After the backup is complete stop the scheduler and restart from step 1 to validate that the password is stored.
If everything works with the test, you can stop the scheduler and restart it in the background.


Alternatively, you could use "passwordaccess prompt" in dsm.sys. And do one of the following:

store the password in clear text in dsm.sys:
password current_password

Or specify the password in the command that starts the scheduler:
dsmc sched -password=current_password
 

combato

ADSM.ORG Member
#13
Great, this worked! Followed step 1-4 and now the node knows it passwd.

I have really tried to look everywhere at IBMs knowledge base but I have not found a single page that describes how to setup this kind of backup (step by step).

Very good that you exists! Thanks!
 

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 9 16.4%
  • Keep using TSM for Spectrum Protect.

    Votes: 32 58.2%
  • Let's be formal and just say Spectrum Protect

    Votes: 9 16.4%
  • Other (please comement)

    Votes: 5 9.1%

Forum statistics

Threads
31,150
Messages
132,626
Members
21,324
Latest member
h3llb0y
Top