Re: TSM db backup delayed or hung for more than few hours

2023-05-30 Thread Saravanan Palanisamy
Hi Skylar

We use disk for db backup and it will finish within 30 minutes once db
backup started at db2 level for 2 tb database.

There is no errors or warnings reported during db backup and only concern
it takes more than 30 min to see db backup message in db2diag log though
tsm side backup db command issued.

We just need to ensure db backup get complete two times to clear all the
logs.

Sometime we noticed there was no db backup message in db2 diag log and db
backup process hang with 0 bytes even after  12 hours.

There is more stress for us to monitor db backup process very closely as it
may get hung anytime.

Our data fully resides on all flash disk ( db , active , archive and
directory container )





On Tue, 30 May 2023 at 11:29 PM, Skylar Thompson  wrote:

> What's the device type for the DB backup? We'll see this when SAN discovery
> hasn't caught up with new device paths after a replacement. The telltale
> will be ANR8975I messages on the library manager and ANR8974I messages on
> the clients.
>
> As others noted, though, it can also be an API package problem. It might be
> fruitful looking in the activity log around the time backups start, along
> with the db2diag.log and tsmdbmgr.log files.
>
> On Mon, May 29, 2023 at 05:16:50AM +0800, Saravanan Palanisamy wrote:
> > !---|
> >   This Message Is From an Untrusted Sender
> >   You have not previously corresponded with this sender.
> >   See https://itconnect.uw.edu/email-tags for additional
> >   information.Please contact the UW-IT Service Center,
> >   h...@uw.edu 206.221.5000, for assistance.
> > |---!
> >
> > V8.1.18
> >
> > We have noticed tsm backup started at tsm level but  didn???t issue any
> message to db2 and tsm level db backup appears hung
> >
> > db2 list utilities show details - No process
> > db2diag.log - didn???t see any message like ( Starting an online db
> backup )
> >
> > Tried to restart tsm server to clear db2 hung process but no luck and db
> backup again hung.
> >
> > Main issue here :
> >
> > When we start tsm db backup it???s not able start and archive log became
> full. Tried to increase archive log few times.
> >
> > We tried almost 3 times ( we waited more than 1 hour ) but no luck.
> >
> > we always run db backup to clear archive log so that server will up and
> running.
> >
> > Same issue observed on last week in different server and today one more
> server.
> >
> > We have raised PMR to check this issue.
> >
> > Did anyone face this issue in v8.1.18 ?
> >
> > We have never seen this issue earlier but noticed after upgrade to
> v8.1.18
> >
> >
> > Usually when we issue db backup command it will immediately start and we
> will see tsmdbmgr sessions in tsm server.  It looks like strange issue and
> causing outage for production jobs.
> >
> >
> > Regards
> > Sarav
> > +65 9857 8665
>
> --
> -- Skylar Thompson (skyl...@u.washington.edu)
> -- Genome Sciences Department (UW Medicine), System Administrator
> -- Foege Building S046, (206)-685-7354
> -- Pronouns: He/Him/His
>
--
Thanks & Regards,
Saravanan
Mobile: +65-8228 4384


Re: TSM db backup delayed or hung for more than few hours

2023-05-30 Thread Saravanan Palanisamy
Hi Vikas 

We are using latest tsm client (8.1.17.2) and server version (8.1.18) 

Regards 
Sarav 
+65 9857 8665


> On 30 May 2023, at 2:27 AM, Vikas Arora  wrote:
> 
> Hi Sarav,
> 
> May  I ask which tsm client version (dsmadmc) you are using? Can you please
> try to update it with the latest version and then re-try? I had a similar
> experience a few days ago and that helped!
> 
> thanks
> 
> 
> 
> Grüße
> Vikas Arora
> 
> *e Mail* : vikar...@gmail.com
> 
> 
>> On Mon, 29 May 2023 at 13:38, Saravanan Palanisamy <
>> evergreen.sa...@gmail.com> wrote:
>> 
>> Today it took more than 90 min to initiate db backup at db2 level where as
>> admin schedule issues backup db command 90 min before and backup got
>> completed. We will monitor closely.
>> 
>> Regards
>> Sarav
>> +65 9857 8665
>> 
>> 
>>>> On 29 May 2023, at 3:29 PM, David L.A. De Leeuw  wrote:
>>> 
>>> Hi Sarav
>>> 
>>> We had a similar case, just yesterday. I noticed the daily full database
>> backup schedule was missed a number of days.
>>> Then I found that five days ago the daily full backup just hanged.
>>> Canceling the process hung as well on "pending".
>>> 
>>> I contacted our system administrator and she reported that db2 got
>> "stuck".
>>> She rebooted the server, and the next backup ran as usual.
>>> If this repeats, we will open a PMR as well.
>>> 
>>> Our version: 8.1.17
>>> 
>>> Best wishes
>>> 
>>> David de Leeuw
>>> 
>>> -Original Message-
>>> From: ADSM: Dist Stor Manager  On Behalf Of
>> Saravanan Palanisamy
>>> Sent: Monday, May 29, 2023 12:17 AM
>>> To: ADSM-L@VM.MARIST.EDU
>>> Subject: [ADSM-L] TSM db backup delayed or hung for more than few hours
>>> 
>>> V8.1.18
>>> 
>>> We have noticed tsm backup started at tsm level but  didn’t issue any
>> message to db2 and tsm level db backup appears hung
>>> 
>>> db2 list utilities show details - No process db2diag.log - didn’t see
>> any message like ( Starting an online db backup )
>>> 
>>> Tried to restart tsm server to clear db2 hung process but no luck and db
>> backup again hung.
>>> 
>>> Main issue here :
>>> 
>>> When we start tsm db backup it’s not able start and archive log became
>> full. Tried to increase archive log few times.
>>> 
>>> We tried almost 3 times ( we waited more than 1 hour ) but no luck.
>>> 
>>> we always run db backup to clear archive log so that server will up and
>> running.
>>> 
>>> Same issue observed on last week in different server and today one more
>> server.
>>> 
>>> We have raised PMR to check this issue.
>>> 
>>> Did anyone face this issue in v8.1.18 ?
>>> 
>>> We have never seen this issue earlier but noticed after upgrade to
>> v8.1.18
>>> 
>>> 
>>> Usually when we issue db backup command it will immediately start and we
>> will see tsmdbmgr sessions in tsm server.  It looks like strange issue and
>> causing outage for production jobs.
>>> 
>>> 
>>> Regards
>>> Sarav
>>> +65 9857 8665
>> 


Re: TSM db backup delayed or hung for more than few hours

2023-05-29 Thread Saravanan Palanisamy
Today it took more than 90 min to initiate db backup at db2 level where as 
admin schedule issues backup db command 90 min before and backup got completed. 
We will monitor closely. 

Regards 
Sarav 
+65 9857 8665


> On 29 May 2023, at 3:29 PM, David L.A. De Leeuw  wrote:
> 
> Hi Sarav
> 
> We had a similar case, just yesterday. I noticed the daily full database 
> backup schedule was missed a number of days. 
> Then I found that five days ago the daily full backup just hanged.
> Canceling the process hung as well on "pending".
> 
> I contacted our system administrator and she reported that db2 got "stuck".
> She rebooted the server, and the next backup ran as usual.
> If this repeats, we will open a PMR as well. 
> 
> Our version: 8.1.17
> 
> Best wishes
> 
> David de Leeuw
> 
> -----Original Message-
> From: ADSM: Dist Stor Manager  On Behalf Of Saravanan 
> Palanisamy
> Sent: Monday, May 29, 2023 12:17 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: [ADSM-L] TSM db backup delayed or hung for more than few hours
> 
> V8.1.18 
> 
> We have noticed tsm backup started at tsm level but  didn’t issue any message 
> to db2 and tsm level db backup appears hung 
> 
> db2 list utilities show details - No process db2diag.log - didn’t see any 
> message like ( Starting an online db backup ) 
> 
> Tried to restart tsm server to clear db2 hung process but no luck and db 
> backup again hung. 
> 
> Main issue here : 
> 
> When we start tsm db backup it’s not able start and archive log became full. 
> Tried to increase archive log few times. 
> 
> We tried almost 3 times ( we waited more than 1 hour ) but no luck. 
> 
> we always run db backup to clear archive log so that server will up and 
> running. 
> 
> Same issue observed on last week in different server and today one more 
> server. 
> 
> We have raised PMR to check this issue. 
> 
> Did anyone face this issue in v8.1.18 ? 
> 
> We have never seen this issue earlier but noticed after upgrade to v8.1.18 
> 
> 
> Usually when we issue db backup command it will immediately start and we will 
> see tsmdbmgr sessions in tsm server.  It looks like strange issue and causing 
> outage for production jobs. 
> 
> 
> Regards
> Sarav 
> +65 9857 8665


TSM db backup delayed or hung for more than few hours

2023-05-28 Thread Saravanan Palanisamy
V8.1.18 

We have noticed tsm backup started at tsm level but  didn’t issue any message 
to db2 and tsm level db backup appears hung 

db2 list utilities show details - No process 
db2diag.log - didn’t see any message like ( Starting an online db backup ) 

Tried to restart tsm server to clear db2 hung process but no luck and db backup 
again hung. 

Main issue here : 

When we start tsm db backup it’s not able start and archive log became full. 
Tried to increase archive log few times. 

We tried almost 3 times ( we waited more than 1 hour ) but no luck. 

we always run db backup to clear archive log so that server will up and 
running. 

Same issue observed on last week in different server and today one more server. 

We have raised PMR to check this issue. 

Did anyone face this issue in v8.1.18 ? 

We have never seen this issue earlier but noticed after upgrade to v8.1.18 


Usually when we issue db backup command it will immediately start and we will 
see tsmdbmgr sessions in tsm server.  It looks like strange issue and causing 
outage for production jobs. 


Regards 
Sarav 
+65 9857 8665


Re: Hot add Transport for restore virtual machine

2023-04-25 Thread Saravanan Palanisamy
Thanks Richard. Backup was working well in hotadd as VADP host resides on
same data store.

I just doubt whether hotadd transport supported for restore vm though we
place VADP host in the same data store .

We tried to enable SAN policy as Online in VADP host  but it didn’t help.

Just wondering anyone used hotadd transport for restore because when we
restore using hot add it didn’t progress anything.



On Tue, 25 Apr 2023 at 8:35 PM, Elberse, R.H.L. (Richard) <
r.elbe...@rocmn.nl> wrote:

> Hi Sarav,
>
> The datastore must be available to the host on which the datamover is
> restoring the vm.
> DSM.OPT should not have a setting that rules out using hotadd.
> There may be other options that may cause the hotadd restore not being
> used.
>
> Richard
>
> -Oorspronkelijk bericht-
> Van: ADSM: Dist Stor Manager  Namens Saravanan
> Palanisamy
> Verzonden: dinsdag 25 april 2023 13:55
> Aan: ADSM-L@VM.MARIST.EDU
> Onderwerp: [ADSM-L] Hot add Transport for restore virtual machine
>
> Hi Everyone
>
> Is there any additional settings required to enable hotadd transport while
> restoring vm using TSM for VE ( VADP host is virtual machine )?
>
> Regards
> Sarav
> +65 9857 8665
> 
>  .. .. .. .. Disclaimer .. .. .. ..
> VERTROUWELIJK: De informatie in dit bericht is vertrouwelijk. Het is
> daarom niet toegestaan dat u deze informatie openbaar maakt,
> vermenigvuldigt of verspreidt, tenzij de verzender aangeeft dat dit wel is
> toegestaan. Als dit e-mailbericht niet voor u bestemd is, vragen wij u
> vriendelijk maar dringend om het bericht en kopieën daarvan te vernietigen.
> Dit bericht is gecontroleerd op bekende virussen.
>
-- 
Thanks & Regards,
Saravanan
Mobile: +65-8228 4384


Hot add Transport for restore virtual machine

2023-04-25 Thread Saravanan Palanisamy
Hi Everyone 

Is there any additional settings required to enable hotadd transport while 
restoring vm using TSM for VE ( VADP host is virtual machine )? 

Regards 
Sarav 
+65 9857 8665


Re: OSSM Integration with SP 8.1.16

2023-01-06 Thread Saravanan Palanisamy
Thanks for your response. We have imported the certificate with SAN name then 
it worked. Looks like SAN name is mandatory for OSSM integration. 


> On 5 Jan 2023, at 11:21 PM, Lee Miller  wrote:
> 
> Hello,
> I am working on a similar problem in a Level 2 assist (related to a sale 
> force ticket)  I have opened your  question and the L2 assist in the OSSM 
> development slack channel.   Once I get a response I will update both.   
> 
> -Original Message-
> From: ADSM: Dist Stor Manager  On Behalf Of Saravanan 
> Palanisamy
> Sent: Thursday, January 5, 2023 9:02 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: [EXTERNAL] [ADSM-L] OSSM Integration with SP 8.1.16
> 
> Hello Everyone,
> 
> 
> 
> I have tried to configure Open Snap Store Manager to integrate with SPP.
> When I tried to use default TSM self signed cert then I can do the OSSM 
> config without any issue. However when I try to use CA signed cert then OSSM 
> services are not able to communicate with IBM Spectrum Protect Server and 
> OSSM services are not coming up. Does anyone successful configure OSSM with 
> CA signed cert ? Even I tried to copy the CA cert files to 
> /home/tsminst1/ossm/.secret/CAs/mycacert.cert.
> 
> 
> Have tried with other TSM servers where we have imported CA cert but 
> encounter same issue but when I remove the cert and do the config then it 
> works.
> 
> If anyone come across this issue and give some light on it then would really 
> appreciate it.
> 
> 
> 
> Regards,
> Sarav
> --
> Thanks & Regards,
> Saravanan
> Mobile: +65-8228 4384


OSSM Integration with SP 8.1.16

2023-01-05 Thread Saravanan Palanisamy
Hello Everyone,



I have tried to configure Open Snap Store Manager to integrate with SPP.
When I tried to use default TSM self signed cert then I can do the OSSM
config without any issue. However when I try to use CA signed cert then
OSSM services are not able to communicate with IBM Spectrum Protect Server
and OSSM services are not coming up. Does anyone successful configure OSSM
with CA signed cert ? Even I tried to copy the CA cert files to
/home/tsminst1/ossm/.secret/CAs/mycacert.cert.


Have tried with other TSM servers where we have imported CA cert but
encounter same issue but when I remove the cert and do the config then it
works.

If anyone come across this issue and give some light on it then would
really appreciate it.



Regards,
Sarav
--
Thanks & Regards,
Saravanan
Mobile: +65-8228 4384


Re: Command Routing Failed => Does this affect Server2Server communication, too?

2022-11-04 Thread Saravanan Palanisamy
No issues for server to server communication.


Regards
Sarav

On Fri, 4 Nov 2022 at 4:25 PM, Bjørn Nachtwey 
wrote:

