TSM Client V7.1.6.5

2017-10-11 Thread Saravanan Palanisamy
Hello TSM Giants 

Is there any issues with Windows TSM Client 7.1.6.5 ? Especially on system 
state restore using WinPE CD v3.1? 

One of my client server ( windows physical server 2008. ) is down for past 4 
days and IBM had shared almost 2 efix but still issues keeps on coming one 
another. 

C drive restore  seems to be okay but system state never get completed 

I am really scared of v7.1.6.5 because more than 3000 windows severs are 
running with this version. 

Please let me know if any known issues related to systemstate if anyone 
encounter in v7.1.6.5

One of IBM security patch APAR previously forced us to upgrade both Windows and 
LInix to v7.1.6.5 but now it became night mare for me. 

Just would like to share my pain here. 


Regards 
Sarav
+65 9856 8665

Scalability problems with expiration?

2017-10-11 Thread Hans Christian Riksheim
I have noticed that expiration suddenly takes a lot more time. The first
million objects are expired/deleted very quickly but it slows down to an
almost hang with the last 10%.

The DB has reached 2 TB and server is 7.1.3.100. Any performance
enhancements in later levels?

Hans Chr.


Re: TSM Client V7.1.6.5

2017-10-11 Thread Zoltan Forray
There is this page with "Client known problems and limitation"


On Wed, Oct 11, 2017 at 5:42 AM, Saravanan Palanisamy <
evergreen.sa...@gmail.com> wrote:

> Hello TSM Giants
>
> Is there any issues with Windows TSM Client 7.1.6.5 ? Especially on system
> state restore using WinPE CD v3.1?
>
> One of my client server ( windows physical server 2008. ) is down for past
> 4 days and IBM had shared almost 2 efix but still issues keeps on coming
> one another.
>
> C drive restore  seems to be okay but system state never get completed
>
> I am really scared of v7.1.6.5 because more than 3000 windows severs are
> running with this version.
>
> Please let me know if any known issues related to systemstate if anyone
> encounter in v7.1.6.5
>
> One of IBM security patch APAR previously forced us to upgrade both
> Windows and LInix to v7.1.6.5 but now it became night mare for me.
>
> Just would like to share my pain here.
>
>
> Regards
> Sarav
> +65 9856 8665




--
*Zoltan Forray*
Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator
Xymon Monitor Administrator
VMware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
www.ucc.vcu.edu
zfor...@vcu.edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://phishing.vcu.edu/


Re: Scalability problems with expiration?

2017-10-11 Thread Zoltan Forray
We hit the problem at 6.3.6 per this document
 which says:

*After upgrading the server to 6.3.6.000 (or higher)  and 7.1.3 (or higher)
expiration might "hang" on a node while expiring backup data only.
 Expiration is not actually hung it is still processing but very slowly due
to a non-optimized*
*SQL/Select.   A change to this SQL/Select occurred between 6.3.5.0 and
6.3.6.0.   This code change was implemented in servers 6.3.6.0+ and 7.1.3.0
to 7.1.7.   There have been no reported problems at 7.1.3 or above.*

On Wed, Oct 11, 2017 at 8:35 AM, Hans Christian Riksheim 
wrote:

> I have noticed that expiration suddenly takes a lot more time. The first
> million objects are expired/deleted very quickly but it slows down to an
> almost hang with the last 10%.
>
> The DB has reached 2 TB and server is 7.1.3.100. Any performance
> enhancements in later levels?
>
> Hans Chr.
>



--
*Zoltan Forray*
Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator
Xymon Monitor Administrator
VMware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
www.ucc.vcu.edu
zfor...@vcu.edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://phishing.vcu.edu/


Re: TSM Client V7.1.6.5

2017-10-11 Thread Andrew Raibeck
I think some of those items are a little dated. For example, I do not
recall the history behind this one:

Windows 2008 must be restored using Windows PE 2.0. Windows 7 and Windows
2008 R2 require Windows PE 3.0 for ASR restore.

but Windows PE 3.1 is the minum version that should be used for Windows
Server 2008.

Here is a parent link to articles covering backup and recovery of Windows:

https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Storage%20Manager/page/Best%20practices%20for%20Tivoli%20Storage%20Manager%20backup-archive%20client

The above URL includes links to these individual articles:

* Best Practices for Recovering Windows Server 2008, Windows Server 2008
R2, Windows 7, and Windows Vista
* Best Practices for Recovering Windows Server 2012 and Windows 8
* Best Practices for Recovering Windows Server 2012 R2 and Windows 8.1
* Guidelines for Backup and Recovery of Microsoft Windows Server 2016 and
Microsoft Windows 10
* Best Practices for Backing Up Microsoft Windows

