I am running TSM for VE 7.1.4.1 on WIndows 2008 and it has been OK until
about 2 weeks ago. Since then every night the backup job (should be over
100 VM's) just kind of aborts without logging success or failure. The only
errors in the logs are these (which don't appear in any Google searches)
Hi Rick,
OC does not contain anything, everything is in the database of the connected
TSM server, so you can just have a second OC that connects to your DR server
using a properties file for this, see this technote :
http://www-01.ibm.com/support/docview.wss?uid=swg21983376
--
Best regards /
On a datamover node, run:
dsmc -asnode=XXX
q vm YYY -inactive
where XXX is the "datacenter node" that is used to record the VME data
and YYY is the VM node in question.
You can add -detail to the query for more verbose output.
David
-Original Message-
From: ADSM: Dist Stor Manager [mai
Looking to see if anyone has found a good way to run a report on a specific VM
on its backup history.
In other words, I would like to show a server owner when their VM was backed up
and basic information about its success or failure.
Thanks
Eric
We went through this and found the startup script has the ulimit commands
in it and were set too low. Also, did you check /etc/security/limits.conf
https://www.ibm.com/support/knowledgecenter/SSATMW_7.1.0/com.ibm.itsm.srv.install.doc/t_srv_startsrv_set_access_ulimit-linux.html
On Wed, Jun 1, 201
Some additional analysis: a cat /proc//limits indeed shows a Max open
files 4096... I don't know why, since both the root user as the instance user
have the proper settings:
Root:
# ulimit -Hn
65536
# ulimit -Sn
65536
Instance user:
$ ulimit -Hn
65536
$ ulimit -Sn
65536
Kind regards,
Eric van Loo
Hello,
You must increase the limit for the tsm user.
To check:
ps -ef|grep dsmserv
cat /proc//limits
Regards,
Philippe
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Loon,
EJ van (ITOPT3) - KLM
Sent: mercredi 1 juin 2016 12:53
To: ADSM-L@V
Hi guys!
I'm setting up a 7.1.5 server on Linux. I followed all specs and I have raised
the hard and soft limits for open files to the recommended value of 65536 for
both the instance user as root. However, I keep on receiving the following
message:
ANR3619W The user limit for open files is belo