> Hi,
>
> does this new feature also affect the server2server communication, e.g.
> for LibMan <=> LibClient?
>
> If so, which server should I upgrade first? Or should I set all
> passwords to UPCASE?
>
> Thanks & best
> Bjørn
>
> On 02.11.22 17:22, Michael Prix wrote:
> > Hello Sarav,
> >
> >  not strange, but works as designed (by IBM).
> > Introduced with 8.1.16 is case sensitivity for the passwords.
> > So, if you send a command from a server with codelevel lower than
> > 8.1.16, the password is sent in UPPERCASE.
> > If you send a command from an 8.1.6 Server, the password is send as
> > you entered it (PaSSwoRD)
> >
> > A server below 8.1.16 checkes the submitted password against his
> > stored one, which is UPEERCASE.
> > A server at 8.1.16 checkes against his stored one, which might be MiXeD.
> >
> > This all is valid only for security=strict, old behaviour is
> > accomplished by security=transitional
> >
> > So, if you have a mixed environment, change the passwords to
> > UPPERCASE. or update all servers instantly.
> >  --
> >
> > Michael Prix
> >
> > On 11/2/22 10:11, Saravanan Palanisamy wrote:
> >> Dear Team
> >>
> >> We have upgraded tsm server to v8.1.16 and all our automation scripts
> >> start to fail due to invalid password thorough correct password is
> >> provided.
> >>
> >> If you update sessionsecurity=transition then if we try same
> >> credential then it works but command routing will not work.
> >>
> >> If you update sessionsecurity=transition then command routing will
> >> work but if you try dsmadmc with correct password it will fail with
> >> invalid password and user id get locked
> >>
> >> Looks very strange.
> >>
> >> Regards
> >> Sarav
> >> +65 9857 8665
>
> --
>
> --
> Bjørn Nachtwey
>
> Arbeitsgruppe "IT-Infrastruktur"
> E-Mail:bjoern.nacht...@gwdg.de
>
> --
> Gesellschaft fuer wissenschaftliche D
> <https://www.google.com/maps/search/llschaft+fuer+wissenschaftliche+D?entry=gmail&source=g>atenverarbeitung
> mbH Goettingen (GWDG)
> Burckhardtweg 4, 37077 Goettingen, URL:https://gwdg.de
>
> Support: Tel.: +49 551 39-3, URL:https://gwdg.de/support
> Sekretariat: Tel.: +49 551 39-30001, E-Mail:g...@gwdg.de
>
> Geschaeftsfuehrer: Prof. Dr. Ramin Yahyapour
> Aufsichtsratsvorsitzender: Prof. Dr. Norbert Lossau
> Sitz der Gesellschaft: Goettingen
> Registergericht: Goettingen, Handelsregister-Nr. B 598
>
> Zertifiziert nach ISO 9001
>
> --
>
> https://www.credly.com/badges/0c5c3c9f-097c-462b-b70e-3de524b72a25/public_url
>
> --
>
-- 
Thanks & Regards,
Saravanan
Mobile: +65-8228 4384


Re: Command Routing Failed

2022-11-02 Thread Saravanan Palanisamy
Hi Michael 

Yes it works perfect. All passwords are auto converted to CAPS after upgrade to 
v8.1.16. 
 
Thanks for your inputs. 

Regards 
Sarav 
+65 9857 8665


> On 3 Nov 2022, at 12:23 AM, Michael Prix  wrote:
> 
> Hello Sarav,
> 
>  not strange, but works as designed (by IBM).
> Introduced with 8.1.16 is case sensitivity for the passwords.
> So, if you send a command from a server with codelevel lower than 8.1.16, the 
> password is sent in UPPERCASE.
> If you send a command from an 8.1.6 Server, the password is send as you 
> entered it (PaSSwoRD)
> 
> A server below 8.1.16 checkes the submitted password against his stored one, 
> which is UPEERCASE.
> A server at 8.1.16 checkes against his stored one, which might be MiXeD.
> 
> This all is valid only for security=strict, old behaviour is accomplished by 
> security=transitional
> 
> So, if you have a mixed environment, change the passwords to UPPERCASE. or 
> update all servers instantly.
>  --
> 
> Michael Prix
> 
>> On 11/2/22 10:11, Saravanan Palanisamy wrote:
>> Dear Team
>> 
>> We have upgraded tsm server to v8.1.16 and all our automation scripts start 
>> to fail due to invalid password thorough correct password is provided.
>> 
>> If you update sessionsecurity=transition then if we try same credential then 
>> it works but command routing will not work.
>> 
>> If you update sessionsecurity=transition then command routing will work but 
>> if you try dsmadmc with correct password it will fail with invalid password 
>> and user id get locked
>> 
>> Looks very strange.
>> 
>> Regards
>> Sarav
>> +65 9857 8665


Command Routing Failed

2022-11-02 Thread Saravanan Palanisamy
Dear Team

We have upgraded tsm server to v8.1.16 and all our automation scripts start to 
fail due to invalid password thorough correct password is provided. 

If you update sessionsecurity=transition then if we try same credential then it 
works but command routing will not work. 

If you update sessionsecurity=transition then command routing will work but if 
you try dsmadmc with correct password it will fail with invalid password and 
user id get locked 

Looks very strange. 

Regards 
Sarav 
+65 9857 8665


Re: NFS Storage used as directory container storage pool

2022-08-02 Thread Saravanan Palanisamy
Hi Zoltan

Thanks for your inputs. We have no plan to use as File device class and may
be not good idea to use either directory container stg pool. Currently we
are using S3 as target for long term storage and looking for some other
alternatives as we have stored more than 8 PB and don’t want to be single
archival storage.

Regards
Sarav

On Tue, 2 Aug 2022 at 9:15 PM, Zoltan Forray  wrote:

> We have had lots of issues using NFS (ISILON) storage as standard FILE
> pools and would never try to use them for containers.  Currently we only
> use them as overflow/next stgpools (vs active, ingest of backups) since we
> simply don't have sufficient, proper storage to handle backups.  IBM's
> official statement about NFS:
>
> https://www.ibm.com/support/pages/ibm-spectrum-protect-server-support-nfs
>
> On Tue, Aug 2, 2022 at 9:05 AM Marc Lanteigne 
> wrote:
>
> > Hi Sarav,
> >
> > For Directory Container Pools, NFS mounted filesystems are not
> > recommended. The nature of the file I/O of directory container pools
> > doesn't work well with NFS mounted filesystems.
> >
> > If you plan to use Directory Container pools, I highly recommend that you
> > follow the Blueprints, otherwise you may not be happy with the
> performance.
> > https://www.ibm.com/support/pages/ibm-spectrum-protect-blueprints
> >
> > -
> > Thanks,
> > Marc...
> >
> > Marc Lanteigne
> > Spectrum Protect Specialist AVP / SRT
> > IBM Systems, Spectrum Protect / Plus
> > +1-506-460-9074
> > marclantei...@ca.ibm.com
> > Office Hours:  Monday to Friday, 7:00 to 15:30 Eastern
> >
> > IBM
> >
> > -Original Message-
> > From: ADSM: Dist Stor Manager  On Behalf Of
> > Saravanan Palanisamy
> > Sent: Tuesday, August 2, 2022 09:45 AM
> > To: ADSM-L@VM.MARIST.EDU
> > Subject: [EXTERNAL] [ADSM-L] NFS Storage used as directory container
> > storage pool
> >
> > Did anyone try using NFS file system as Directory container storage pool
> ?
> >
> > is there any drawback to use such options?
> >
> > we have enough bandwidth 25G to support NFS mount points and its
> dedicated
> > for backup servers.
> >
> >
> >
> > Regards
> > Sarav
> > --
> > Thanks & Regards,
> > Saravanan
> > Mobile: +65-8228 4384
> >
>
>
> --
> *Zoltan Forray*
> Enterprise Backup Administrator
> VMware Systems Administrator
> Enterprise Compute & Storage Platforms Team
> VCU Infrastructure 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/
> <https://adminmicro2.questionpro.com>
>
-- 
Thanks & Regards,
Saravanan
Mobile: +65-8228 4384


Re: NFS Storage used as directory container storage pool

2022-08-02 Thread Saravanan Palanisamy
Hi Marc

Thanks for the quick response. We do use block storage as per ibm blue
print for backup workloads and looking for NFS storage as directory
container for long term retention. Thanks for the suggestions and
appreciate your response.


Regards
Sarav

On Tue, 2 Aug 2022 at 9:04 PM, Marc Lanteigne 
wrote:

> Hi Sarav,
>
> For Directory Container Pools, NFS mounted filesystems are not
> recommended. The nature of the file I/O of directory container pools
> doesn't work well with NFS mounted filesystems.
>
> If you plan to use Directory Container pools, I highly recommend that you
> follow the Blueprints, otherwise you may not be happy with the performance.
> https://www.ibm.com/support/pages/ibm-spectrum-protect-blueprints
>
> -
> Thanks,
> Marc...
>
> Marc Lanteigne
> Spectrum Protect Specialist AVP / SRT
> IBM Systems, Spectrum Protect / Plus
> +1-506-460-9074
> marclantei...@ca.ibm.com
> Office Hours:  Monday to Friday, 7:00 to 15:30 Eastern
>
> IBM
>
> -Original Message-
> From: ADSM: Dist Stor Manager  On Behalf Of
> Saravanan Palanisamy
> Sent: Tuesday, August 2, 2022 09:45 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: [EXTERNAL] [ADSM-L] NFS Storage used as directory container
> storage pool
>
> Did anyone try using NFS file system as Directory container storage pool ?
>
> is there any drawback to use such options?
>
> we have enough bandwidth 25G to support NFS mount points and its dedicated
> for backup servers.
>
>
>
> Regards
> Sarav
> --
> Thanks & Regards,
> Saravanan
> Mobile: +65-8228 4384
>
--
Thanks & Regards,
Saravanan
Mobile: +65-8228 4384


NFS Storage used as directory container storage pool

2022-08-02 Thread Saravanan Palanisamy
Did anyone try using NFS file system as Directory container storage pool ?

is there any drawback to use such options?

we have enough bandwidth 25G to support NFS mount points and its dedicated
for backup servers.



Regards
Sarav
--
Thanks & Regards,
Saravanan
Mobile: +65-8228 4384


Re: 8.1.15 Linux client update causing failures

2022-07-12 Thread Saravanan Palanisamy
So far We don’t see any issues in windows. All scheduled backups are 
successful. 

Regards 
Sarav 
+65 9857 8665


> On 13 Jul 2022, at 9:00 AM, Tom Alverson  wrote:
> 
> Is the windows client safe for this version?
> 
> 
>> On Tue, Jul 12, 2022, 7:06 PM Saravanan Palanisamy <
>> evergreen.sa...@gmail.com> wrote:
>> 
>> Hi Zoltan
>> 
>> Yes we have also faced same issue and IBM support confirmed they will open
>> new APAR. We have reverted all clients v8.1.14 to address the issue.
>> 
>> Regards
>> Sarav
>> +65 9857 8665
>> 
>> 
>>>> On 13 Jul 2022, at 2:31 AM, Del Hoobler  wrote:
>>> 
>>> Hi Zoltan,
>>> 
>>> IBM knows about this ... and it's being actively worked.
>>> 
>>> I am sure it will be mitigated soon.
>>> 
>>> Feel free to open a fresh IBM Support case so you can be quickly
>> notified once it is fixed.
>>> 
>>> 
>>> Del
>>> 
>>> 
>>> From: ADSM: Dist Stor Manager  on behalf of
>> Zoltan Forray 
>>> Sent: Tuesday, July 12, 2022 1:56 PM
>>> To: ADSM-L@VM.MARIST.EDU 
>>> Subject: [EXTERNAL] 8.1.15 Linux client update causing failures
>>> 
>>> We started rolling out the 8.1.15 Linux client via apogee and many
>> clients
>>> are failing with:
>>> 
>>> *** Error in `dsmc': double free or corruption (!prev):
>> 0x02baf970
>>> ***
>>> 
>>> The only matching Google hit goes back to a V7 client issue - long fixed.
>>> 
>>> At first I thought it might be related to a Linux flavor (we run Rocky8,
>>> CentOS 7.1/8, RHEL 7/8) but I don't see a pattern.  All of these servers
>>> are upgrading from 8.1.14 and downleveling the client to 8.1.14 fixes
>> this.
>>> 
>>> Anyone else seeing this?
>>> 
>>> FWIW, I could swear that during one of my many Google searches I saw a
>>> reference to 8.1.15.2 (eFix?) but now I can't find it again.
>>> --
>>> *Zoltan Forray*
>>> Enterprise Backup Administrator
>>> VMware Systems Administrator
>>> Enterprise Compute & Storage Platforms Team
>>> VCU Infrastructure Services
>>> www.ucc.vcu.edu<http://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/
>>> <https://adminmicro2.questionpro.com >
>> 


Re: 8.1.15 Linux client update causing failures

2022-07-12 Thread Saravanan Palanisamy
Hi Zoltan 

Yes we have also faced same issue and IBM support confirmed they will open new 
APAR. We have reverted all clients v8.1.14 to address the issue. 

Regards 
Sarav 
+65 9857 8665


> On 13 Jul 2022, at 2:31 AM, Del Hoobler  wrote:
> 
> Hi Zoltan,
> 
> IBM knows about this ... and it's being actively worked.
> 
> I am sure it will be mitigated soon.
> 
> Feel free to open a fresh IBM Support case so you can be quickly notified 
> once it is fixed.
> 
> 
> Del
> 
> 
> From: ADSM: Dist Stor Manager  on behalf of Zoltan 
> Forray 
> Sent: Tuesday, July 12, 2022 1:56 PM
> To: ADSM-L@VM.MARIST.EDU 
> Subject: [EXTERNAL] 8.1.15 Linux client update causing failures
> 
> We started rolling out the 8.1.15 Linux client via apogee and many clients
> are failing with:
> 
> *** Error in `dsmc': double free or corruption (!prev): 0x02baf970
> ***
> 
> The only matching Google hit goes back to a V7 client issue - long fixed.
> 
> At first I thought it might be related to a Linux flavor (we run Rocky8,
> CentOS 7.1/8, RHEL 7/8) but I don't see a pattern.  All of these servers
> are upgrading from 8.1.14 and downleveling the client to 8.1.14 fixes this.
> 
> Anyone else seeing this?
> 
> FWIW, I could swear that during one of my many Google searches I saw a
> reference to 8.1.15.2 (eFix?) but now I can't find it again.
> --
> *Zoltan Forray*
> Enterprise Backup Administrator
> VMware Systems Administrator
> Enterprise Compute & Storage Platforms Team
> VCU Infrastructure 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: BA Client 8.1.13.3 documentation

2022-01-14 Thread Saravanan Palanisamy
Yes v8.1.13.3 shipping log4j 2.17.1. Got it clarified with PMR support. 

Regards 
Sarav 
+65 9857 8665


> On 14 Jan 2022, at 9:24 PM, Zoltan Forray  wrote:
> 
> I noticed 8.1.13.3 of Windows/Linux BA clients are available for download
> but every documentation link goes to "thin air"? Even from the PSIRT page
> you get "Sorry, no posts matched your criteria."
> 
> I am suspecting log4j 2.17.1 but can not verify.
> 
> Anyone find any details/documentation?
> --
> *Zoltan Forray*
> Backup Systems 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: client deployment with SP 8.1.12

2021-06-28 Thread Saravanan Palanisamy
Hi Stefan


Do you have an existing ibm_deploy_client_import ? You can try to rename all 
old nodes and try import. I had same issue but it worked after removed previous 
imported nodes for IBM deployment. 

Regards 
Sarav 
+65 9857 8665


> On 28 Jun 2021, at 3:29 PM, Tsm Tsm  wrote:
> 
> Hello,
> 
> the spectrum protect server has no internet connection so
> i imported .exp files from local directory but the OC Button for planning
> software deployment still is greyed out.
> 
> 
> i did
> 
> download .exp File from IBM (ftp)
> download Updatemanager File from IBM
> 
> import node * filedata=archive mergefilespaces=yes
> devclass=ibm_deploy_client_import volumenames=e:\tsm1\deploy
> \8.1.12.0-TIV-TSMBAC-WinX64.EXP
> import node * filedata=archive mergefilespaces=yes
> devclass=ibm_deploy_client_import volumenames=e:\tsm1\deploy
> \Updatemanager-WinX64.EXP
> 
> 
> what is missing to start with deployment?
> 
> thank you for your comments.
> 
> 
> with best regards
> Stefan Savoric


Re: Decom Node

2021-05-10 Thread Saravanan Palanisamy
Thanks Frederick. Appreciate your response. 

Regards 
Sarav 
+65 9857 8665


> On 10 May 2021, at 8:47 PM, De Kezel, Frederik 
>  wrote:
> 
> Maybe first recommission those nodes?
> Then you will be able to replicate them.
> And then decommission again when replication is finished.
> 
> 
> Use the RECOMMISSION commands to recommission a decommissioned
> client node or virtual machine (VM).
> 
> *  3.52.1 RECOMMISSION NODE (Recommission a decommissioned
>   application or system client node)
> 
> *  3.52.2 RECOMMISSION VM (Recommission a virtual machine)
> 
> 
> Rgds,
> 
> -Original Message-
> From: ADSM: Dist Stor Manager  On Behalf Of Saravanan 
> Palanisamy
> Sent: maandag 10 mei 2021 14:29
> To: ADSM-L@VM.MARIST.EDU
> Subject: [ADSM-L] Decom Node
> 
> **This Message originated from a Non-ArcelorMittal source**
> 
> 
> Dear team
> 
> We have decommissioned few nodes but would like to replicate those nodes to 
> different server. Since replication not supported for decom node we would 
> like to check how to replicate those nodes.
> 
> 
> Regards
> Sarav
> +65 9857 8665