These are (mostly) up to date, with the last two being most recent.

Best regards,

Andy



Andrew Raibeck | IBM Spectrum Protect Level 3 | stor...@us.ibm.com

IBM Tivoli Storage Manager links:
Product support:
https://www.ibm.com/support/entry/portal/product/tivoli/tivoli_storage_manager

Online documentation:
http://www.ibm.com/support/knowledgecenter/SSGSG7/landing/welcome_ssgsg7.html

Product Wiki:
https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%20Storage%20Manager

"ADSM: Dist Stor Manager"  wrote on 2017-10-11
08:37:35:

> From: Zoltan Forray 
> To: ADSM-L@VM.MARIST.EDU
> Date: 2017-10-11 08:38
> Subject: Re: TSM Client V7.1.6.5
> Sent by: "ADSM: Dist Stor Manager" 
>
> There is this page with "Client known problems and limitation"
>


>
> On Wed, Oct 11, 2017 at 5:42 AM, Saravanan Palanisamy <
> evergreen.sa...@gmail.com> wrote:
>
> > Hello TSM Giants
> >
> > Is there any issues with Windows TSM Client 7.1.6.5 ? Especially on
system
> > state restore using WinPE CD v3.1?
> >
> > One of my client server ( windows physical server 2008. ) is down for
past
> > 4 days and IBM had shared almost 2 efix but still issues keeps on
coming
> > one another.
> >
> > C drive restore  seems to be okay but system state never get completed
> >
> > I am really scared of v7.1.6.5 because more than 3000 windows severs
are
> > running with this version.
> >
> > Please let me know if any known issues related to systemstate if anyone
> > encounter in v7.1.6.5
> >
> > One of IBM security patch APAR previously forced us to upgrade both
> > Windows and LInix to v7.1.6.5 but now it became night mare for me.
> >
> > Just would like to share my pain here.
> >
> >
> > Regards
> > Sarav
> > +65 9856 8665
>
>
>
>
> --
> *Zoltan Forray*
> Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator
> Xymon Monitor Administrator
> VMware Administrator
> Virginia Commonwealth University
> UCC/Office of Technology Services
> www.ucc.vcu.edu
> zfor...@vcu.edu - 804-828-4807
> Don't be a phishing victim - VCU and other reputable organizations will
> never use email to request that you reply with your password, social
> security number or confidential personal information. For more details
> visit https://urldefense.proofpoint.com/v2/url?
> u=http-3A__phishing.vcu.edu_&d=DwIBaQ&c=jf_iaSHvJObTbx-
> siA1ZOg&r=Ij6DLy1l7wDpCbTfcDkLC_KknvhyGdCy_RnAGnhV37I&m=X7_WFArF-
> foq5omhTVXYj0V-nHyt70eTuo7e1GxIFz8&s=ZaaI2XSS2yegPbhN5LIRaB-
> zoW8tSZhSvdQOKpW2TRI&e=
>


Re: Scalability problems with expiration?

2017-10-11 Thread Hans Christian Riksheim
Thanks Zoltan. Time for an upgrade then.

Hans Chr.

On Wed, Oct 11, 2017 at 2:46 PM, Zoltan Forray  wrote:

> We hit the problem at 6.3.6 per this document
>  which says:
>
> *After upgrading the server to 6.3.6.000 (or higher)  and 7.1.3 (or higher)
> expiration might "hang" on a node while expiring backup data only.
>  Expiration is not actually hung it is still processing but very slowly due
> to a non-optimized*
> *SQL/Select.   A change to this SQL/Select occurred between 6.3.5.0 and
> 6.3.6.0.   This code change was implemented in servers 6.3.6.0+ and 7.1.3.0
> to 7.1.7.   There have been no reported problems at 7.1.3 or above.*
>
> On Wed, Oct 11, 2017 at 8:35 AM, Hans Christian Riksheim <
> bull...@gmail.com>
> wrote:
>
> > I have noticed that expiration suddenly takes a lot more time. The first
> > million objects are expired/deleted very quickly but it slows down to an
> > almost hang with the last 10%.
> >
> > The DB has reached 2 TB and server is 7.1.3.100. Any performance
> > enhancements in later levels?
> >
> > Hans Chr.
> >
>
>
>
> --
> *Zoltan Forray*
> Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator
> Xymon Monitor Administrator
> VMware Administrator
> Virginia Commonwealth University
> UCC/Office of Technology Services
> www.ucc.vcu.edu
> zfor...@vcu.edu - 804-828-4807
> Don't be a phishing victim - VCU and other reputable organizations will
> never use email to request that you reply with your password, social
> security number or confidential personal information. For more details
> visit http://phishing.vcu.edu/
>


Re: Magic Decoder Ring needed

