Re: Database restore and containerpools

[Loon, Eric van (ITOPT3) - KLM]

Hi Stefan!
I think too this is the way to do it, but I prefer to have an 'official' 
confirmation from IBM (Del?). IBM might have to correct the manual too than, 
because an audit of a container that is not in the database doesn't seem to 
work...
Kind regards,
Eric van Loon
Air France/KLM Storage Engineering

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Stefan 
Folkerts
Sent: donderdag 3 augustus 2017 19:50
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Database restore and containerpools

Hi Eric,

I've been in this situation before a while back and what I did was about the 
same, I did a query container from a for loop based on the output from the find 
command on the filesytems I believe and every container I did not find in 
Spectrum protect was deleted (rc != 0 on the dsmadmc q container) was deleted 
on the filesystem by hand, I double checked everything.





On Thu, Aug 3, 2017 at 3:14 PM, Loon, Eric van (ITOPT3) - KLM < 
eric-van.l...@klm.com> wrote:

> Hi all,
> I'm working on a procedure on how to handle a TSM server (with a 
> container
> pool) when a database is restored to the latest backup. When you do 
> this, you might end up with containers which were created after the 
> last backup and which are not known to the TSM server because they 
> were not yet created at the time of the last backup.
> In my case all containers are located in subdirectories in 
> /tech/tsm/server, I use the following command to count them:
>
> find /tech/tsm/server/container* -type f|wc -l
>
> and then I use this command to count the amount of containers in TSM:
>
> select count(*) from containers
>
> The amount should be the same. If there are more files on the local 
> filesystem than in TSM, these are obsolete and should be removed. The 
> SP manual (chapter Recovery from data loss outages) suggests to use 
> the audit container  action=removedamaged to delete 
> the container, but that doesn't seem to work.  To test this I copied a 
> container to a temp file on the local filesystem, moved the source 
> container to a new one in TSM (temporarily set reusedelay=0) and as 
> soon as the source file was gone, renamed the temp file to the same 
> name as the source file. As soon as I audit it, it is not being removed:
>
> ANR2017I Administrator ADMIN command: AUDIT CONTAINER 
> /tech/tsm/server/container00/01/01c7.dcf 
> action=removedamaged ANR3710I This command will delete container 
> /tech/tsm/server/container00/01/01c7.dcf
> from the file system.
> ANR3711E Container 
> /tech/tsm/server/container00/01/01c7.dcf
> will not be removed from the file system.
> ANR2017I Administrator ADMIN issued command: ROLLBACK
>
> The message ANR3711E seems to indicate that the header could not be 
> validated...
>
> What should be the right procedure to handle such a situation then? 
> Just delete the obsolete containers manually?
> Thanks for any help in advance!
> Kind regards,
> Eric van Loon
> Air France/KLM Storage Engineering
> 
> 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
> 
>

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 

Re: Database restore and containerpools

[Stefan Folkerts]

Hi Eric,

I've been in this situation before a while back and what I did was about
the same, I did a query container from a for loop based on the output from
the find command on the filesytems I believe and every container I did not
find in Spectrum protect was deleted (rc != 0 on the dsmadmc q container)
was deleted on the filesystem by hand, I double checked everything.





On Thu, Aug 3, 2017 at 3:14 PM, Loon, Eric van (ITOPT3) - KLM <
eric-van.l...@klm.com> wrote:

> Hi all,
> I'm working on a procedure on how to handle a TSM server (with a container
> pool) when a database is restored to the latest backup. When you do this,
> you might end up with containers which were created after the last backup
> and which are not known to the TSM server because they were not yet created
> at the time of the last backup.
> In my case all containers are located in subdirectories in
> /tech/tsm/server, I use the following command to count them:
>
> find /tech/tsm/server/container* -type f|wc -l
>
> and then I use this command to count the amount of containers in TSM:
>
> select count(*) from containers
>
> The amount should be the same. If there are more files on the local
> filesystem than in TSM, these are obsolete and should be removed. The SP
> manual (chapter Recovery from data loss outages) suggests to use the audit
> container  action=removedamaged to delete the container,
> but that doesn't seem to work.  To test this I copied a container to a temp
> file on the local filesystem, moved the source container to a new one in
> TSM (temporarily set reusedelay=0) and as soon as the source file was gone,
> renamed the temp file to the same name as the source file. As soon as I
> audit it, it is not being removed:
>
> ANR2017I Administrator ADMIN command: AUDIT CONTAINER
> /tech/tsm/server/container00/01/01c7.dcf action=removedamaged
> ANR3710I This command will delete container 
> /tech/tsm/server/container00/01/01c7.dcf
> from the file system.
> ANR3711E Container /tech/tsm/server/container00/01/01c7.dcf
> will not be removed from the file system.
> ANR2017I Administrator ADMIN issued command: ROLLBACK
>
> The message ANR3711E seems to indicate that the header could not be
> validated...
>
> What should be the right procedure to handle such a situation then? Just
> delete the obsolete containers manually?
> Thanks for any help in advance!
> Kind regards,
> Eric van Loon
> Air France/KLM Storage Engineering
> 
> 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
> 
>

Database restore and containerpools

[Loon, Eric van (ITOPT3) - KLM]

Hi all,
I'm working on a procedure on how to handle a TSM server (with a container 
pool) when a database is restored to the latest backup. When you do this, you 
might end up with containers which were created after the last backup and which 
are not known to the TSM server because they were not yet created at the time 
of the last backup.
In my case all containers are located in subdirectories in /tech/tsm/server, I 
use the following command to count them:

find /tech/tsm/server/container* -type f|wc -l

and then I use this command to count the amount of containers in TSM:

select count(*) from containers

The amount should be the same. If there are more files on the local filesystem 
than in TSM, these are obsolete and should be removed. The SP manual (chapter 
Recovery from data loss outages) suggests to use the audit container 
 action=removedamaged to delete the container, but that doesn't 
seem to work.  To test this I copied a container to a temp file on the local 
filesystem, moved the source container to a new one in TSM (temporarily set 
reusedelay=0) and as soon as the source file was gone, renamed the temp file to 
the same name as the source file. As soon as I audit it, it is not being 
removed:

ANR2017I Administrator ADMIN command: AUDIT CONTAINER 
/tech/tsm/server/container00/01/01c7.dcf action=removedamaged
ANR3710I This command will delete container 
/tech/tsm/server/container00/01/01c7.dcf from the file system.
ANR3711E Container /tech/tsm/server/container00/01/01c7.dcf will 
not be removed from the file system.
ANR2017I Administrator ADMIN issued command: ROLLBACK

The message ANR3711E seems to indicate that the header could not be validated...

What should be the right procedure to handle such a situation then? Just delete 
the obsolete containers manually?
Thanks for any help in advance!
Kind regards,
Eric van Loon
Air France/KLM Storage Engineering

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: 2 nics on tsm server.

[Bo Nielsen]

I've solved my problem. When I disabled the firewall on my TSM server, it 
worked.

Thanks, for all the replies.

Regards

Bo
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Sasa 
Drnjevic
Sent: 27. juli 2017 12:20
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] 2 nics on tsm server.

On 27.7.2017. 12:11, Bo Nielsen wrote:
> Hi
>
> I can't telnet. telnet: command not found


http://www.sysprobs.com/install-and-enable-telnet-in-windows-8-use-as-telnet-client

--








>
> Arp:
>
> Interface: 192.168.1.11 --- 0x17
>   Internet Address  Physical Address  Type
>   192.168.1.21  00-e0-ed-24-97-af dynamic
>   192.168.1.255 ff-ff-ff-ff-ff-ff static
>
> Regards
>
> Bo
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
> Schneck, Dennis 
> Sent: 27. juli 2017 11:54
> To: ADSM-L@VM.MARIST.EDU
> Subject: [ADSM-L] AW: [ADSM-L] 2 nics on tsm server.
>
> Hi,
>
> can you connecttelnet  1500 for example
>
> you should see:
>
> Connected to .
> Escape character is '^]'.
>
>
> 
> Von: ADSM: Dist Stor Manager [ADSM-L@vm.marist.edu]" im Auftrag von 
> "Bo Nielsen [boa...@dtu.dk]
> Gesendet: Donnerstag, 27. Juli 2017 11:50
> An: ADSM-L@vm.marist.edu
> Betreff: Re: [ADSM-L] 2 nics on tsm server.
>
> Hi,
>
> I can ping from both servers.
> There isn't routing. It's a direct connection between the two servers.
>
> Regards,
>
> Bo
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
> Karel Bos
> Sent: 27. juli 2017 11:27
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] 2 nics on tsm server.
>
> Hi,
>
>
> Start with the basics, OS tools like ping. You probably have no static route 
> to this new/seperate network.
>
> Kind regards,
>
> Karel
>
> -Oorspronkelijk bericht-
> Van: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Namens Bo Nielsen
> Verzonden: donderdag 27 juli 2017 11:10
> Aan: ADSM-L@VM.MARIST.EDU
> Onderwerp: [ADSM-L] 2 nics on tsm server.
>
> Hi TSM's
>
> I have recently added one more NIC to my TSM server.
> The new NIC is connected directly to the server, for which archiving is 
> required.
> From DSM.SYS on the archiving server, who is a RHEL:
>COMMmethod TCPip
>TCPPort1500
>TCPServeraddress  192.168.1.11
>tcpclientaddress  192.168.1.21
>
> The TSM server is a W2K12 R2 and the TSM vers. 7.1.4.1.
>
> When I try to start DSMC, I get this error:
> 27/07/17   10:15:04 ANS5216E Could not establish a TCP/IP connection with
> address '192.168.1.11:1500'. The TCP/IP error is 'Connection timed out'
> (errno = 110).
> 27/07/17   10:15:04 ANS9020E A session could not be established with a TSM
> server or client agent.  The return code is -50.
> 27/07/17   10:15:04 ANS1017E Session rejected: TCP/IP connection failure.
>
> From NETSTAT on TSM server server:
> TCP0.0.0.0:1500   AIT-PTSM03:0   LISTENING
> TCP192.168.1.11:139   AIT-PTSM03:0   LISTENING
> TCP192.168.1.11:63177 192.168.1.21:ssh   ESTABLISHED
>
> The firewall is disabled for now.
>
> Pls, help!! I've search the internet.
>
> Regards,
>
> Bo Nielsen
>
>
> IT Service
>
>
>
> Technical University of Denmark
>
> IT Service
>
> Frederiksborgvej 399
>
> Building 109
>
> DK - 4000 Roskilde
>
> Denmark
>
> Mobil +45 2337 0271
>
> boa...@dtu.dk
>
>
> ---
> Dit e-mailbericht is gecontroleerd op virussen met Avast antivirussoftware.
> https://www.avast.com/antivirus
>