Re: Decom Node

2021-05-10 Thread Saravanan Palanisamy
Please ignore this message. Just found recommissioned node command. 



Regards 
Sarav 
+65 9857 8665


> On 10 May 2021, at 8:28 PM, Saravanan Palanisamy  
> wrote:
> 
> 
> Dear team 
> 
> We have decommissioned few nodes but would like to replicate those nodes to 
> different server. Since replication not supported for decom node we would 
> like to check how to replicate those nodes. 
> 
> 
> Regards 
> Sarav 
> +65 9857 8665
> 


Decom Node

2021-05-10 Thread Saravanan Palanisamy
Dear team 

We have decommissioned few nodes but would like to replicate those nodes to 
different server. Since replication not supported for decom node we would like 
to check how to replicate those nodes. 


Regards 
Sarav 
+65 9857 8665


Re: [E] Re: [ADSM-L] TSM alternatives

2021-04-28 Thread Saravanan Palanisamy
Hi Del 

I could see oracle SPARC support API v8.1 but BA client not released for v8.1. 
What is the purpose of releasing API support for v8.1 without BA client ?

Means no BA client backup supported but still support TDP for oracle ? TDP also 
require BA client to install. 

Please advise if you have any background. 
 

Regards 
Sarav 
+65 9857 8665


> On 26 Apr 2021, at 7:03 PM, Del Hoobler  wrote:
> 
> Hi Michael,
> 
> You are correct. At the end of this year, the Backup/Archive client for 
> Solaris SPARC will not be supported. As you mention, you can buy extended 
> support, but it will only be for "Usage or Known Defect" issues, not for 
> new currency updates or defects.
> 
> I made the previous comment because I wanted other people reading this to 
> make sure they understood it was only Solaris SPARC that this applied to, 
> not Solaris x86_64.
> 
> Thank you.
> 
> 
> Del
> 
> 
> 
> 
> "ADSM: Dist Stor Manager"  wrote on 04/26/2021 
> 06:25:34 AM:
> 
>> From: "Stahlberg, Michael" 
>> To: ADSM-L@VM.MARIST.EDU
>> Date: 04/26/2021 06:26 AM
>> Subject: [EXTERNAL] Re: [E] Re: [ADSM-L] TSM alternatives
>> Sent by: "ADSM: Dist Stor Manager" 
>> 
>> Hi Del,
>> 
>> We use Solaris Sparc, and it was clear for me that this is fully 
> supported
>> until the end of this year, but what happens if a newer OS release will
>> come next year and the client will not work anymore, please.
>> 
>> I got the information from the support team that we can buy extended
>> support, but this means more in case of a failure they will try to help,
>> but there will be no development on this client anymore
>> 
>> It might be wrong, but with this statement, I cannot backup production 
> data
>> anymore.
>> 
>> thanks
>> 
>> regards
>> 
>> > u=http-3A__www.verizon.com&d=DwIFaQ&c=jf_iaSHvJObTbx-
>> 
> siA1ZOg&r=0hq2JX5c3TEZNriHEs7Zf7HrkY2fNtONOrEOM8Txvk8&m=xbwRG2jwrVEOfJbwF7XUE6ogWFzsumbFCZ0SPJpEH-
>> Y&s=FuEfe5SeT2yOWzFApUbjJivuOqOY9QCLmW-e8ZqJV2g&e= >
>> 
>> *Michael Stahlberg*
>> Engineer IV Consultant - Network Eng & Ops
>> Server & Services Management International -* Global Operations | 
> Verizon*
>> Wireline Network
>> Tel: +49 231 972 0 | Cell: +49 231 972 0
>> 
>> 
>> 
>> 
>>> Am Fr., 23. Apr. 2021 um 17:23 Uhr schrieb Del Hoobler 
>> :
>> 
>>> Thanks Michael.
>>> 
>>> Just to be sure it's clear to all.
>>> 
>>> IBM Spectrum Protect still supports Solaris for x86_64. It's the 
> Solaris
>>> SPARC platform that is API only support:
>>> 
>>> 
>>> INVALID URI REMOVED
>> 
> u=https-3A__www.ibm.com_support_pages_node_84861-23Solaris-2520x86-5F64&d=DwIFAw&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=-0-
>> r_o4RMF4NYke7vSCYCBjM7xJlyEdabThqplN58jk&m=YtQc_i2zHXvNtA0l-
>> 
> FkYOG8VOWKBcrHneIIlI92WUq0&s=qAQ_ww-bqRak-N9RxpC9z9bBpXBz00LoQNil0T465iE&e=
>>> 
>>> Some other notes:
>>> - You can still use the Spectrum Protect V7 Solaris SPARC B/A client 
> until
>>> the end of this year with full support... and longer with extended
>>> support.
>>> - You can also mount the Solaris SPARC filesystems and back it up from 
> a
>>> proxy server.
>>> 
>>> 
>>> Del
>>> 
>>> 
>>> 
>>> 
>>> "ADSM: Dist Stor Manager"  wrote on 04/23/2021
>>> 09:32:19 AM:
>>> 
 From: "Stahlberg, Michael" 
 To: ADSM-L@VM.MARIST.EDU
 Date: 04/23/2021 09:33 AM
 Subject: [EXTERNAL] TSM alternatives
 Sent by: "ADSM: Dist Stor Manager" 
 
 HI all,
 
 unfortunately IBM decided to stop the support for Solaris Clients. 
> This
>>> is
 a pain for us and we have decided to move to a different product. 
> I'm
 checking for alternatives and would like to know if somebody has the
>>> same
 issue and/or has already decided to move to a different product. I'm 
> not
 happy about this, but our main clients are all Solaris Clients
>>> still..
 
 regards
 
 >>> u=http-3A__www.verizon.com&d=DwIFaQ&c=jf_iaSHvJObTbx-
 
>>> 
>>> 
>> 
> siA1ZOg&r=0hq2JX5c3TEZNriHEs7Zf7HrkY2fNtONOrEOM8Txvk8&m=6A_Oax46rHV7OFpRD535E9xEkLeChb5REQjB-
 ceSTLc&s=HAwiCutcUMO04kWTHODK3NR79sbupV9T8nQJfPSIaZE&e= >
 
 *Michael Stahlberg*
 Engineer IV Consultant - Network Eng & Ops
 Server & Services Management International -* Global Operations |
>>> Verizon*
 Wireline Network
 Tel: +49 231 972 0 | Cell: +49 231 972 0
 
 
> ==
 
 Verizon Deutschland GmbH - Sebrathweg 20, 44149 Dortmund, Germany -
 Amtsgericht Dortmund, HRB 14952 - Geschäftsführer: Detlef Eppig -
 Vorsitzender des Aufsichtsrats: Francesco de Maio
 
>>> 
>> 


Re: Replication Hung after upgrade to v8.1.10

2020-12-15 Thread Saravanan Palanisamy
Hi Sasa

Delete batch was set to Low priority and it has helped us to address the issue. 
Still working with dev team for apar details. 

Setopt repldeletepriority Low 

Regards 
Sarav 
+65 9857 8665