2017-10-11 Thread Skylar Thompson
 Content preview:  I'm not aware of a fix for the problem (it's with Dell PERC
H810s) but the problem manifested itself in lots and lots of media errors
on a physical device, visible when you export the controller log. The 
symptoms
for TSM included both CRC errors in the pool and also sporadically awful
   I/O throughput. [...]

 Content analysis details:   (0.7 points, 5.0 required)

  pts rule name  description
  -- --
  0.7 SPF_NEUTRALSPF: sender does not match SPF record (neutral)
 -0.0 RP_MATCHES_RCVDEnvelope sender domain matches handover relay 
domain
X-Barracuda-Connect: mx.gs.washington.edu[128.208.8.134]
X-Barracuda-Start-Time: 1507728824
X-Barracuda-Encrypted: ECDHE-RSA-AES256-GCM-SHA384
X-Barracuda-URL: https://148.100.49.28:443/cgi-mod/mark.cgi
X-Barracuda-Scan-Msg-Size: 5262
X-Virus-Scanned: by bsmtpd at marist.edu
X-Barracuda-BRTS-Status: 1
X-Barracuda-Spam-Score: 0.00
X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=3.5 
QUARANTINE_LEVEL=1000.0 KILL_LEVEL=5.5 tests=
X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.43799
Rule breakdown below
 pts rule name  description
 -- 
--

I'm not aware of a fix for the problem (it's with Dell PERC H810s) but the
problem manifested itself in lots and lots of media errors on a physical
device, visible when you export the controller log. The symptoms for TSM
included both CRC errors in the pool and also sporadically awful I/O
throughput.

The controller logs identified the slot with the media errors, and
replacing the drive made all the above problems go away. Of course the real
solution is going to be retiring these soon-to-be-EOSL'd devices, and I've
finally got a budget to do it...

I'm not actually aware of a fix for the problem, though I didn't spend a
lot of time looking for one given that we'll be getting rid of the
equipment in a few weeks. It could very well be an interaction between the
RAID HBA and physical disk firmware. Unfortunately the system has a mix of
disk vendors since Dell isn't consistent about which vendor they ship for
replacements, but the drive I identified was a Fujitsu MBD2300RC.

On Tue, Oct 10, 2017 at 02:18:01PM -0400, Zoltan Forray wrote:
> Thank you for the info.  We have started running AUDIT's but with 30TB+ in
> this disk stgpool, it will take a while.  I am very interested in
> additional details on the RAID firmware issue you mentioned - any specifics
> would be very helpful.  AFAIK, we are up-to-date on all Dell firmware (we
> patch fairly regularly).
>
> Within the past 9-months, this server has had 3-diskpool volumes (all part
> of RAID-5 arrays) suddenly become "bad", requiring full restores, with no
> explanation since there was no sign of hardware problems. While I did open
> a PMR with IBM, by the time they looked at my last failure, they said there
> was nothing they could do to analyze the problem and to call them back the
> next time it happens.
>
> On Tue, Oct 10, 2017 at 2:04 PM, Skylar Thompson 
> wrote:
>
> > Hi Zoltan,
> >
> > We ran into this recently, and it was caused by a firmware bug in a RAID
> > adapter that caused it not to fail and obviously-failing disk in our disk
> > spool. We followed the procedure here:
> >
> > https://www.ibm.com/support/knowledgecenter/en/SSGSG7_7.1.
> > 6/tshoot/r_pdg_1330_1331_msg.html
> >
> > It did take a few AUDIT VOLUME-MOVE DATA cycles to find everything but now
> > it's happy. In a few cases, the file shown by SHOW INVO was obviously
> > detritus, so we deleted it client-side with DELETE BACKUP instead of an
> > audit, because it takes a long time to audit our disk volumes.
> >
> > On Tue, Oct 10, 2017 at 01:56:47PM -0400, Zoltan Forray wrote:
> > > Recently we started seeing these errors on one of our servers:
> > >
> > > 10/10/2017 13:35:51  ANR1330E The server has detected possible corruption
> > > in
> > >   an object that is being restored or moved. The
> > actual
> > >
> > >   values for the incorrect frame are: magic 53454652
> > > hdr
> > >   version2 hdr length32 sequence number
> > >  22610
> > >   data length3FFB0 server ID0 segment ID
> > >
> > >   2720223190 crc0. (SESSION: 39218, PROCESS:
> > > 171)
> > > 10/10/2017 13:35:51  ANR1331E Invalid frame detected.  Expected magic
> > > 53454652
> > >
> > > The Process ID points to a Backup Stgpool process (the only thing
> > running),
> > > not anything being "moved or restored".  There are also a bunch of
> > sessions
> > > running/stuck/hung but that is a different problem.
> > >
> > > Any idea on how to determine what is causing this?  We've seen the error
> > > quite a few times within the past few days.
> > >
> > > -