> On 8 Dec 2020, at 5:46 AM, Sasa Drnjevic  wrote:
> 
> Hi Sarav.
> 
> Thanks for the info.
> 
> Could you please just send some link or more info on the setting or a fix 
> version if it is a fix.
> 
> Tnx - Regards,
> 
> --
> Sasa Drnjevic
> www.srce.unizg.hr/en/
> 
> 
> 
> 
>> On 7.12.2020. 20:02, Saravanan Palanisamy wrote:
>> Team
>> Just would like to update status for replication issue reported earlier. IBM 
>> development team managed to find the root cause and provided solution for 
>> intermittent replication hung. We have applied those recommended settings 
>> and didn’t see any hung for the past 3 weeks.
>> Regards
>> Sarav
>> +65 9857 8665
>>>> On 24 Sep 2020, at 12:12 AM, Sasa Drnjevic  wrote:
>>> 
>>> Hi Sarav and all,
>>> 
>>> I forgot to inform you earlier, but I have solved the problem with HUNG
>>> or more precisely EXTREMELY slow replication.
>>> 
>>> Linux nodees were ALL replicating as before the upgrade, without any
>>> problems.
>>> 
>>> The main culprit was Windows Systemstate. Ordinary NTFS filespaces
>>> replicated fine.
>>> 
>>> But when I have replicated all of the windows nodes manually one-by-one
>>> (not as a nodegroup) the second and all successive runs were normal as
>>> before. So, now everything runs fine as before the upgrade to
>>> v8.1.10.100 (on RHEL 7.8).
>>> 
>>> All windows would take much more to replicate when run for the first
>>> time after the upgrade, some of them took 8 hours instead of less than
>>> 10 minutes.
>>> 
>>> IBM support blamed all of it on canceled replication because they have
>>> found some msgs like:
>>> 
>>> ANR1650W The server detected partially replicated data
>>> from a previous replication operation. This might result
>>> in extended processing time for process 2 while the
>>> server is replicating node nodename...
>>> 
>>> 
>>> Yes, I have canceled some, but maybe only 5-6 windows nodes, but all of
>>> the 40+ windows nodes took ages to replicate for the first time after
>>> upgrade.
>>> 
>>> Most of the windows nodes used some readonly tapes (scanning only?) with
>>> data more than 2 months old which was surely replicated long time ago.
>>> 
>>> Some Linux nodes (out of 180+) were canceled too, but later replicated
>>> with normal throughput.
>>> 
>>> So, be careful :-)
>>> 
>>> Regards,
>>> 
>>> --
>>> Sasa Drnjevic
>>> www.srce.unizg.hr/en/
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>>> On 9.9.2020. 1:08, Saravanan Palanisamy wrote:
>>>> Hi Sasa
>>>> 
>>>> Thanks for the update. We are still waiting for updates from dev team.
>>>> 
>>>> Regards
>>>> Sarav
>>>> +65 9857 8665
>>>> 
>>>> 
>>>>>> On 9 Sep 2020, at 4:55 AM, Sasa Drnjevic  wrote:
>>>>> 
>>>>> On 2.9.2020. 1:30, Saravanan Palanisamy wrote:
>>>>>> Hi Eric
>>>>>> 
>>>>>> We have applied efix to address APAR IT33437 instead of patch 
>>>>>> v8.1.10.100 and we haven’t seen any server crash after >efix. However 
>>>>>> our intermittent replication issue case still in progress.
>>>>> 
>>>>> 
>>>>> Hi Sarav & all.
>>>>> 
>>>>> Last week I have upgraded my target server to v8.1.10.100, and node
>>>>> replication was going without any problems from source v8.1.1.000 to
>>>>> target v8.1.10.100. Both servers are RHEL 7.8.
>>>>> 
>>>>> So, this morning I took my chances and upgraded my source server to
>>>>> v8.1.10.100. The upgrade went fine.
>>>>> 
>>>>> But, replication hangs :-(
>>>>> 
>>>>> I have opened a case with IBM support and did a first step supplying
>>>>> some logs.
>>>>> 
>>>>> But, while trying to find out what is causing the replication to hang I
>>>>> did some 30 manual single node replication jobs and ALL of the Linux
>>>>&

Re: Replication Hung after upgrade to v8.1.10

2020-12-07 Thread Saravanan Palanisamy
Team

Just would like to update status for replication issue reported earlier. IBM 
development team managed to find the root cause and provided solution for 
intermittent replication hung. We have applied those recommended settings and 
didn’t see any hung for the past 3 weeks.


Regards 
Sarav 
+65 9857 8665


> On 24 Sep 2020, at 12:12 AM, Sasa Drnjevic  wrote:
> 
> Hi Sarav and all,
> 
> I forgot to inform you earlier, but I have solved the problem with HUNG
> or more precisely EXTREMELY slow replication.
> 
> Linux nodees were ALL replicating as before the upgrade, without any
> problems.
> 
> The main culprit was Windows Systemstate. Ordinary NTFS filespaces
> replicated fine.
> 
> But when I have replicated all of the windows nodes manually one-by-one
> (not as a nodegroup) the second and all successive runs were normal as
> before. So, now everything runs fine as before the upgrade to
> v8.1.10.100 (on RHEL 7.8).
> 
> All windows would take much more to replicate when run for the first
> time after the upgrade, some of them took 8 hours instead of less than
> 10 minutes.
> 
> IBM support blamed all of it on canceled replication because they have
> found some msgs like:
> 
> ANR1650W The server detected partially replicated data
> from a previous replication operation. This might result
> in extended processing time for process 2 while the
> server is replicating node nodename...
> 
> 
> Yes, I have canceled some, but maybe only 5-6 windows nodes, but all of
> the 40+ windows nodes took ages to replicate for the first time after
> upgrade.
> 
> Most of the windows nodes used some readonly tapes (scanning only?) with
> data more than 2 months old which was surely replicated long time ago.
> 
> Some Linux nodes (out of 180+) were canceled too, but later replicated
> with normal throughput.
> 
> So, be careful :-)
> 
> Regards,
> 
> --
> Sasa Drnjevic
> www.srce.unizg.hr/en/
> 
> 
> 
> 
> 
> 
> 
> 
>> On 9.9.2020. 1:08, Saravanan Palanisamy wrote:
>> Hi Sasa 
>> 
>> Thanks for the update. We are still waiting for updates from dev team. 
>> 
>> Regards 
>> Sarav 
>> +65 9857 8665
>> 
>> 
>>>> On 9 Sep 2020, at 4:55 AM, Sasa Drnjevic  wrote:
>>> 
>>> On 2.9.2020. 1:30, Saravanan Palanisamy wrote:
>>>> Hi Eric 
>>>> 
>>>> We have applied efix to address APAR IT33437 instead of patch v8.1.10.100 
>>>> and we haven’t seen any server crash after >efix. However our intermittent 
>>>> replication issue case still in progress. 
>>> 
>>> 
>>> Hi Sarav & all.
>>> 
>>> Last week I have upgraded my target server to v8.1.10.100, and node
>>> replication was going without any problems from source v8.1.1.000 to
>>> target v8.1.10.100. Both servers are RHEL 7.8.
>>> 
>>> So, this morning I took my chances and upgraded my source server to
>>> v8.1.10.100. The upgrade went fine.
>>> 
>>> But, replication hangs :-(
>>> 
>>> I have opened a case with IBM support and did a first step supplying
>>> some logs.
>>> 
>>> But, while trying to find out what is causing the replication to hang I
>>> did some 30 manual single node replication jobs and ALL of the Linux
>>> nodes replicated with SUCCESS.
>>> 
>>> I have node groups which are replicated with schedules, and of course
>>> some are mixed with Linux and Windows nodes.
>>> 
>>> So, when a windows node hangs it hangs the whole node group.
>>> 
>>> And it seems that the main culprit is the Windows Systemstate.
>>> 
>>> Would bet on that, and I mentioned that to IBM support.
>>> 
>>> We'll see tomorrow.
>>> 
>>> Hope it helps.
>>> 
>>> Rgds,
>>> 
>>> --
>>> Sasa Drnjevic
>>> www.srce.unizg.hr/en/
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>>> 
>>>> Regards 
>>>> Sarav 
>>>> +65 9857 8665
>>>> 
>>>> 
>>>>>> On 1 Sep 2020, at 10:38 PM, Loon, Eric van (ITOP NS) - KLM 
>>>>>>  wrote:
>>>>> 
>>>>> Hi Sarav,
>>>>> 
>>>>> On page https://www.ibm.com/support/pages/node/6212043#8110100 I do find 
>>>>> APAR IT33437 listed.
>>>>> 
>>>>> Kind regards,
>>>>> Eric van Loon
>>>>> Air France/KLM Storage &

Re: Replication Hung after upgrade to v8.1.10

2020-09-08 Thread Saravanan Palanisamy
Hi Sasa 

Thanks for the update. We are still waiting for updates from dev team. 

Regards 
Sarav 
+65 9857 8665


> On 9 Sep 2020, at 4:55 AM, Sasa Drnjevic  wrote:
> 
> On 2.9.2020. 1:30, Saravanan Palanisamy wrote:
>> Hi Eric 
>> 
>> We have applied efix to address APAR IT33437 instead of patch v8.1.10.100 
>> and we haven’t seen any server crash after >efix. However our intermittent 
>> replication issue case still in progress. 
> 
> 
> Hi Sarav & all.
> 
> Last week I have upgraded my target server to v8.1.10.100, and node
> replication was going without any problems from source v8.1.1.000 to
> target v8.1.10.100. Both servers are RHEL 7.8.
> 
> So, this morning I took my chances and upgraded my source server to
> v8.1.10.100. The upgrade went fine.
> 
> But, replication hangs :-(
> 
> I have opened a case with IBM support and did a first step supplying
> some logs.
> 
> But, while trying to find out what is causing the replication to hang I
> did some 30 manual single node replication jobs and ALL of the Linux
> nodes replicated with SUCCESS.
> 
> I have node groups which are replicated with schedules, and of course
> some are mixed with Linux and Windows nodes.
> 
> So, when a windows node hangs it hangs the whole node group.
> 
> And it seems that the main culprit is the Windows Systemstate.
> 
> Would bet on that, and I mentioned that to IBM support.
> 
> We'll see tomorrow.
> 
> Hope it helps.
> 
> Rgds,
> 
> --
> Sasa Drnjevic
> www.srce.unizg.hr/en/
> 
> 
> 
> 
> 
> 
> 
> 
> 
>> 
>> Regards 
>> Sarav 
>> +65 9857 8665
>> 
>> 
>>>> On 1 Sep 2020, at 10:38 PM, Loon, Eric van (ITOP NS) - KLM 
>>>>  wrote:
>>> 
>>> Hi Sarav,
>>> 
>>> On page https://www.ibm.com/support/pages/node/6212043#8110100 I do find 
>>> APAR IT33437 listed.
>>> 
>>> Kind regards,
>>> Eric van Loon
>>> Air France/KLM Storage & Backup
>>> 
>>> -Original Message-
>>> From: ADSM: Dist Stor Manager  On Behalf Of Saravanan 
>>> Palanisamy
>>> Sent: maandag 31 augustus 2020 23:10
>>> To: ADSM-L@VM.MARIST.EDU
>>> Subject: Re: Replication Hung after upgrade to v8.1.10
>>> 
>>> Hi Eric 
>>> 
>>> Thanks. I have gone through v8.1.10.100 APAR details but I don’t find my 
>>> issue here. I am still waiting for IBM on my case. 
>>> 
>>> Regards 
>>> Sarav 
>>> +65 9857 8665
>>> 
>>> 
>>>> On 31 Aug 2020, at 3:00 PM, Loon, Eric van (ITOP NS) - KLM 
>>>>  wrote:
>>>> 
>>>> Hi Sarav,
>>>> 
>>>> You probably noticed it already, but IBM released 8.1.10.100 containing a 
>>>> fix for your (and several other) issues.
>>>> 
>>>> Kind regards,
>>>> Eric van Loon
>>>> Air France/KLM Storage & Backup
>>>> 
>>>> -Original Message-
>>>> From: ADSM: Dist Stor Manager  On Behalf Of 
>>>> Saravanan Palanisamy
>>>> Sent: donderdag 20 augustus 2020 17:42
>>>> To: ADSM-L@VM.MARIST.EDU
>>>> Subject: Re: Replication Hung after upgrade to v8.1.10
>>>> 
>>>> IT33437
>>>> 
>>>> Regards 
>>>> Sarav 
>>>> +65 9857 8665
>>>> 
>>>> 
>>>>>> On 20 Aug 2020, at 11:05 PM, Loon, Eric van (ITOP NS) - KLM 
>>>>>>  wrote:
>>>>> 
>>>>> Hi Sarav,
>>>>> 
>>>>> You stated " There is also one more issue on v8.1.10 where server will 
>>>>> crash abruptly if you use directory container. It appears to be known 
>>>>> issue and we have got efix to address it". I find this very alarming, 
>>>>> because I'm about to start production on a new server running this level. 
>>>>> Do you have an APAR number?
>>>>> 
>>>>> Kind regards,
>>>>> Eric van Loon
>>>>> Air France/KLM Storage & Backup
>>>>> 
>>>>> 
>>>>> -Original Message-
>>>>> From: ADSM: Dist Stor Manager  On Behalf Of 
>>>>> Saravanan Palanisamy
>>>>> Sent: donderdag 20 augustus 2020 16:58
>>>>> To: ADSM-L@VM.MARIST.EDU
>>>>> Subject: Re: Replication Hung after upgrade to v8.1.10
>>>>> 
>>>>> Thanks Erwann for the update

Re: Replication Hung after upgrade to v8.1.10

2020-09-01 Thread Saravanan Palanisamy
Hi Eric 

We have applied efix to address APAR IT33437 instead of patch v8.1.10.100 and 
we haven’t seen any server crash after efix. However our intermittent 
replication issue case still in progress. 

Regards 
Sarav 
+65 9857 8665


> On 1 Sep 2020, at 10:38 PM, Loon, Eric van (ITOP NS) - KLM 
>  wrote:
> 
> Hi Sarav,
> 
> On page https://www.ibm.com/support/pages/node/6212043#8110100 I do find APAR 
> IT33437 listed.
> 
> Kind regards,
> Eric van Loon
> Air France/KLM Storage & Backup
> 
> -Original Message-
> From: ADSM: Dist Stor Manager  On Behalf Of Saravanan 
> Palanisamy
> Sent: maandag 31 augustus 2020 23:10
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: Replication Hung after upgrade to v8.1.10
> 
> Hi Eric 
> 
> Thanks. I have gone through v8.1.10.100 APAR details but I don’t find my 
> issue here. I am still waiting for IBM on my case. 
> 
> Regards 
> Sarav 
> +65 9857 8665
> 
> 
>> On 31 Aug 2020, at 3:00 PM, Loon, Eric van (ITOP NS) - KLM 
>>  wrote:
>> 
>> Hi Sarav,
>> 
>> You probably noticed it already, but IBM released 8.1.10.100 containing a 
>> fix for your (and several other) issues.
>> 
>> Kind regards,
>> Eric van Loon
>> Air France/KLM Storage & Backup
>> 
>> -Original Message-
>> From: ADSM: Dist Stor Manager  On Behalf Of Saravanan 
>> Palanisamy
>> Sent: donderdag 20 augustus 2020 17:42
>> To: ADSM-L@VM.MARIST.EDU
>> Subject: Re: Replication Hung after upgrade to v8.1.10
>> 
>> IT33437
>> 
>> Regards 
>> Sarav 
>> +65 9857 8665
>> 
>> 
>>>> On 20 Aug 2020, at 11:05 PM, Loon, Eric van (ITOP NS) - KLM 
>>>>  wrote:
>>> 
>>> Hi Sarav,
>>> 
>>> You stated " There is also one more issue on v8.1.10 where server will 
>>> crash abruptly if you use directory container. It appears to be known issue 
>>> and we have got efix to address it". I find this very alarming, because I'm 
>>> about to start production on a new server running this level. Do you have 
>>> an APAR number?
>>> 
>>> Kind regards,
>>> Eric van Loon
>>> Air France/KLM Storage & Backup
>>> 
>>> 
>>> -Original Message-
>>> From: ADSM: Dist Stor Manager  On Behalf Of Saravanan 
>>> Palanisamy
>>> Sent: donderdag 20 augustus 2020 16:58
>>> To: ADSM-L@VM.MARIST.EDU
>>> Subject: Re: Replication Hung after upgrade to v8.1.10
>>> 
>>> Thanks Erwann for the update. 
>>> 
>>> We are still facing intermittent hang and no progress on our case. If it’s 
>>> one server then we could say it’s environment issue but 3 different pair 
>>> and all are in different countries as well. We are holding upgrade for rest 
>>> of countries until find out root cause. 
>>> 
>>> There is also one more issue on v8.1.10 where server will crash abruptly if 
>>> you use directory container. It appears to be known issue and we have got 
>>> efix to address it. 
>>> 
>>> I will keep you posted if I hear any updates on my case. 
>>> 
>>> Regards 
>>> Sarav 
>>> +65 9857 8665
>>> 
>>> 
>>>>> On 20 Aug 2020, at 10:10 PM, Erwann SIMON  wrote:
>>>> 
>>>> Hello,
>>>> 
>>>> I've just upgraded some servers to that level and I do not encounter this 
>>>> king of issue (right now...).
>>>> 
>>>> -- 
>>>> Best regards / Cordialement / مع تحياتي
>>>> Erwann SIMON
>>>> 
>>>> - Mail original -
>>>> De: "Saravanan Palanisamy" 
>>>> À: ADSM-L@VM.MARIST.EDU
>>>> Envoyé: Mardi 21 Juillet 2020 00:37:41
>>>> Objet: [ADSM-L] Replication Hung after upgrade to v8.1.10
>>>> 
>>>> Dear Team
>>>> 
>>>> Is there anyone facing intermittent replication hung issue after upgrade 
>>>> to v8.1.10? 
>>>> 
>>>> We have upgraded TSM server from 8.1.9.300 to 8.1.10 and replication 
>>>> process is hung intermittently on all 3 servers. Just want to see whether 
>>>> anyone else impacted. 
>>>> 
>>>> Once restart TSM instance then replication works but again replication 
>>>> node process will get hung. But we don’t see any hung for protect stg and 
>>>> it works fine. 
>>>> 
>>>> We have raised case with IBM and working on it.
>>>>

Re: Replication Hung after upgrade to v8.1.10

2020-08-31 Thread Saravanan Palanisamy
Hi Eric 

Thanks. I have gone through v8.1.10.100 APAR details but I don’t find my issue 
here. I am still waiting for IBM on my case. 

Regards 
Sarav 
+65 9857 8665


> On 31 Aug 2020, at 3:00 PM, Loon, Eric van (ITOP NS) - KLM 
>  wrote:
> 
> Hi Sarav,
> 
> You probably noticed it already, but IBM released 8.1.10.100 containing a fix 
> for your (and several other) issues.
> 
> Kind regards,
> Eric van Loon
> Air France/KLM Storage & Backup
> 
> -Original Message-
> From: ADSM: Dist Stor Manager  On Behalf Of Saravanan 
> Palanisamy
> Sent: donderdag 20 augustus 2020 17:42
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: Replication Hung after upgrade to v8.1.10
> 
> IT33437
> 
> Regards 
> Sarav 
> +65 9857 8665
> 
> 
>> On 20 Aug 2020, at 11:05 PM, Loon, Eric van (ITOP NS) - KLM 
>>  wrote:
>> 
>> Hi Sarav,
>> 
>> You stated " There is also one more issue on v8.1.10 where server will crash 
>> abruptly if you use directory container. It appears to be known issue and we 
>> have got efix to address it". I find this very alarming, because I'm about 
>> to start production on a new server running this level. Do you have an APAR 
>> number?
>> 
>> Kind regards,
>> Eric van Loon
>> Air France/KLM Storage & Backup
>> 
>> 
>> -Original Message-
>> From: ADSM: Dist Stor Manager  On Behalf Of Saravanan 
>> Palanisamy
>> Sent: donderdag 20 augustus 2020 16:58
>> To: ADSM-L@VM.MARIST.EDU
>> Subject: Re: Replication Hung after upgrade to v8.1.10
>> 
>> Thanks Erwann for the update. 
>> 
>> We are still facing intermittent hang and no progress on our case. If it’s 
>> one server then we could say it’s environment issue but 3 different pair and 
>> all are in different countries as well. We are holding upgrade for rest of 
>> countries until find out root cause. 
>> 
>> There is also one more issue on v8.1.10 where server will crash abruptly if 
>> you use directory container. It appears to be known issue and we have got 
>> efix to address it. 
>> 
>> I will keep you posted if I hear any updates on my case. 
>> 
>> Regards 
>> Sarav 
>> +65 9857 8665
>> 
>> 
>>>> On 20 Aug 2020, at 10:10 PM, Erwann SIMON  wrote:
>>> 
>>> Hello,
>>> 
>>> I've just upgraded some servers to that level and I do not encounter this 
>>> king of issue (right now...).
>>> 
>>> -- 
>>> Best regards / Cordialement / مع تحياتي
>>> Erwann SIMON
>>> 
>>> - Mail original -
>>> De: "Saravanan Palanisamy" 
>>> À: ADSM-L@VM.MARIST.EDU
>>> Envoyé: Mardi 21 Juillet 2020 00:37:41
>>> Objet: [ADSM-L] Replication Hung after upgrade to v8.1.10
>>> 
>>> Dear Team
>>> 
>>> Is there anyone facing intermittent replication hung issue after upgrade to 
>>> v8.1.10? 
>>> 
>>> We have upgraded TSM server from 8.1.9.300 to 8.1.10 and replication 
>>> process is hung intermittently on all 3 servers. Just want to see whether 
>>> anyone else impacted. 
>>> 
>>> Once restart TSM instance then replication works but again replication node 
>>> process will get hung. But we don’t see any hung for protect stg and it 
>>> works fine. 
>>> 
>>> We have raised case with IBM and working on it.
>>> 
>>> Regards 
>>> Sarav 
>>> +65 9857 8665
>> 
>> For information, services and offers, please visit our web site: 
>> http://www.klm.com. This e-mail and any attachment may contain confidential 
>> and privileged material intended for the addressee only. If you are not the 
>> addressee, you are notified that no part of the e-mail or any attachment may 
>> be disclosed, copied or distributed, and that any other action related to 
>> this e-mail or attachment is strictly prohibited, and may be unlawful. If 
>> you have received this e-mail by error, please notify the sender immediately 
>> by return e-mail, and delete this message.
>> 
>> Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
>> employees shall not be liable for the incorrect or incomplete transmission 
>> of this e-mail or any attachments, nor responsible for any delay in receipt.
>> Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
>> Airlines) is registered in Amstelveen, The Netherlands, with registered 
>> number 33014286
>&g

Re: Replication Hung after upgrade to v8.1.10

2020-08-24 Thread Saravanan Palanisamy
RHEL v7 

Regards 
Sarav 
+65 9857 8665


> On 24 Aug 2020, at 7:15 PM, Sasa Drnjevic  wrote:
> 
> Thank you Sarav,
> 
> and what are the architectures of those 3 different pairs you have
> upgraded to v8.1.10 and now experience Replication hangs?
> 
> Linux, AIX, Windows...?
> 
> 
> Regards,
> 
> --
> Sasa Drnjevic
> www.srce.unizg.hr/en/
> 
> 
> 
> 
> 
>> On 24.8.2020. 12:42, Saravanan Palanisamy wrote:
>> Hi Sasa, 
>> 
>> Replication payload will vary for each server and it’s about 1 TB to 5 TB. 
>> 
>> Case is pending with dev team now. Will update once I hear from them. 
>> 
>> Regards 
>> Sarav 
>> +65 9857 8665
>> 
>> 
>>>> On 24 Aug 2020, at 5:17 PM, Sasa Drnjevic  wrote:
>>> 
>>> Dear Sarav,
>>> 
>>> can you please post which are the architectures of those 3 different
>>> pairs you have upgraded to v8.1.10 and now experience Replication hangs?
>>> 
>>> What is the approx daily replication payload you have?
>>> 
>>> Has there been any progress to solve it?
>>> 
>>> Thank you!
>>> 
>>> Regards,
>>> 
>>> --
>>> Sasa Drnjevic
>>> www.srce.unizg.hr/en/
>>> 
>>> 
>>> 
>>> 
>>>> On 20.8.2020. 16:58, Saravanan Palanisamy wrote:
>>>> Thanks Erwann for the update. 
>>>> 
>>>> We are still facing intermittent hang and no progress on our case. If it’s 
>>>> one server then we could say it’s environment issue but 3 different pair 
>>>> and all are in different countries as well. We are holding upgrade for 
>>>> rest of countries until find out root cause. 
>>>> 
>>>> There is also one more issue on v8.1.10 where server will crash abruptly 
>>>> if you use directory container. It appears to be known issue and we have 
>>>> got efix to address it. 
>>>> 
>>>> I will keep you posted if I hear any updates on my case. 
>>>> 
>>>> Regards 
>>>> Sarav 
>>>> +65 9857 8665
>>>> 
>>>> 
>>>>>> On 20 Aug 2020, at 10:10 PM, Erwann SIMON  wrote:
>>>>> 
>>>>> Hello,
>>>>> 
>>>>> I've just upgraded some servers to that level and I do not encounter this 
>>>>> king of issue (right now...).
>>>>> 
>>>>> -- 
>>>>> Best regards / Cordialement / مع تحياتي
>>>>> Erwann SIMON
>>>>> 
>>>>> - Mail original -
>>>>> De: "Saravanan Palanisamy" 
>>>>> À: ADSM-L@VM.MARIST.EDU
>>>>> Envoyé: Mardi 21 Juillet 2020 00:37:41
>>>>> Objet: [ADSM-L] Replication Hung after upgrade to v8.1.10
>>>>> 
>>>>> Dear Team
>>>>> 
>>>>> Is there anyone facing intermittent replication hung issue after upgrade 
>>>>> to v8.1.10? 
>>>>> 
>>>>> We have upgraded TSM server from 8.1.9.300 to 8.1.10 and replication 
>>>>> process is hung intermittently on all 3 servers. Just want to see whether 
>>>>> anyone else impacted. 
>>>>> 
>>>>> Once restart TSM instance then replication works but again replication 
>>>>> node process will get hung. But we don’t see any hung for protect stg and 
>>>>> it works fine. 
>>>>> 
>>>>> We have raised case with IBM and working on it. 
>>>>> 
>>>>> Regards 
>>>>> Sarav 
>>>>> +65 9857 8665


Re: Replication Hung after upgrade to v8.1.10

2020-08-24 Thread Saravanan Palanisamy
Hi Sasa, 

Replication payload will vary for each server and it’s about 1 TB to 5 TB. 

Case is pending with dev team now. Will update once I hear from them. 

Regards 
Sarav 
+65 9857 8665


> On 24 Aug 2020, at 5:17 PM, Sasa Drnjevic  wrote:
> 
> Dear Sarav,
> 
> can you please post which are the architectures of those 3 different
> pairs you have upgraded to v8.1.10 and now experience Replication hangs?
> 
> What is the approx daily replication payload you have?
> 
> Has there been any progress to solve it?
> 
> Thank you!
> 
> Regards,
> 
> --
> Sasa Drnjevic
> www.srce.unizg.hr/en/
> 
> 
> 
> 
>> On 20.8.2020. 16:58, Saravanan Palanisamy wrote:
>> Thanks Erwann for the update. 
>> 
>> We are still facing intermittent hang and no progress on our case. If it’s 
>> one server then we could say it’s environment issue but 3 different pair and 
>> all are in different countries as well. We are holding upgrade for rest of 
>> countries until find out root cause. 
>> 
>> There is also one more issue on v8.1.10 where server will crash abruptly if 
>> you use directory container. It appears to be known issue and we have got 
>> efix to address it. 
>> 
>> I will keep you posted if I hear any updates on my case. 
>> 
>> Regards 
>> Sarav 
>> +65 9857 8665
>> 
>> 
>>>> On 20 Aug 2020, at 10:10 PM, Erwann SIMON  wrote:
>>> 
>>> Hello,
>>> 
>>> I've just upgraded some servers to that level and I do not encounter this 
>>> king of issue (right now...).
>>> 
>>> -- 
>>> Best regards / Cordialement / مع تحياتي
>>> Erwann SIMON
>>> 
>>> - Mail original -
>>> De: "Saravanan Palanisamy" 
>>> À: ADSM-L@VM.MARIST.EDU
>>> Envoyé: Mardi 21 Juillet 2020 00:37:41
>>> Objet: [ADSM-L] Replication Hung after upgrade to v8.1.10
>>> 
>>> Dear Team
>>> 
>>> Is there anyone facing intermittent replication hung issue after upgrade to 
>>> v8.1.10? 
>>> 
>>> We have upgraded TSM server from 8.1.9.300 to 8.1.10 and replication 
>>> process is hung intermittently on all 3 servers. Just want to see whether 
>>> anyone else impacted. 
>>> 
>>> Once restart TSM instance then replication works but again replication node 
>>> process will get hung. But we don’t see any hung for protect stg and it 
>>> works fine. 
>>> 
>>> We have raised case with IBM and working on it. 
>>> 
>>> Regards 
>>> Sarav 
>>> +65 9857 8665


Re: Replication Hung after upgrade to v8.1.10

2020-08-20 Thread Saravanan Palanisamy
IT33437

Regards 
Sarav 
+65 9857 8665


> On 20 Aug 2020, at 11:05 PM, Loon, Eric van (ITOP NS) - KLM 
>  wrote:
> 
> Hi Sarav,
> 
> You stated " There is also one more issue on v8.1.10 where server will crash 
> abruptly if you use directory container. It appears to be known issue and we 
> have got efix to address it". I find this very alarming, because I'm about to 
> start production on a new server running this level. Do you have an APAR 
> number?
> 
> Kind regards,
> Eric van Loon
> Air France/KLM Storage & Backup
> 
> 
> -----Original Message-
> From: ADSM: Dist Stor Manager  On Behalf Of Saravanan 
> Palanisamy
> Sent: donderdag 20 augustus 2020 16:58
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: Replication Hung after upgrade to v8.1.10
> 
> Thanks Erwann for the update. 
> 
> We are still facing intermittent hang and no progress on our case. If it’s 
> one server then we could say it’s environment issue but 3 different pair and 
> all are in different countries as well. We are holding upgrade for rest of 
> countries until find out root cause. 
> 
> There is also one more issue on v8.1.10 where server will crash abruptly if 
> you use directory container. It appears to be known issue and we have got 
> efix to address it. 
> 
> I will keep you posted if I hear any updates on my case. 
> 
> Regards 
> Sarav 
> +65 9857 8665
> 
> 
>> On 20 Aug 2020, at 10:10 PM, Erwann SIMON  wrote:
>> 
>> Hello,
>> 
>> I've just upgraded some servers to that level and I do not encounter this 
>> king of issue (right now...).
>> 
>> -- 
>> Best regards / Cordialement / مع تحياتي
>> Erwann SIMON
>> 
>> - Mail original -
>> De: "Saravanan Palanisamy" 
>> À: ADSM-L@VM.MARIST.EDU
>> Envoyé: Mardi 21 Juillet 2020 00:37:41
>> Objet: [ADSM-L] Replication Hung after upgrade to v8.1.10
>> 
>> Dear Team
>> 
>> Is there anyone facing intermittent replication hung issue after upgrade to 
>> v8.1.10? 
>> 
>> We have upgraded TSM server from 8.1.9.300 to 8.1.10 and replication process 
>> is hung intermittently on all 3 servers. Just want to see whether anyone 
>> else impacted. 
>> 
>> Once restart TSM instance then replication works but again replication node 
>> process will get hung. But we don’t see any hung for protect stg and it 
>> works fine. 
>> 
>> We have raised case with IBM and working on it.
>> 
>> Regards 
>> Sarav 
>> +65 9857 8665
> 
> For information, services and offers, please visit our web site: 
> http://www.klm.com. This e-mail and any attachment may contain confidential 
> and privileged material intended for the addressee only. If you are not the 
> addressee, you are notified that no part of the e-mail or any attachment may 
> be disclosed, copied or distributed, and that any other action related to 
> this e-mail or attachment is strictly prohibited, and may be unlawful. If you 
> have received this e-mail by error, please notify the sender immediately by 
> return e-mail, and delete this message.
> 
> Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
> employees shall not be liable for the incorrect or incomplete transmission of 
> this e-mail or any attachments, nor responsible for any delay in receipt.
> Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
> Airlines) is registered in Amstelveen, The Netherlands, with registered 
> number 33014286
> 


Re: Replication Hung after upgrade to v8.1.10

2020-08-20 Thread Saravanan Palanisamy
Thanks Erwann for the update. 

We are still facing intermittent hang and no progress on our case. If it’s one 
server then we could say it’s environment issue but 3 different pair and all 
are in different countries as well. We are holding upgrade for rest of 
countries until find out root cause. 

There is also one more issue on v8.1.10 where server will crash abruptly if you 
use directory container. It appears to be known issue and we have got efix to 
address it. 

I will keep you posted if I hear any updates on my case. 

Regards 
Sarav 
+65 9857 8665


> On 20 Aug 2020, at 10:10 PM, Erwann SIMON  wrote:
> 
> Hello,
> 
> I've just upgraded some servers to that level and I do not encounter this 
> king of issue (right now...).
> 
> -- 
> Best regards / Cordialement / مع تحياتي
> Erwann SIMON
> 
> ----- Mail original -
> De: "Saravanan Palanisamy" 
> À: ADSM-L@VM.MARIST.EDU
> Envoyé: Mardi 21 Juillet 2020 00:37:41
> Objet: [ADSM-L] Replication Hung after upgrade to v8.1.10
> 
> Dear Team
> 
> Is there anyone facing intermittent replication hung issue after upgrade to 
> v8.1.10? 
> 
> We have upgraded TSM server from 8.1.9.300 to 8.1.10 and replication process 
> is hung intermittently on all 3 servers. Just want to see whether anyone else 
> impacted. 
> 
> Once restart TSM instance then replication works but again replication node 
> process will get hung. But we don’t see any hung for protect stg and it works 
> fine. 
> 
> We have raised case with IBM and working on it. 
> 
> Regards 
> Sarav 
> +65 9857 8665


Replication Hung after upgrade to v8.1.10

2020-07-20 Thread Saravanan Palanisamy
Dear Team

Is there anyone facing intermittent replication hung issue after upgrade to 
v8.1.10? 

We have upgraded TSM server from 8.1.9.300 to 8.1.10 and replication process is 
hung intermittently on all 3 servers. Just want to see whether anyone else 
impacted. 

Once restart TSM instance then replication works but again replication node 
process will get hung. But we don’t see any hung for protect stg and it works 
fine. 

We have raised case with IBM and working on it. 

Regards 
Sarav 
+65 9857 8665


Re: MS SQL for Linux

2020-04-23 Thread Saravanan Palanisamy
Thank You Del. 

I have voted for the request. 

Regards 
Sarav 
+65 9857 8665


> On 24 Apr 2020, at 6:19 AM, Del Hoobler  wrote:
> 
> Hi Sarav,
> 
> We have not seen a lot of demand for this yet. If you are interested, 
> please vote for this RFE:
> 
> http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=108504
> 
> 
> Del
> 
> 
> 
> "ADSM: Dist Stor Manager"  wrote on 04/23/2020 
> 03:28:25 PM:
> 
>> From: Saravanan Palanisamy 
>> To: ADSM-L@VM.MARIST.EDU
>> Date: 04/23/2020 03:29 PM
>> Subject: [EXTERNAL] MS SQL for Linux
>> Sent by: "ADSM: Dist Stor Manager" 
>> 
>> Team
>> 
>> Done anyone know whether IBM will support Linux MS SQL in near future ?
>> 
>> 
>> Regards
>> Sarav
>> +65 9857 8665
>> 


MS SQL for Linux

2020-04-23 Thread Saravanan Palanisamy
Team

Done anyone know whether IBM will support Linux MS SQL in near future ?


Regards
Sarav
+65 9857 8665


RFE to address overlap issue

2019-10-02 Thread Saravanan Palanisamy
Team 


Would appreciate if you can vote for below RFE to address schedule overlap 
issue with Fourth and Last Week of the month. 


> https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=135079
> 


> Regards 
> Sarav 
> +65 9857 8665
> 


Spectrum Protect Meta Data replication feature

2019-08-07 Thread Saravanan Palanisamy
Hello Everyone 


Does anyone know when Spectrum Protect release feature to replicate meta data 
between TSM servers for data resides in Object storage ? 

Regards 
Sarav 
+65 9857 8665


Replication for IBM Cleversafe nodes

2019-05-22 Thread Saravanan Palanisamy
Dear Folks,

Is this recommended to run replicate node alone since it won't support
protect stgpool command for cloud container storage pool ? Did anyone try
this option for daily more than 10 Tb provided you have sufficient network
bandwidth ? When we test for 1 or 2 Tb it works well but not sure whether
it's recommended for 10 to 15 Tb ?

or

Is it recommended to use hardware level replication for IBM clever safe
nodes and perform DR scenario for offsite copy ?

Regards,
Sarav


Repli server db usage is high than Primary server

2019-02-02 Thread Saravanan Palanisamy
Hello Experts,

What cases repl server would have more db usage than primary server. Here I go 
with one setup in similar situation.
Primary server db usage - 67% (out of 6TB)
Replication Server db usage  - 96% (out of 6TB)

repli server uses only for replication purpose, no there native backups 
configured over there.

suggestion pl.

- Saravanan


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"
>> 
> <https://www-01.ibm.com/support/docview.wss?uid=swg21646952#wincommon_probs>
> 
>> 
>> 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=
>> 


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

NDMP Backup Problem

2017-08-09 Thread Saravanan Palanisamy
Dear Experts,

I am looking for your advice on below topic.

We have NDMP backups are configured with SP Server (7.1.6). The Netapp ( v8.5 , 
7 mode) setup would be like, the remote site production filer has been syncing 
the data to DR site Filer (snapmirror).
The TSM NDMP backup is configured from DR site. The tape drives are zoned to 
NAS filer and volume backups are scheduled from TSM schedule (backup node ).

Few days before, one of Netapp vol usage was grownup to 300 % ( earlier 4 TB,  
current size - 8.6 TB and dudup is 64% so, current size is around 14 TB).

After the data increase, the specific volume's backup started to failed in all 
methods like,  full, differential and with out TOC and with TOC.   The backup 
is failing in varies stages like after the completion of 20, 40 , 50%.

Any advice ?

Regards,
Saravanan


Re: LTO4 Tape Recovery

2017-03-10 Thread Saravanan Palanisamy
TSM v7.1.7

Regards 
Sarav 
+65 9857 8665


> On 10 Mar 2017, at 8:05 PM, Sasa Drnjevic  wrote:
> 
> Hi.
> Which TSM version?
> 
> I used the following long time ago... It is a long shot. I wish you luck
> 
> Get this  tsmtape0.1.tar.z  here:
> 
> https://sourceforge.net/projects/tsmtape/
> 
> 
> This is an excerpt from a README:
> =
> 
>Description:
>TSMtape recovers files from a Tivoli Storage Manager (TSM) v5.x tape.
> 
> 
>Detail:
>TSM is unable to import a rogue tape that is not identified within
>its database or restore a file located on a known tape after it has
> been expired.
>TSMtape will allow the recovery of these files by reading a TSM v5.x
> (tested against 5.2)
>tape and allowing restoration or listing of all files without need
> of the
>TSM software or database.
> 
>OS:
>Updated to compile/run on Linux x86. gcc version 3.3.3 (SuSE Linux)
> 
> 
>History:
>TSMtape is based off adsmtape written by Thorhallur Sverrisson who
>released the original work under GNU GPL. adsmtape targeted ADSM
>(predecessor to TSM) v3 and was written for AIX.
>https://sourceforge.net/projects/adsmtape/
> 
>Build:
>untar the files and run make.
> 
>Usage:
>   ./TSMtape [-R|restore]   
>or
>   ./TSMtape [-A|--audittape]  
> 
>Options:
>-h, --help  display this help and exit
>-A, --audit Output list of files stored on tape with supporting
> details in csv format
>-R, --restore   Restore "your" files ;-)
> File parsing can be a partial or full path, Use a
> '/' as a catchall
> 
>-v[vv]  Print additional debugging information
> 
>   Example:
> ./TSMtape --restore /dev/st0 /etc/shadow /tmp/recovered
> ./TSMtape --audit /dev/st0 / /tmp/tapefiles.csv
> 
> ...
> ..
> .
> 
> ==
> ==
> 
> 
> Regards,
> 
> --
> Sasa Drnjevic
> www.srce.unizg.hr
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>> On 10.3.2017. 5:22, Saravanan Palanisamy wrote:
>> Folks,
>> 
>> I badly need some help
>> 
>> One of the data got deleted from TSM database but tape wasn't not re-used 
>> and it's available in PCT reclaimable. This tape also never overwritten. 
>> Unfortunately I don't have TSM DB backup for the the same date.
>> 
>> We need this data and can anyone tried to recover this previously.
>> 
>> Does IBM have any other tool to recover such cases ?
>> 
>> Regards
>> Sarav
>> +65 9857 8665
>> 