Re: TSM Client V7.1.6.5

2017-10-11 Thread Saravanan Palanisamy
Thanks Andy and Zoltan 


Regards 
Sarav 
+65 9857 8665


> On 11 Oct 2017, at 8:56 PM, Andrew Raibeck  wrote:
> 
> I think some of those items are a little dated. For example, I do not
> recall the history behind this one:
> 
> Windows 2008 must be restored using Windows PE 2.0. Windows 7 and Windows
> 2008 R2 require Windows PE 3.0 for ASR restore.
> 
> but Windows PE 3.1 is the minum version that should be used for Windows
> Server 2008.
> 
> Here is a parent link to articles covering backup and recovery of Windows:
> 
> https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Storage%20Manager/page/Best%20practices%20for%20Tivoli%20Storage%20Manager%20backup-archive%20client
> 
> The above URL includes links to these individual articles:
> 
> * Best Practices for Recovering Windows Server 2008, Windows Server 2008
> R2, Windows 7, and Windows Vista
> * Best Practices for Recovering Windows Server 2012 and Windows 8
> * Best Practices for Recovering Windows Server 2012 R2 and Windows 8.1
> * Guidelines for Backup and Recovery of Microsoft Windows Server 2016 and
> Microsoft Windows 10
> * Best Practices for Backing Up Microsoft Windows
> 
> These are (mostly) up to date, with the last two being most recent.
> 
> Best regards,
> 
> Andy
> 
> 
> 
> Andrew Raibeck | IBM Spectrum Protect Level 3 | stor...@us.ibm.com
> 
> IBM Tivoli Storage Manager links:
> Product support:
> https://www.ibm.com/support/entry/portal/product/tivoli/tivoli_storage_manager
> 
> Online documentation:
> http://www.ibm.com/support/knowledgecenter/SSGSG7/landing/welcome_ssgsg7.html
> 
> Product Wiki:
> https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%20Storage%20Manager
> 
> "ADSM: Dist Stor Manager"  wrote on 2017-10-11
> 08:37:35:
> 
>> From: Zoltan Forray 
>> To: ADSM-L@VM.MARIST.EDU
>> Date: 2017-10-11 08:38
>> Subject: Re: TSM Client V7.1.6.5
>> Sent by: "ADSM: Dist Stor Manager" 
>> 
>> There is this page with "Client known problems and limitation"
>> 
> 
> 
>> 
>> On Wed, Oct 11, 2017 at 5:42 AM, Saravanan Palanisamy <
>> evergreen.sa...@gmail.com> wrote:
>> 
>>> Hello TSM Giants
>>> 
>>> Is there any issues with Windows TSM Client 7.1.6.5 ? Especially on
> system
>>> state restore using WinPE CD v3.1?
>>> 
>>> One of my client server ( windows physical server 2008. ) is down for
> past
>>> 4 days and IBM had shared almost 2 efix but still issues keeps on
> coming
>>> one another.
>>> 
>>> C drive restore  seems to be okay but system state never get completed
>>> 
>>> I am really scared of v7.1.6.5 because more than 3000 windows severs
> are
>>> running with this version.
>>> 
>>> Please let me know if any known issues related to systemstate if anyone
>>> encounter in v7.1.6.5
>>> 
>>> One of IBM security patch APAR previously forced us to upgrade both
>>> Windows and LInix to v7.1.6.5 but now it became night mare for me.
>>> 
>>> Just would like to share my pain here.
>>> 
>>> 
>>> Regards
>>> Sarav
>>> +65 9856 8665
>> 
>> 
>> 
>> 
>> --
>> *Zoltan Forray*
>> Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator
>> Xymon Monitor Administrator
>> VMware Administrator
>> Virginia Commonwealth University
>> UCC/Office of Technology Services
>> www.ucc.vcu.edu
>> zfor...@vcu.edu - 804-828-4807
>> Don't be a phishing victim - VCU and other reputable organizations will
>> never use email to request that you reply with your password, social
>> security number or confidential personal information. For more details
>> visit https://urldefense.proofpoint.com/v2/url?
>> u=http-3A__phishing.vcu.edu_&d=DwIBaQ&c=jf_iaSHvJObTbx-
>> siA1ZOg&r=Ij6DLy1l7wDpCbTfcDkLC_KknvhyGdCy_RnAGnhV37I&m=X7_WFArF-
>> foq5omhTVXYj0V-nHyt70eTuo7e1GxIFz8&s=ZaaI2XSS2yegPbhN5LIRaB-
>> zoW8tSZhSvdQOKpW2TRI&e=
>>