LTO4 Tape Recovery

2017-03-09 Thread Saravanan Palanisamy
Folks, 

I badly need some help 

One of the data got deleted from TSM database but tape wasn't not re-used and 
it's available in PCT reclaimable. This tape also never overwritten. 
Unfortunately I don't have TSM DB backup for the the same date. 

We need this data and can anyone tried to recover this previously. 

Does IBM have any other tool to recover such cases ? 

Regards 
Sarav 
+65 9857 8665


Tsm server 7.1.6.3

2016-11-10 Thread Saravanan Palanisamy
> 
> Do we have tsm server package 7.1.6.3 software for AIX ?? I couldn't find it 
> in ftp site and passport advantage 
> 
> 
> "Select * from events " is not working on 7.1.6.0 and same has been fixed in 
> next version 
> 
> Unfortunately 7.1.7 installation package also failed when run "install.sh -c" 
> ( downloaded from passport site ) ( 2 servers worked and 2 servers failed ) 
> 
> Do we have fix pack 7.1.6.x for aix ?? 
> 
> 
> Regards 
> Sarav 
> +65 9857 8665
> 


Add on tools /software

2016-09-30 Thread Saravanan Palanisamy
Greetings !!

Do we have any tool or software to manage tsm client scheduler from centralised 
tool/software ??

Something like checking tsm logs and restarting tsm services without logging 
into client server 

Would really appreciate your inputs 

Regards 
Sarav 
+65 9857 8665


Spectrum Protect support for I series

2016-07-29 Thread Saravanan Palanisamy
Just noticed that TSM support has been withdrawn for IBM i on TSM 6.2 , Is
this confirmed and latest Spectrum Protect version doesn't support IBM i ?


With the EOS of TSM 6.2, access to TSM Servers through the TSM API on IBM i
will also reach EOS. TSM 6.2 is the *last *version of TSM that will support
IBM i. *No further versions of TSM will have API support for IBM i.*

https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20Backup%2C%20Recovery%20and%20Media%20Services%20%28BRMS%29%20for%20i/page/Tivoli%20Storage%20Manager%20%28TSM%29




--
Thanks & Regards,
Saravanan
Mobile: +65-8228 4384


Re: How to tell what VM's are running backup in TSM for VE 7.1?

2015-04-25 Thread Saravanan Palanisamy
Hi Steve, 

There will be snapshot creation message for each Virtual machine backup and 
once backup got completed then it will create another entry for snapshot 
deletion in Vcenter task log. You can use this task log to identify latest 
backup. 



By Sarav
+65-82284384


> On 25 Apr 2015, at 8:54 pm, Schaub, Steve  wrote:
> 
> Eric, can you point me to where exactly in the vCenter web gui I can see this?
> Thanks,
> -steve
> 
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
> McWilliams, Eric
> Sent: Friday, April 24, 2015 9:28 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] How to tell what VM's are running backup in TSM for VE 
> 7.1?
> 
> The only thing I've found that shows me what jobs are currently running is in 
> vCenter.
> 
> 
> Eric 
> 
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
> Schaub, Steve
> Sent: Friday, April 24, 2015 7:15 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] How to tell what VM's are running backup in TSM for VE 
> 7.1?
> 
> Thanks to everyone who responded, but from what I'm seeing, none of these 
> queries show me which VM's are currently backing up?  Completed/fail, yes.  
> When I have 20-30 concurrent nodes running, and someone wants to know exactly 
> which ones are running, I'm at a loss.  Obviously VE must know, why isn't the 
> info exposed somewhere obvious?
> Very frustrating.
> -steve
> 
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
> Schneider, Jim
> Sent: Thursday, April 23, 2015 4:37 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] How to tell what VM's are running backup in TSM for VE 
> 7.1?
> 
> This is close.  I check time stamps to identify failures.  The time stamp 
> could also indicate a backup in progress.
> 
> select substr(filespace_name,9,18) as VM, filespace_id as FSID, 
> cast(backup_end as char(19) ) as "Backup Completed" from filespaces where 
> node_name='VC1_CH2_DM' order by 3
> 
> Jim Schneider
> 
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
> Schaub, Steve
> Sent: Thursday, April 23, 2015 3:22 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: [ADSM-L] How to tell what VM's are running backup in TSM for VE 7.1?
> 
> Running into some issues troubleshooting VE backups and hopefully I just 
> don't know where to look.
> I came in this morning and was surprised to find that one of my datamovers 
> was still running a schedule.
> There were 2 sessions in TSM, but of course they were using the datacenter 
> name so I had no idea what was running, or what was still waiting to run.
> So what do I use to gain visibility into a running VE schedule?
> I want to know:
> 
> 1.   What is running
> 
> 2.   What has completed
> 
> 3.   What is waiting to run
> I tried deciphering it from dsmsched.log, but gave up looking for those 
> needles in that haystack.
> I also went to the VE web UI hoping "reports/recent tasks" would help, but 
> nothing showed up there.
> Surely there is some easy way to do this simple task that I have overlooked 
> in the manual?
> 
> Steve Schaub
> Systems Engineer II, Backup/Recovery
> Blue Cross Blue Shield of Tennessee
> 
> -
> Please see the following link for the BlueCross BlueShield of Tennessee 
> E-mail disclaimer:  
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.bcbst.com_email-5Fdisclaimer.shtm&d=AwIFAg&c=MaiD1Z8YVCD63kI1LCyPtWg0Yfm6VFptlj7wuHNxy-0&r=ohMdG7xLBNfJLpBxDYE1hxG5DHMxVAlyhTmATkid320&m=VIPhTO-oTQWGHjIONlYGjBE4zbFQXd7gRTxtv6vY9OM&s=zPQoR6cgZiHSFr7zdM2XwO-R6LwNGk3-XNAZRGNXM8A&e=
>  
> 
> **
> Information contained in this e-mail message and in any attachments thereto 
> is confidential. If you are not the intended recipient, please destroy this 
> message, delete any copies held on your systems, notify the sender 
> immediately, and refrain from using or disclosing all or any part of its 
> content to any other person.
> -
> Please see the following link for the BlueCross BlueShield of Tennessee 
> E-mail disclaimer:  
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.bcbst.com_email-5Fdisclaimer.shtm&d=AwIFAg&c=MaiD1Z8YVCD63kI1LCyPtWg0Yfm6VFptlj7wuHNxy-0&r=ohMdG7xLBNfJLpBxDYE1hxG5DHMxVAlyhTmATkid320&m=VIPhTO-oTQWGHjIONlYGjBE4zbFQXd7gRTxtv6vY9OM&s=zPQoR6cgZiHSFr7zdM2XwO-R6LwNGk3-XNAZRGNXM8A&e=
>  
> 
> **
> *** CONFIDENTIALITY NOTICE *** 
> 
> This message and any included attachments are from MedSynergies, Inc. and are 
> intended only for the addressee. The contents of this message contain 
> confidential information belonging to the sender that is legally protected. 
> Unauthorized forwarding, printing

Re: How to tell what VM's are running backup in TSM for VE 7.1?

2015-04-24 Thread Saravanan Palanisamy
Hi Steve, 

You can check query fi node f=d 

By Sarav
+65-82284384


> On 24 Apr 2015, at 4:22 am, Schaub, Steve  wrote:
> 
> Running into some issues troubleshooting VE backups and hopefully I just 
> don't know where to look.
> I came in this morning and was surprised to find that one of my datamovers 
> was still running a schedule.
> There were 2 sessions in TSM, but of course they were using the datacenter 
> name so I had no idea what was running, or what was still waiting to run.
> So what do I use to gain visibility into a running VE schedule?
> I want to know:
> 
> 1.   What is running
> 
> 2.   What has completed
> 
> 3.   What is waiting to run
> I tried deciphering it from dsmsched.log, but gave up looking for those 
> needles in that haystack.
> I also went to the VE web UI hoping "reports/recent tasks" would help, but 
> nothing showed up there.
> Surely there is some easy way to do this simple task that I have overlooked 
> in the manual?
> 
> Steve Schaub
> Systems Engineer II, Backup/Recovery
> Blue Cross Blue Shield of Tennessee
> 
> -
> Please see the following link for the BlueCross BlueShield of Tennessee 
> E-mail disclaimer:  http://www.bcbst.com/email_disclaimer.shtm


How to setup dedicated tape drives for storage agent

2014-09-15 Thread Saravanan Palanisamy
Dear TSM Folks,

Has anybody tried this approach to enhance tape drive availability ?

Create 64 tape drives in data domain and allocate 32 tape drives only for
TSM server backup ( Lan based backup) and remaining 32 tape drives dedicate
for storage agent

Is this possible to implement this setup ?

I really had concern because storage agent definitely need tape drive
should be defined and path must be online in TSM server before defining
path for storage agent.

Will it work if turn off tape drive path in TSM server and only turn on
corresponding path for storage agent ? I never tried this approach and has
anybody got real time experience on this setup?

--
Thanks & Regards,
Saravanan
Mobile: +65-86966188


Re: TSM server preparedb failed

2014-04-10 Thread Saravanan Palanisamy
Below is message but didn't receive any error.

TSM server Version : 5.5.4.0
TSM upgrade utility : 5.5.4.0

root@rlruscdb:/usr/tivoli/tsm/server/bin# nohup
/usr/tivoli/tsm/upgrade/bin/dsmupgrd preparedb >prepare.out 2>&1 &
[1] 8454158
root@rlruscdb:/usr/tivoli/tsm/server/bin# tail -100f prepare.out
ANR7800I DSMSERV generated at 13:40:49 on Jan 28 2013.
Tivoli Storage Manager for AIX-RS/6000
Version 5, Release 5, Level 7.0
Licensed Materials - Property of IBM
(C) Copyright IBM Corporation 1990, 2009.
All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corporation.
ANR0900I Processing options file /usr/tivoli/tsm/server/bin/dsmserv.opt.
ANR7811I Using instance directory /usr/tivoli/tsm/server/bin.
ANR4726I The ICC support module has been loaded.
ANR0990I Server restart-recovery in progress.
ANR0200I Recovery log assigned capacity is 9416 megabytes.
ANR0201I Database assigned capacity is 24576 megabytes.
ANR0306I Recovery log volume mount in progress.
ANR0353I Recovery log analysis pass in progress.
ANR0354I Recovery log redo pass in progress.
ANR0355I Recovery log undo pass in progress.
ANR0352I Transaction recovery complete.
ANR1635I The server machine GUID,
3d.be.a1.f0.84.1e.11.d7.8e.0b.08.63.0a.01.02-
.0d, has initialized.
root@rlruscdb:/usr/tivoli/tsm/server/bin#

Tried fore ground but not progress after ANR1635I and it return to OS
On Thu, Apr 10, 2014 at 2:55 PM, Saravanan wrote:

> Hi TSM folks,,,
>
> Have started TSM server upgrade and it got stopped during prepare db phase
>
> No error message but stopped after ANR1635I message
>
> Any light on it ?
>
>
>
>
> By Sarav
> +65-82284384
>
>
>


--
 Thanks & Regards,
Saravanan
Mobile: +65-86966188


Re: Database question :)

2013-12-13 Thread Saravanan Palanisamy
Hi Mickael,

You can go for TSM with HADR ...

http://emmanuel.iffly.free.fr/doku.php?id=tsm:tsm_hadr


On Fri, Dec 13, 2013 at 10:05 PM, mik  wrote:

> Hi everybody, always me :)
>
> I have a question for you (Rick if you know lol)
>
> In my dream i'am ask if it's possible to have to TSM sharing database?
>
> I'am explain better
>
> I want a TSM in charge of the stockage on tape and share his database (or
> echange information with the other database) with an another TSM (in charge
> of the backupset in other)
>
> Or i want to put in place a TSM in Clustering with another in case of the
> TSM server go down i continu to have a TSM in rescues.
>
> Do you understand what i want or may be it's a stupid idea lol
>
> Regards, Mickael.
>
> +--
> |This was sent by bobpatrick808...@yahoo.fr via Backup Central.
> |Forward SPAM to ab...@backupcentral.com.
> +--
>



--
Thanks & Regards,
Saravanan
Mobile: +65-86966188


TSM for VE - Error

2013-03-06 Thread Saravanan Palanisamy
Dear Team,

Did anyone see below error while backup's vmware guest machine from proxy
server.

03/06/2013 03:23:18 ANS9365E VMware vStorage API error for virtual machine
''.
   TSM function name : VixDiskLib_Open
   TSM file  : vmvddksdk.cpp (1745)
   API return code   : 13
   API error message : You do not have access rights to this file
03/06/2013 03:23:18 ANS5283E The operation was unsuccessful.

I have 6 VM's and only 3 VM's got backed up successfully and rest of the
VM's were failed with API return code 13.

I would really appreciate if anybody help me on this issue.

--
Thanks & Regards,
Saravanan
Mobile: +65-86966188


TSM server 6.3.1 backup sessions hung

2012-09-05 Thread Saravanan Palanisamy
Dear Team,

We have strange issue in our environment. We are facing this issue after
upgraded TSM server from 6.1.3 to 6.3.1.

Around 8 PM( Regular backpus will start by 6 PM) all the backups sessions
are hanging and we don't see any backup progress. First time we thought it
might complete in some time unfortunatly it took more than 14 hours just
for 10 GB of data and it never completes. We have restarted the TSM server
and the same backup was completed with in 14 minutes. This issue is
intermittent( 3 days once and 4 days once). If we restart the TSM sever
then everything is working as desired.


When we investigate from DB2 end, we don't see any db2 table maintaince
utilities (i.e runstats, reorg) running in the server. Also we are able to
login into the TSM server and check the backup status. We don't have any
clue to identify the issue.

I would really appriciate if somebody shares any idea for this issue.


--
 Thanks & Regards,
Saravanan
Mobile: +65-86966188


SAP BR Offline backup is very slow

2012-06-23 Thread Saravanan Palanisamy
Dear Team,

I am facing very strange issue in my environment and i would desperatly
looking for some help.

We have recently applied below AIX patch on SAP servers and it cause the BR
Offline backup to pretty slow.

Vulnerability in LDAP Authentication
JRE hangs when converting Java
Multiple vulnerabilities in AIX BIND
Sudo format string vulnerability
Vulnerability in ICMP packet handling
TCP network packet denial of service

AIX: 6100-06-05-1115
TSM server : 5.5.6.1
Storage Agent Version: 5.5.6.0
TDP for R3 : 5.5.0.0
TSM BA Client : 5.5.3.4

BR Online backup running fine( both LAN and LAN-Free backup)
BR Offline backup running fine only in LAN based backup but in LAN-Free
backup it's very slow.
While BR Offline backup runs, i have tested some file level backup over the
storage agent and backup throughput was really good.( Transfered 22 GB of
data and it took only 4 min)

We have applied the AIX patches on 4 servers( 3 SAP Oracle, 1 Oracle) and
all the four servers the BR Offline backups are running very slowly. I have
raised the PMR but they are not ready to help at this moment( due to
performance issue)

Here is the one piece transfer speed.

BKI2017I: Blocksize is set to 131072 bytes
BKI0027I: Time: 05/27/12 02:30:53 Object: 1 of 23 in process:
/oracle/DA1/sapdata6/sr3701_3/sr3701.data3 Size: 22.000 GB, MGMNT-CLASS:
WSWT-NONPROD-MCDAILY, TSM-Server: DCWTSM .
BKI0023I: Time: 05/27/12 02:35:26 Done: 22.000 GB (7.4 %) of 296.310 GB.
Estimated end time: 05/27/12 03:32:59.
BKI0053I: Time: 05/27/12 02:35:26 Object: 1 of 23 done:
/oracle/DA1/sapdata6/sr3701_3/sr3701.data3 with: 22.000 GB saved with
description DA1___A0H2P0MBFU.

Before apply the patch BR Offline backup took only *4 min 27 sec*


BKI0027I: Time: 06/24/12 03:20:26 Object: 2 of 24 in process:
/oracle/DA1/sapdata6/sr3701_4/sr3701.data4 Size: 24.414 GB, MGMNT-CLASS:
WSWT-NONPROD-MCDAILY, TSM-Server: DCWTSM .
BKI0023I: Time: 06/24/12 03:40:22 Done: 50.781 GB (16.5 %) of 307.604 GB.
Estimated end time: 06/24/12 07:40:30.
BKI0053I: Time: 06/24/12 03:40:22 Object: 2 of 24 done:
/oracle/DA1/sapdata6/sr3701_4/sr3701.data4 with: 24.414 GB saved with
description DA1___A0H3T1QJWB.

After apply the patch BR Offline backup took *20 min*



--
 Thanks & Regards,
Saravanan
Mobile: +65-86966188


Tivoli Storage Manager API initialization, rc = 610

2012-05-25 Thread Saravanan Palanisamy
 Team,

I am facing TDP for domino API issue. Did anyone faced this issue earlier?

notes> domdsmc query adsm
IBM Tivoli Storage Manager for Mail:
Data Protection for Lotus Domino
Version 5, Release 5, Level 3.0
(C) Copyright IBM Corporation 1999, 2010. All rights reserved.
 ACD5412W An error was encountered with Tivoli Storage Manager API
initialization, rc = 610.
Examine the dsierror.log for more information or determine if the TSM API
is installed properly.
 Warning! Error initializing the connection to the TDP library
Could not connect to the Adsm server



--
 Thanks & Regards,
Saravanan


Re: Tape Volume usage

2012-05-25 Thread Saravanan Palanisamy
Team,

I am facing TDP for domino API issue. Did anyone faced this issue earlier?

notes> domdsmc query adsm
IBM Tivoli Storage Manager for Mail:
Data Protection for Lotus Domino
Version 5, Release 5, Level 3.0
(C) Copyright IBM Corporation 1999, 2010. All rights reserved.
 ACD5412W An error was encountered with Tivoli Storage Manager API
initialization, rc = 610.
Examine the dsierror.log for more information or determine if the TSM API
is installed properly.
 Warning! Error initializing the connection to the TDP library
Could not connect to the Adsm server


Re: Multiple restore session fails in TSM5.3 on AIX5.5

2012-03-15 Thread Saravanan Palanisamy
You need to cancel the existing restore then only it will allow you to
perform any further restore.

dsmc q restore

dsmc can restore

use these commands

On Thu, Mar 15, 2012 at 6:32 PM, devesh  wrote:

> Hello All,
>
> I am trying to perform multiple restore operation parallely.
> But whenever I try, only one session start other session terminates with
> following error :
>
>
> ---
> ANS1247I Waiting for files from the server...
>
> >> Restore Processing Interrupted!! <<
> ANS1330S This node currently has a pending restartable restore session.
>
> The requested operation cannot complete until this session either
> completes or is canceled.
>
> ---
>
> I have changed the following setting to perform multiple restore:
>
> update node  maxnummp=10
> maxsession 25
>
> My device type is file
> I have set mountlimit to 10
>
> Also, I have changed the resourceutilization to 10 (changed in the dsm.sys
> file)
>
> thanks and regards,
> Devesh Gupta
>
> +--
> |This was sent by devesh.gu...@nechclst.in via Backup Central.
> |Forward SPAM to ab...@backupcentral.com.
> +--
>



--
Thanks & Regards,
Saravanan
Mobile: +65-86966188


Re: TSM 6.3

2011-11-17 Thread Saravanan Palanisamy
Hi Johnny,

When you install TSM 6.3, it will install the TSM API 6.2.2 by
default and your server will work as desired.

http://www-01.ibm.com/support/docview.wss?rs=663&context=SSGSG7&q1=TSM+known+issues&q2=TSM+6.3&uid=swg21568281&loc=en_US&cs=utf-8&lang=en

You can remove the old API and install the latest one 6.3.


On Wed, Nov 16, 2011 at 11:04 PM, Johnny Lea  wrote:

> Trying to install TSM 6.3 Server on a RHEL 6.1 server.
>
> I got the server installed but when installing the 6.3 client I get errors
> "fileconflicts with file from package TIVsm-API-6.2.2-0.i586".  The 6.2
> packages were installed by the 6.3 server install.
>
> Tried installing the client rpm with -ivh, -Uvh, -nodeps but getting same
> errors.
>
> Any ideas?
>
> Thanks,
> Johnny
>
>
>
> Individuals who have received this information in error or are not
> authorized to receive it must promptly return or dispose of the information
> and notify the sender. Those individuals are hereby notified that they are
> strictly prohibited from reviewing, forwarding, printing, copying,
> distributing or using this information in any way.
>



--
Thanks & Regards,
Sarav
TSM Specialist
Mobile: +974-3344-1538


Re: Many DB Backups

2011-10-24 Thread Saravanan Palanisamy
what do u see in activity log when automatic backup started?

q act se="An automatic full database backup " begind=-1



http://www.ibm.com/developerworks/wikis/display/tivolistoragemanager/Tivoli+Storage+Manager+V6.1.2+automatic+DB+backup

On Mon, Oct 24, 2011 at 12:45 PM, Richard van Denzel
wrote:

> Hi All,
>
> After upgrading a TSM server from 5.5.4.3 to 6.2.2.30 we see that DB
> Backups
> are taken every 10 minutes or so (FULL DB Backups).
> What can be causing this (no dedup running), and how can we stop this?
>
> Richard.
>



--
Thanks & Regards,
Sarav
Mobile: +974-3344-1538


Re: Data change rate

2011-10-12 Thread Saravanan Palanisamy
The below query will give the changed data rate.


select sum(LASTSESS_RECVD)/1024/1024/1024 "Changed data in GB" from nodes

On Wed, Oct 12, 2011 at 3:53 PM, Ehresman,David E.
wrote:

> Is there any way from the server side to get an estimate of overall client
> data change rate?
>



--
Thanks & Regards,
Sarav
Mobile: +974-3344-1538


Passthough disk attached hyper-v machine backup

2011-09-15 Thread Saravanan Palanisamy
Hi,

Will TSM support passthough disk attached Hyper-v Guest Machine backup?

I have one Hyper-v Guest machine and it has physical disk( Storage
disk) directly attached to the guest machine. The Symantec Backup Exec 2010
R3 doesn't support this kind of backup so i would be checking the
possibility from TSM end.

http://www.symantec.com/business/support/index?page=content&id=TECH87330&actp=search&viewlocale=en_US&searchid=1316079032152


--
Thanks & Regards,
Sarav
TSM Specialist
Mobile: +974-3344-1538


Re: AW: [ADSM-L] Rman not deleting old backups

2011-07-25 Thread Saravanan Palanisamy
You can run "crosscheck" command in RMAN prompt and see whether all the old
objects are able to identified or not. If not reported in "report obsolete"
after running "crosscheck" then create the new node and retain the old node
until it meets retention and remove the old node from TSM server.

 Also check what kind of files(i.e backup pieces, archive logs & control
files) are not expired and are they appearing in "report obsolete" output.

select
Node_name,FILESPACE_NAME,BACKUP_DATE,DEACTIVATE_DATE,CLASS_NAME,STATE,TYPE,HL_NAME,LL_NAME
from backups where BACKUP_DATE BETWEEN '2010-04-01 00:00:00.00' and
'2010-04-07 23:59:59.00' and node_name in('nodename')

On Mon, Jul 25, 2011 at 10:46 AM, Karl, Christian <
christian.k...@huk-coburg.de> wrote:

> Hi,
> ...bell rings, yes.
> The certain case is, when the databaseID has changed in the RMAN. When and
> why that happens you should ask your local DBA.
> All files that have been created with the old DB-ID are not referenced any
> more from RMAN and therefore are not deleted by RMAN.
> By the way,  it seems that you have to clean it up now. In that case
> TDPOSYNC etc. does not work as it does not list the old backups :)
> Best way is to define a new TSM-node for the affected DB's and let the old
> filespace (active data) expire.
> Deleting items inside TSM with the (not supported) delete command is not a
> good way to clean up the mess.
>
> Regards
> Chris Karl
>
>
>
>
>
>
>
> Christian Karl
> Abteilung Informatik Betrieb
>
> HUK-COBURG
> Bahnhofsplatz
> 96444 Coburg
> Telefon:  09561 96-44117
> Telefax:  09561 96-44104
> E-Mail:   christian.k...@huk-coburg.de
> Internet: www.huk.de
> ===
> HUK-COBURG Haftpflicht-Unterstützungs-Kasse kraftfahrender Beamter
> Deutschlands a. G. in Coburg
> Reg.-Gericht Coburg HRB 100; St.-Nr. 9212/101/00021
> Sitz der Gesellschaft: Bahnhofsplatz, 96444 Coburg
> Vorsitzender des Aufsichtsrats: Werner Strohmayr.
> Vorstand: Dr. Wolfgang Weiler (Sprecher), Wolfgang Flaßhoff, Stefan
> Gronbach, Klaus-Jürgen Heitmann, Dr. Hans Olav Herøy, Jörn Sandig.
> ===
> Diese Nachricht enthält vertrauliche und/oder rechtlich geschützte
> Informationen.
> Wenn Sie nicht der richtige Adressat sind oder diese Nachricht irrtümlich
> erhalten haben,
> informieren Sie bitte sofort den Absender und vernichten Sie diese
> Nachricht.
> Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Nachricht ist
> nicht gestattet.
>
> This information may contain confidential and/or privileged information.
> If you are not the intended recipient (or have received this information in
> error) please notify the
> sender immediately and destroy this information.
> Any unauthorized copying, disclosure or distribution of the material in
> this information is strictly forbidden.
> ===
>
> -Ursprüngliche Nachricht-
> Von: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Im Auftrag von
> molin gregory
> Gesendet: Montag, 25. Juli 2011 09:20
> An: ADSM-L@VM.MARIST.EDU
> Betreff: Re: [ADSM-L] Rman not deleting old backups
>
> Hello,
>
> In certain case, rman do not remove expired backup.
> You have to use tdposync for find/remove manualy backups.
>
> Regards, Cordialement,
> Grégory Molin
> Tel : 0141628162
> gregory.mo...@afnor.org
> -Message d'origine-
> De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de
> David E Ehresman
> Envoyé : vendredi 22 juillet 2011 17:35
> À : ADSM-L@VM.MARIST.EDU
> Objet : [ADSM-L] Rman not deleting old backups
>
> Awhile back someone shared on this list their commands/scripts for
> verifying that rman was not leaving any old backups on the TSM server.
> I can't seem to find it now.  Ring a bell with anyone?
>
> David
>
> "ATTENTION.
>
> Ce message et les pièces jointes sont confidentiels et établis à
> l'attention exclusive de leur destinataire (aux adresses spécifiques
> auxquelles il a été adressé). Si vous n'êtes pas le destinataire de ce
> message, vous devez immédiatement en avertir l'expéditeur et supprimer ce
> message et les pièces jointes de votre système.
>
> This message and any attachments are confidential and intended to be
> received only by the addressee. If you are not the intended recipient,
> please notify immediately the sender by reply and delete the message and any
> attachments from your system. "
>



-- 
Thanks & Regards,
Sarav
Mobile: +974-3344-1538
Email: evergreen.sa...@gmail.com, 
evergreen.sa...@yahoo.co.in
http://qa.linkedin.com/pub/saravanan-palanisamy/36/584/482

There are no secrets to success. It is the result of preparation, hard work
and learning from failure - Colin Powell


Re: SV: TSM 61 upgradation error...

2011-07-21 Thread Saravanan Palanisamy
ACUINI0029E The install version, $(acu.compatibleVersions), is not valid.
The installer will now shutdown. Please check with the log files for a more
complete description of the failure.
PRESS  TO CONTINUE:



http://www.ibm.com/developerworks/forums/thread.jspa?threadID=336789


Remove the old logs and directories and it will work
/var/tivoli/tsm
/usr/ibm
/var/ibm




On Thu, Jul 21, 2011 at 12:37 PM, Saravanan Palanisamy <
evergreen.sa...@gmail.com> wrote:

> what error you are looking in log file /var/tivoli/tsm/log.txt ?
>
> On Thu, Jul 21, 2011 at 8:19 AM, Christian Svensson <
> christian.svens...@cristie.se> wrote:
>
>> When do you get the problem and what OS are you running?
>> I sow on a Windows system where I needed to delete the installation
>> software directory between each upgrade step.
>>
>> /Christian
>>
>> -Ursprungligt meddelande-
>> Från: Kiran [mailto:ki...@dqentertainment.com]
>> Skickat: den 21 juli 2011 07:08
>> Till: ADSM-L@VM.MARIST.EDU
>> Ämne: TSM 61 upgradation error...
>>
>> Hi,
>>
>>
>>
>> Iam getting the following error when I trying to upgrade my existing TSM
>> 5.5.2 to TSM6.1
>>
>>
>>
>> ACUINI0029E The install version, $(acu.compatibleVersions), is not valid.
>>
>> Failed to initialize DE Engine
>>
>>
>>
>> Please suggest.
>>
>>
>>
>> Regards,
>>
>> Kiran.
>>
>> Disclaimer:
>> This email message (including attachments if any) may contain privileged,
>> proprietary, confidential information, which may be exempt from any kind of
>> disclosure whatsoever and is intended solely for the use of addressee (s).
>> If you are not the intended recipient, kindly inform us by return e-mail and
>> also kindly disregard the contents of the e-mail, delete the original
>> message and destroy any copies thereof immediately. You are notified that
>> any dissemination, distribution or copying of this communication is strictly
>> prohibited unless approved by the sender.
>>
>> DQ Entertainment (DQE) has taken every reasonable precaution to minimize
>> the risk of transmission of computer viruses with this e-mail; DQE is not
>> liable for any damage you may sustain as a result of any virus in this
>> e-mail. DQE shall not be liable for the views expressed in the e-mail. DQE
>> reserves the right to monitor and review the content of all messages sent to
>> or from this e-mail address
>>
>
>
>
> --
> Thanks & Regards,
> Sarav
> Mobile: +974-3344-1538
> Email: evergreen.sa...@gmail.com, 
> evergreen.sa...@yahoo.co.in
> http://qa.linkedin.com/pub/saravanan-palanisamy/36/584/482
>
> There are no secrets to success. It is the result of preparation, hard work
> and learning from failure - Colin Powell
>
>


-- 
Thanks & Regards,
Sarav
Mobile: +974-3344-1538
Email: evergreen.sa...@gmail.com, 
evergreen.sa...@yahoo.co.in
http://qa.linkedin.com/pub/saravanan-palanisamy/36/584/482

There are no secrets to success. It is the result of preparation, hard work
and learning from failure - Colin Powell


Re: SV: TSM 61 upgradation error...

2011-07-21 Thread Saravanan Palanisamy
what error you are looking in log file /var/tivoli/tsm/log.txt ?

On Thu, Jul 21, 2011 at 8:19 AM, Christian Svensson <
christian.svens...@cristie.se> wrote:

> When do you get the problem and what OS are you running?
> I sow on a Windows system where I needed to delete the installation
> software directory between each upgrade step.
>
> /Christian
>
> -Ursprungligt meddelande-
> Från: Kiran [mailto:ki...@dqentertainment.com]
> Skickat: den 21 juli 2011 07:08
> Till: ADSM-L@VM.MARIST.EDU
> Ämne: TSM 61 upgradation error...
>
> Hi,
>
>
>
> Iam getting the following error when I trying to upgrade my existing TSM
> 5.5.2 to TSM6.1
>
>
>
> ACUINI0029E The install version, $(acu.compatibleVersions), is not valid.
>
> Failed to initialize DE Engine
>
>
>
> Please suggest.
>
>
>
> Regards,
>
> Kiran.
>
> Disclaimer:
> This email message (including attachments if any) may contain privileged,
> proprietary, confidential information, which may be exempt from any kind of
> disclosure whatsoever and is intended solely for the use of addressee (s).
> If you are not the intended recipient, kindly inform us by return e-mail and
> also kindly disregard the contents of the e-mail, delete the original
> message and destroy any copies thereof immediately. You are notified that
> any dissemination, distribution or copying of this communication is strictly
> prohibited unless approved by the sender.
>
> DQ Entertainment (DQE) has taken every reasonable precaution to minimize
> the risk of transmission of computer viruses with this e-mail; DQE is not
> liable for any damage you may sustain as a result of any virus in this
> e-mail. DQE shall not be liable for the views expressed in the e-mail. DQE
> reserves the right to monitor and review the content of all messages sent to
> or from this e-mail address
>



-- 
Thanks & Regards,
Sarav
Mobile: +974-3344-1538
Email: evergreen.sa...@gmail.com, 
evergreen.sa...@yahoo.co.in
http://qa.linkedin.com/pub/saravanan-palanisamy/36/584/482

There are no secrets to success. It is the result of preparation, hard work
and learning from failure - Colin Powell


Re: volumes associated with a node

2011-06-29 Thread Saravanan Palanisamy
select volume_name from contents where node_name like '%nodename%' and
FILESPACE_NAME like '%Filespacename%' and FILE_NAME like '%Filename%'

On Wed, Jun 29, 2011 at 3:48 PM, molin gregory wrote:

> Hello,
>
> Try : q nodedata NODENAME stg=
>
> Cordialement,
> Grégory Molin
> Tel : 0141628162
> gregory.mo...@afnor.org
>
> -Message d'origine-
> De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de
> Tim Brown
> Envoyé : mercredi 29 juin 2011 14:40
> À : ADSM-L@VM.MARIST.EDU
> Objet : [ADSM-L] volumes associated with a node
>
> Is there a select statement that will list all tape volumes that have files
> for
>
> a given TSM node.
>
>
>
> Thanks,
>
>
>
> Tim Brown
> Systems Specialist - Project Leader
> Central Hudson Gas & Electric
> 284 South Ave
> Poughkeepsie, NY 12601
> Email: tbr...@cenhud.com <>
> Phone: 845-486-5643
> Fax: 845-486-5921
> Cell: 845-235-4255
>
>
>
>
> This message contains confidential information and is only for the intended
> recipient. If the reader of this message is not the intended recipient, or
> an employee or agent responsible for delivering this message to the intended
> recipient, please notify the sender immediately by replying to this note and
> deleting all copies and attachments.
>
> "ATTENTION.
>
> Ce message et les pièces jointes sont confidentiels et établis à
> l'attention exclusive de leur destinataire (aux adresses spécifiques
> auxquelles il a été adressé). Si vous n'êtes pas le destinataire de ce
> message, vous devez immédiatement en avertir l'expéditeur et supprimer ce
> message et les pièces jointes de votre système.
>
> This message and any attachments are confidential and intended to be
> received only by the addressee. If you are not the intended recipient,
> please notify immediately the sender by reply and delete the message and any
> attachments from your system. "
>



-- 
Thanks & Regards,
Sarav
+974-3344-1538

There are no secrets to success. It is the result of preparation, hard work
and learning from failure - Colin Powell


Re: Lan-free backup doesn't work!

2011-06-27 Thread Saravanan Palanisamy
Hi Stkr34,

Step1:

Add the below lines into dsm.sys file.
lanfreecommmethod tcpip
lanfreetcpserveraddress hostname
lanfreetcpport 1500
nodename nodename

Start the storage agent in the background using the below command
 Step 2:

/opt/tivoli/tsm/StorageAgent/bin/fdsmsta &
Step 3:

try some test backup thru ba client.

dsmc inc /opt/tivoli/tsm/client/ba/bin/dsm.sys

Step4:

search the activity log for the below string

q act se=proxied*by begind=-1

check whether any session proxied for storage agent node. Also do validate
using the below command

validate lanfree nodename storageagent


On Mon, Jun 27, 2011 at 1:14 PM, stkr34  wrote:

> Hello,
> Im new here and I'm not TSM admin. But, maybe someone  help me about lan
> free backup problem. The problem is I couldn't see my server on TSM lanfree
> list.  when I command q ses I can not see Proxy By Storage Agent.
> How can I restart storage agent on linux?
>
> Thanks,
> Stkr34
>
> +--
> |This was sent by suat@eczacibasi.com.tr via Backup Central.
> |Forward SPAM to ab...@backupcentral.com.
> +--
>



--
Thanks & Regards,
Sarav
+974-3344-1538

There are no secrets to success. It is the result of preparation, hard work
and learning from failure - Colin Powell


Re: Updgarde issues from TSM 6.2 to 6.2.2.30 on AIX 6.1

2011-06-22 Thread Saravanan Palanisamy
It seems you don't have any problem with db2 license...you are having
issues with TSM server license..

what error message you have seen in db2diag.log during server startup...




On Wed, Jun 22, 2011 at 10:55 PM, Abid Ilias  wrote:

> Here the output.
>
>
> $ db2licm -l
> Product name: "DB2 Enterprise Server Edition"
> License type: "Restricted"
> Expiry date:  "Permanent"
> Product identifier:   "db2ese"
> Version information:  "9.7"
>
> Thanks
> Abid
>
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of
> Carlo Zanelli
> Sent: Wednesday, June 22, 2011 2:44 PM
> To: ADSM-L@vm.marist.edu
> Subject: Re: [ADSM-L] Updgarde issues from TSM 6.2 to 6.2.2.30 on AIX 6.1
>
> Could you please run
>
> db2licm -l
>
> and report the output.
>
> 10x
>
> Carlo.
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
> Abid Ilias
> Sent: mercoledì 22 giugno 2011 21:33
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] Updgarde issues from TSM 6.2 to 6.2.2.30 on AIX 6.1
>
> Hello Carlo,
>
> Answers are below...
>
> Thanks
> Abid Ilias
> Storage Systems Administrator
> IT Services - University of Chicago
> Work: 773-702-0246
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of
> Carlo Zanelli
> Sent: Wednesday, June 22, 2011 2:13 PM
> To: ADSM-L@vm.marist.edu
> Subject: Re: [ADSM-L] Updgarde issues from TSM 6.2 to 6.2.2.30 on AIX 6.1
>
> Hi Abid,
>
>
>
> too few informations to give you some help.
>
>
>
> a)What is the OS/Version?
> AIX 6100-06-05-1115
>
> b) Is the TSM in cluster?
> No
>
> c) If so, is it in HACMP?
> No
>
> d)Wath are  the steps you have done for the upgrading?
> Our AIX admin ran the install.bin, here the out put from lslpp -l|grep TSM
>
> tivoli.tsm.server 6.2.2.30  COMMITTED  TSM Server
> 6.2.1.0  COMMITTED  TSM Server License
> 6.2.1.0  COMMITTED  TSM Server License Runtime
>6.2.2.30  COMMITTED  TSM Server Messages, locale
>  tivoli.tsm.server 6.2.2.30  COMMITTED  TSM Server
>
> e)Have you recataloged the db2 ?
> No
>
>
>
> Kindly,
>
> Carlo.
>
>
>
>
>
>
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
> Abid Ilias
> Sent: mercoledì 22 giugno 2011 21:03
> To: ADSM-L@VM.MARIST.EDU
> Subject: [ADSM-L] Updgarde issues from TSM 6.2 to 6.2.2.30 on AIX 6.1
>
>
>
> We have up upgraded TSM from 6.2 to 6.2.2.30 and are not able to start the
> server.  I have a PMR open with IBM, checking to see if someone has
> encountered this.  Any thoughts and suggestions would be appreciated.
>
>
>
>
>
> $ dsmserv
>
> ANR7800I DSMSERV generated at 17:54:46 on Apr 15 2011.
>
>
>
> Tivoli Storage Manager for AIX
>
> Version 6, Release 2, Level 2.30
>
>
>
> Licensed Materials - Property of IBM
>
>
>
> (C) Copyright IBM Corporation 1990, 2010.
>
> All rights reserved.
>
> U.S. Government Users Restricted Rights - Use, duplication or disclosure
> restricted by GSA ADP Schedule Contract with IBM Corporation.
>
>
>
> ANR7801I Subsystem process ID is 5963934.
>
> ANR0900I Processing options file /home/stagg/tsminst1/dsmserv.opt.
>
> ANR7811I Using instance directory /home/stagg/tsminst1.
>
> ANR4726I The ICC support module has been loaded.
>
> ANR0990I Server restart-recovery in progress.
>
> ANR0151W Failure starting database manager.
>
> ANR0279S The database manager failed to start. The database manager license
> key is invalid or was removed.
>
>
>
>
>
>
>
> Regards
>
> Abid
>
>
> -
> Ai sensi del D.Lgs. 196/2003 si precisa che le informazioni contenute nel
> messaggio e negli eventuali allegati sono riservate al/ai destinatario/i
> indicato/i. Nel caso di erroneo recapito, si chiede cortesemente a chi legge
> di dare immediata comunicazione al mittente e di cancellare il presente
> messaggio e gli eventuali allegati. Si invita ad astenersi dall'effettuare:
> inoltri, copie, distribuzioni e divulgazioni non autorizzate del presente
> messaggio e degli eventuali allegati.
>
> --
> According to Italian law (D.Lgs 196/2003) information contained in this
> message and any attachment contained therein is addressed exclusively to the
> intended recipient. If you have received this message in error would you
> please inform immediately the sender and delete the message and its
> attachments. You are also requested not to make copies, nor to forward the
> message and its attachments or disclose their content unless authorised.
>
> -
> Ai sensi del D.Lgs. 196/2003 si precisa che le informazioni contenute nel
> messaggio e negli eventuali allegati sono riservate al/ai destinatario/i
> indicato/i. Nel caso di erroneo recapito, si chiede cortesemente a chi legge
> di dare immediata comunicazione al mittente e di cancell

Re: Updgarde issues from TSM 6.2 to 6.2.2.30 on AIX 6.1

2011-06-22 Thread Saravanan Palanisamy
Hi,

Please check ur license for db2 database.

db2licm -l
Product name: "DB2 Enterprise Server Edition"
License type: "Restricted"
Expiry date:  "Permanent"
Product identifier:   "db2ese"
Version information:  "9.7"

if you don't find then search the license files

find / -name db2ese.lic

find / -name db2so.lic


db2licm -a db2ese.lic

LIC1402I  License added successfully.

LIC1426I  This product is now licensed for use as outlined in your License
Agree
ment.  USE OF THE PRODUCT CONSTITUTES ACCEPTANCE OF THE TERMS OF THE IBM
LICENSE
 AGREEMENT, LOCATED IN THE FOLLOWING DIRECTORY:
"C:\PROGRA~1\Tivoli\TSM\db2\lice
nse\en"

db2licm -a db2so.lic
LIC1402I  License added successfully.

LIC1426I  This product is now licensed for use as outlined in your License
Agree
ment.  USE OF THE PRODUCT CONSTITUTES ACCEPTANCE OF THE TERMS OF THE IBM
LICENSE
 AGREEMENT, LOCATED IN THE FOLLOWING DIRECTORY:
"C:\PROGRA~1\Tivoli\TSM\db2\lice
nse\en"

On Wed, Jun 22, 2011 at 10:43 PM, Andrew Carlson wrote:

> We had to recatlog the database after an upgrade from 6.2.2.0 to I
> think it was 6.2.2.2 - I have a doc with the instructions, but I can't
> get access to it from home for some readon :(
>
> On Wed, Jun 22, 2011 at 14:32, Abid Ilias  wrote:
> > Hello Carlo,
> >
> > Answers are below...
> >
> > Thanks
> > Abid Ilias
> > Storage Systems Administrator
> > IT Services - University of Chicago
> > Work: 773-702-0246
> >
> > -Original Message-
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of
> Carlo Zanelli
> > Sent: Wednesday, June 22, 2011 2:13 PM
> > To: ADSM-L@vm.marist.edu
> > Subject: Re: [ADSM-L] Updgarde issues from TSM 6.2 to 6.2.2.30 on AIX 6.1
> >
> > Hi Abid,
> >
> >
> >
> > too few informations to give you some help.
> >
> >
> >
> > a)What is the OS/Version?
> > AIX 6100-06-05-1115
> >
> > b) Is the TSM in cluster?
> > No
> >
> > c) If so, is it in HACMP?
> > No
> >
> > d)Wath are  the steps you have done for the upgrading?
> > Our AIX admin ran the install.bin, here the out put from lslpp -l|grep
> TSM
> >
> > tivoli.tsm.server 6.2.2.30  COMMITTED  TSM Server
> > 6.2.1.0  COMMITTED  TSM Server License
> > 6.2.1.0  COMMITTED  TSM Server License
> Runtime
> >6.2.2.30  COMMITTED  TSM Server Messages,
> locale
> >  tivoli.tsm.server 6.2.2.30  COMMITTED  TSM Server
> >
> > e)Have you recataloged the db2 ?
> > No
> >
> >
> >
> > Kindly,
> >
> > Carlo.
> >
> >
> >
> >
> >
> >
> >
> > -Original Message-
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
> Abid Ilias
> > Sent: mercoledì 22 giugno 2011 21:03
> > To: ADSM-L@VM.MARIST.EDU
> > Subject: [ADSM-L] Updgarde issues from TSM 6.2 to 6.2.2.30 on AIX 6.1
> >
> >
> >
> > We have up upgraded TSM from 6.2 to 6.2.2.30 and are not able to start
> the server.  I have a PMR open with IBM, checking to see if someone has
> encountered this.  Any thoughts and suggestions would be appreciated.
> >
> >
> >
> >
> >
> > $ dsmserv
> >
> > ANR7800I DSMSERV generated at 17:54:46 on Apr 15 2011.
> >
> >
> >
> > Tivoli Storage Manager for AIX
> >
> > Version 6, Release 2, Level 2.30
> >
> >
> >
> > Licensed Materials - Property of IBM
> >
> >
> >
> > (C) Copyright IBM Corporation 1990, 2010.
> >
> > All rights reserved.
> >
> > U.S. Government Users Restricted Rights - Use, duplication or disclosure
> restricted by GSA ADP Schedule Contract with IBM Corporation.
> >
> >
> >
> > ANR7801I Subsystem process ID is 5963934.
> >
> > ANR0900I Processing options file /home/stagg/tsminst1/dsmserv.opt.
> >
> > ANR7811I Using instance directory /home/stagg/tsminst1.
> >
> > ANR4726I The ICC support module has been loaded.
> >
> > ANR0990I Server restart-recovery in progress.
> >
> > ANR0151W Failure starting database manager.
> >
> > ANR0279S The database manager failed to start. The database manager
> license key is invalid or was removed.
> >
> >
> >
> >
> >
> >
> >
> > Regards
> >
> > Abid
> >
> >
> > -
> > Ai sensi del D.Lgs. 196/2003 si precisa che le informazioni contenute nel
> messaggio e negli eventuali allegati sono riservate al/ai destinatario/i
> indicato/i. Nel caso di erroneo recapito, si chiede cortesemente a chi legge
> di dare immediata comunicazione al mittente e di cancellare il presente
> messaggio e gli eventuali allegati. Si invita ad astenersi dall'effettuare:
> inoltri, copie, distribuzioni e divulgazioni non autorizzate del presente
> messaggio e degli eventuali allegati.
> >
> > --
> > According to Italian law (D.Lgs 196/2003) information contained in this
> message and any attachment contained therein is addressed exclusively to the
> intended recipient. If you have received this message in error would you
> please inform immediately the sender and delete the message and its
> attachments. You are also requested 

Re: preview incremental backup?

2011-06-09 Thread Saravanan Palanisamy
this command will do the previewbut it's only supported in TSM
6.x BA clients

http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp?topic=/com.ibm.itsm.client.doc/r_opt_querysummary.html

dsmc query backup /usr/ -subdir=yes -querysummary...

On Thu, Jun 9, 2011 at 8:16 PM, Keith Arbogast  wrote:

> My age is a closely guarded secret, until days like this.
> K.
>



--
Thanks & Regards,
Sarav
+974-3344-1538

There are no secrets to success. It is the result of preparation, hard work
and learning from failure - Colin Powell