Re: Query regarding IBM Spectrum Suite support renewal

[Vandeventer, Harold [OITS]]

We are doing the same as you, switching to an alternate solution.

We were told by our IBM representative that the LICENSE to use the software was 
still in place after the end date of the contract.

The only thing lost is the ability to get technical support through the IBM 
ticketing system.  That date corresponds to the end-date of your support 
contract.


-Original Message-
From: ADSM: Dist Stor Manager  On Behalf Of DUDLEY Paul
Sent: Tuesday, May 14, 2019 8:01 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Query regarding IBM Spectrum Suite support renewal

EXTERNAL: This email originated from outside of the organization. Do not click 
any links or open any attachments unless you trust the sender and know the 
content is safe.


We are moving away from TSM/Spectrum in the coming months. Our annual IBM 
Spectrum Protect Suite Terabyte annual software subscription and support 
renewal is due however we are looking to not renew it as we will soon be 
backing up our servers using a different product. We have been advised in 
writing (email) by our IBM renewals specialist that we will still be able to 
use the TSM software once the current software subscription and support 
contract expires. Has anyone else had experience with this and confirm it is 
correct?


Regards
Paul Dudley
pdud...@anl.com.au


CONFIDENTIALITY AND PRIVILEGE NOTICE
This e-mail message, including attachments, if any, is intended for the person 
or entity to which it is addressed and may contain confidential or privileged 
information. Any unauthorized review, use, or disclosure is prohibited. If you 
are not the intended recipient, please contact the sender and destroy the 
original message, including all copies, Thank you.

Re: Bottomless pit

[Vandeventer, Harold [OITS]]

You're seeing the same issue I've seen.

Q OCCUP values for SystemState seem to have no relationship to the number that 
are eventually deleted.

The value on Q OCCUP is always much lower than what is reported in Q PRO.

And, deleting system state takes a LONG time.

-Original Message-
From: ADSM: Dist Stor Manager  On Behalf Of Zoltan Forray
Sent: Monday, February 25, 2019 1:05 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Bottomless pit

EXTERNAL: This email originated from outside of the organization. Do not click 
any links or open any attachments unless you trust the sender and know the 
content is safe.


Here is a new one...

We turned off backing up SystemState last week.  Now I am going through and 
deleted the Systemstate filesystems.

Since I wanted to see how many objects would be deleted, I did a "Q OCCUPANCY" 
and preserved the file count numbers for all Windows nodes on this server.

For 4-nodes, the delete of their systemstate filespaces has been running for 
5-hours. A "Q PROC" shows:

2019-02-25 08:52:05 Deleting file space
ORION-POLL-WEST\SystemState\NULL\System State\SystemState (fsId=1) (backup
data) for node ORION-POLL-WEST: *105,511,859 objects deleted*.

Considering the occupancy for this node was *~5-Million objects*, how has it 
deleted *105-Million* objects (and counting).  The other 3-nodes in question 
are also up to *>100-Million objects deleted* and none of them had more than 
*6M objects* in occupancy?

At this rate, the deleting objects count for 4-nodes systemstate will exceed 
50% of the total occupancy objects on this server that houses the backups for* 
263-nodes*?

I vaguely remember some bug/APAR about systemstate backups being 
large/slow/causing performance problems with expiration but these nodes client 
levels are fairly current (8.1.0.2 - staying below the 8.1.2/SSL/TLS 
enforcement levels) and the ISP server is 7.1.7.400.  All of these are Windows 
2016, if that matters.

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


CONFIDENTIALITY AND PRIVILEGE NOTICE
This e-mail message, including attachments, if any, is intended for the person 
or entity to which it is addressed and may contain confidential or privileged 
information. Any unauthorized review, use, or disclosure is prohibited. If you 
are not the intended recipient, please contact the sender and destroy the 
original message, including all copies, Thank you.

Re: Windows ARL change

[Vandeventer, Harold [OITS]]

; revert to the Day 1 backup, assuming your copygroup retention settings

have

> > not caused the older backup to expire.

> >

> >

> > 2. If you later decide to put this option back to its default

> > (SKIPNTSECURITYCRC NO) then you might see a one-time very big backup,

> > because at that time, any files whose change is only to security, will

be

> > backed up, resulting possibly in a backup workload that is larger than

> > usual.

> >

> > In sum: Best practice to ensure most complete incremental backup is to

> > allow the data to be backed up, even if only the security has changed.

> > Proceed with caution, thinking about future ramifications of using this

> > option.

> >

> > Best regards,

> >

> > Andy

> >

> >





> >

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

> >

> > "ADSM: Dist Stor Manager"  wrote on 2018-10-30

> > 14:57:47:

> >

> >> From: Robert Talda 

> >> To: ADSM-L@VM.MARIST.EDU

> >> Date: 2018-10-30 14:58

> >> Subject: Re: Windows ARL change

> >> Sent by: "ADSM: Dist Stor Manager" 

> >>

> >> Harold:

> >>  Have same issue - often several times a year as departments here

> >> administer their own servers - and no magic bullet.  Probably

> >> doesn’t help other than “misery loves company”

> >>

> >>  Keeping fingers crossed someone smarter than I has a workaround,

> >> Bob

> >>

> >> Robert Talda

> >> EZ-Backup Systems Engineer

> >> Cornell University

> >> +1 607-255-8280

> >> r...@cornell.edu

> >>

> >>

> >>> On Oct 30, 2018, at 11:20 AM, Vandeventer, Harold [OITS]

> >>  wrote:

> >>>

> >>> Our "server security" folks are making several changes in Windows

> >> Access Rights at the top of a folder structure which then cascades

> >> all the way down to all files.  This is being done on several nodes.

> >>>

> >>> Is there a way to avoid Spectrum Protect from backing up all those

> >> files, most of which haven't changed in content other than the ARL

> > property?

> >>>

> >>> We charge back to agencies based on the bytes in auditocc table.

> >> The ARL change results in a double up of the cost.

> >>>

> >>> The nodes are running various 7.x versions.

> >>>

> >>> Thanks for any guidance you might have.

> >>>

> >>

>



CONFIDENTIALITY AND PRIVILEGE NOTICE
This e-mail message, including attachments, if any, is intended for the person 
or entity to which it is addressed and may contain confidential or privileged 
information. Any unauthorized review, use, or disclosure is prohibited. If you 
are not the intended recipient, please contact the sender and destroy the 
original message, including all copies, Thank you.

Windows ARL change

[Vandeventer, Harold [OITS]]

Our "server security" folks are making several changes in Windows Access Rights 
at the top of a folder structure which then cascades all the way down to all 
files.  This is being done on several nodes.

Is there a way to avoid Spectrum Protect from backing up all those files, most 
of which haven't changed in content other than the ARL property?

We charge back to agencies based on the bytes in auditocc table. The ARL change 
results in a double up of the cost.

The nodes are running various 7.x versions.

Thanks for any guidance you might have.


Harold Vandeventer
Office of Information Technology Services
(785) 296-4999
harold.vandeven...@ks.gov | 
www.oits.ks.gov



CONFIDENTIALITY AND PRIVILEGE NOTICE
This email message including attachments, if any, is intended for the person or 
entity to which it is addressed and may contain confidential and/or privileged 
information. Any unauthorized review, use or disclosure is prohibited. If you 
are not the intended recipient, please contact the sender and destroy the 
original message, including all copies.




CONFIDENTIALITY AND PRIVILEGE NOTICE
This e-mail message, including attachments, if any, is intended for the person 
or entity to which it is addressed and may contain confidential or privileged 
information. Any unauthorized review, use, or disclosure is prohibited. If you 
are not the intended recipient, please contact the sender and destroy the 
original message, including all copies, Thank you.

Restoring older file version

[Vandeventer, Harold [OITS]]

I have a node manager attempting to restore a previous version of a file.

The Mgmt class indicates Versions data exists: 3, Versions data deleted: 3, 
Retain extra versions 30 Days.

The file has not been deleted.
The file date is 4/20/18.
It changes "monthly" but I don't know the exact dates, probably varies from 
month to month.

Using View Active/Inactive doesn't present the previous versions.

If he picks a point in time of 4/20/18, he sees the file dated 4/20.
If he picks point in time of 4/19/19, no versions are displayed.

I would expect at least one previous version unless the "retain extra versions 
30 days" is the property allowing the file to be deleted from TSM sooner than 
expected.

The node is running on version 6.01 against an old TSM at 6.3.4.300. (I'm in an 
upgrade issue, so can't deal with that yet, or open a PMR)

For the community: is that "retain extra versions" value of 30 the issue?  It's 
allowing a file version dated 3/19 or earlier to be deleted?


Harold Vandeventer
Office of Information Technology Services
(785) 296-4999
harold.vandeven...@ks.gov | www.oits.ks.gov



CONFIDENTIALITY AND PRIVILEGE NOTICE
This email message including attachments, if any, is intended for the person or 
entity to which it is addressed and may contain confidential and/or privileged 
information. Any unauthorized review, use or disclosure is prohibited. If you 
are not the intended recipient, please contact the sender and destroy the 
original message, including all copies.




CONFIDENTIALITY AND PRIVILEGE NOTICE
This e-mail message, including attachments, if any, is intended for the person 
or entity to which it is addressed and may contain confidential or privileged 
information. Any unauthorized review, use, or disclosure is prohibited. If you 
are not the intended recipient, please contact the sender and destroy the 
original message, including all copies, Thank you.

Re: cancelling replication for a nodegroup

[Vandeventer, Harold [OITS]]

I agree, middle of the night is a problem.

I don't know of a way to cancel without knowing the PROCESS number.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Jeannie Bruno
Sent: Wednesday, April 19, 2017 7:52 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] cancelling replication for a nodegroup

Hello.  Thanks.   But if this was in the middle of the night and you didn't 
know what the process number was and I wanted to create a script and schedule 
it so to cancel that same node group at a specific time on a specific 
day..how do I find out what the process number is?


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Vandeventer, Harold [OITS]
Sent: Wednesday, April 19, 2017 8:42 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] cancelling replication for a nodegroup


** THIS IS AN EXTERNAL EMAIL ** Use caution before opening links / attachments. 
Never supply UserID/PASSWORD information.


I use CAN PRO nnn.

I believe the intent for CAN REP is to stop all of them, regardless of how many.



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Jeannie Bruno
Sent: Wednesday, April 19, 2017 7:24 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] cancelling replication for a nodegroup

Hello.  I see there is a 'cancel replication' command but it doesn't look like 
there is an option for a specific node or nodegroup.  But what if there are 
many nodegroups replicating and I want to cancel just one of them.

Anyone know of script or 'select' statement I can use to cancel a specific 
nodegroup name?
Do I need the process number first?



Jeannie Bruno
Senior Systems Analyst
jbr...@cenhud.com<mailto:jbr...@cenhud.com>
Central Hudson Gas & Electric
(845) 486-5780
We Care About Your Privacy. This message may contain confidential and/or 
privileged 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. Thank you.


CONFIDENTIALITY AND PRIVILEGE NOTICE
This e-mail message, including attachments, if any, is intended for the person 
or entity to which it is addressed and may contain confidential or privileged 
information. Any unauthorized review, use, or disclosure is prohibited. If you 
are not the intended recipient, please contact the sender and destroy the 
original message, including all copies, Thank you.

Re: cancelling replication for a nodegroup

[Vandeventer, Harold [OITS]]

I use CAN PRO nnn.

I believe the intent for CAN REP is to stop all of them, regardless of how many.



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Jeannie Bruno
Sent: Wednesday, April 19, 2017 7:24 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] cancelling replication for a nodegroup

Hello.  I see there is a 'cancel replication' command but it doesn't look like 
there is an option for a specific node or nodegroup.  But what if there are 
many nodegroups replicating and I want to cancel just one of them.

Anyone know of script or 'select' statement I can use to cancel a specific 
nodegroup name?
Do I need the process number first?



Jeannie Bruno
Senior Systems Analyst
jbr...@cenhud.com
Central Hudson Gas & Electric
(845) 486-5780
We Care About Your Privacy. This message may contain confidential and/or 
privileged 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. Thank you.


CONFIDENTIALITY AND PRIVILEGE NOTICE
This e-mail message, including attachments, if any, is intended for the person 
or entity to which it is addressed and may contain confidential or privileged 
information. Any unauthorized review, use, or disclosure is prohibited. If you 
are not the intended recipient, please contact the sender and destroy the 
original message, including all copies, Thank you.

Re: RFE: Node custom information user field

[Vandeventer, Harold [OITS]]

I agree.

You got my vote too.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Alford, Ben
Sent: Thursday, February 02, 2017 7:29 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] RFE: Node custom information user field

Conny,
Thank you!  I have just voted for this RFE.  With such a field we would be able 
to store our internal billing account number for each TSM node.
Ben Alford
University of Tennessee

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Conny 
Landstedt
Sent: Thursday, February 2, 2017 7:54 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] RFE: Node custom information user field

Hi,

I've placed an RFE for what I in short call 'Node custom information user field'
http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe_ID=98544

As described in the RFE:
A 'custom information' field is desirable where we could input information in 
any format we as a user wish. There is no custom field to use for node details. 
Only 'Contact' field is available and it is not sufficient.

The use cases are many, and as described in the RFE:
This could be used as a normal textfield or for for example a JSON string, or 
an XML string for easy integration with other systems. Sometimes we simply need 
somewhere to place some information for a particular node or for all nodes. For 
example to track who the end customer is for the node, agreement number for the 
node, or what system it belongs to. It's a free user 'custom information' field 
so the possibilities for it's use case is pretty much what we as end users can 
imagine using it for.

If you think this is a good idea please vote for it.

Best regards
Conny Landstedt


CONFIDENTIALITY AND PRIVILEGE NOTICE
This e-mail message, including attachments, if any, is intended for the person 
or entity to which it is addressed and may contain confidential or privileged 
information. Any unauthorized review, use, or disclosure is prohibited. If you 
are not the intended recipient, please contact the sender and destroy the 
original message, including all copies, Thank you.

Monitoring for Spectrum Protect

[Vandeventer, Harold [OITS]]

Is Monitoring/Reporting version 7.1.3.000 the latest available?

I've searched for a later release, but not finding anything.

I'm running 7.1.3.000, obtained from Passport Advantage.  It requires IE 8 or 
IE9.

The FTP maintenance file has the same version number.

IE 11 can't properly open the "Launch IBM Cognos Administration" link.




CONFIDENTIALITY AND PRIVILEGE NOTICE
This e-mail message, including attachments, if any, is intended for the person 
or entity to which it is addressed and may contain confidential or privileged 
information. Any unauthorized review, use, or disclosure is prohibited. If you 
are not the intended recipient, please contact the sender and destroy the 
original message, including all copies, Thank you.

Re: Fine tuning INCLUDE/EXCLUDE and EXCLUDE.DIR

[Vandeventer, Harold [OITS]]

Thanks to all for some great suggestions.

My initial addition was a simple list of EXCLUDE.DIR for each of the currently 
existing folders below J:\IMAGENOW that are not to be traversed.

That cut backup time from 24+ hours down to 15 hours.

We're running two nodes on that server, with slight changes in the dsm.opt to 
have one responsible for a given path, the other node for another path.

The manager of that server insists that new paths won't be created; we'll see 
if that's true, 'eh?  

Thanks again to everyone.



From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Neil 
Strand
Sent: Monday, August 29, 2016 1:51 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Fine tuning INCLUDE/EXCLUDE and EXCLUDE.DIR

Harold, 
   It sounds as if you need a multiplexed session solution.  You might want to 
check out dsmISI MAGS.  It is a utility that manages many simultaneous Spectrum 
Protect sessions running in parallel. 

http://www.general-storage.com/PRODUCTS/dsmISI-MAGS/dsmisi-mags.html 

Cheers, 
Neil Strand 

www.cassevern.com 
6201 Chevy Chase Drive, Laurel, MD 20707 
800.252.4715 . 301.776.3400 . Fax 301.776.3444 



From:        "Vandeventer, Harold [OITS]" <mailto:harold.vandeven...@ks.gov> 
To:        mailto:ADSM-L@VM.MARIST.EDU 
Date:        08/26/2016 02:24 PM 
Subject:        [ADSM-L] Fine tuning INCLUDE/EXCLUDE and EXCLUDE.DIR 
Sent by:        "ADSM: Dist Stor Manager" <mailto:ADSM-L@VM.MARIST.EDU> 




One of my clients has a server running ImageNow.  There are millions of files 
and several thousand folders that take over 24 hours for the daily incremental.

My goal is to backup a single ImageNow folder and reduce the elapsed time to 
traverse thousands of folders that don't need to be backed up.

We worked out a setup for a new node in an effort to backup only a given path 
within the ImageNow structure.

The following dsm.opt statements are in place:
DOMAIN J:
EXCLUDE J:\...\*
INCLUDE J:\IMAGENOW\SUBOB_OSM\...\*

That was successful in backing up only the files and subfolders/files in 
SUBOB_OSM.  But it also backed up thousands of directories on J:\.  Most of 
them are in the \IMAGENOW path.

My plan is to add a few EXCLUDE.DIR statements such as:
EXCLUDE.DIR J:\IMAGENOW\54_OSM
EXCLUDE.DIR J:\IMAGENOW\DEFAULT_OSM

The question:  will adding EXCLUDE.DIR now, after the node has backed up all 
those paths, result in a performance improvement?

I suspect Spectrum Protect server will send all the directory names to the 
node, but hopefully the work on the node side will be much faster.

Or, will we need to delete the filespace, then start over with a fresh 
"incremental forever" backup to clear out all that directory structure?

Thanks.

Harold Vandeventer
Office of Information Technology Services
2800 SW Topeka Blvd
Topeka, KS 66611
(785) 296-0631
mailto:harold.vandeven...@ks.gov | www.oits.ks.gov



CONFIDENTIALITY AND PRIVILEGE NOTICE
This email message including attachments, if any, is intended for the person or 
entity to which it is addressed and may contain confidential and/or privileged 
information. Any unauthorized review, use or disclosure is prohibited. If you 
are not the intended recipient, please contact the sender and destroy the 
original message, including all copies.



CONFIDENTIALITY AND PRIVILEGE NOTICE
This e-mail message, including attachments, if any, is intended for the person 
or entity to which it is addressed and may contain confidential or privileged 
information. Any unauthorized review, use, or disclosure is prohibited. If you 
are not the intended recipient, please contact the sender and destroy the 
original message, including all copies, Thank you.

Re: Fine tuning INCLUDE/EXCLUDE and EXCLUDE.DIR

[Vandeventer, Harold [OITS]]

Thanks Bob.  As a first update, I'll have the client add the various 
EXCLUDE.DIR statements.

I'm betting there isn't a "wildcard" just in case a new folder appears that we 
DON'T want to backup.

Thanks again.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Robert 
Talda
Sent: Friday, August 26, 2016 1:40 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Fine tuning INCLUDE/EXCLUDE and EXCLUDE.DIR

Harold:
   For what is worth, been there, done this.

  Yes, adding the EXCLUDE.DIR statements will improve backup performance - 
AFTER the first backup, during which the client will tell the server to expire 
all the files and folders that are no longer backed up.  If you delete the 
filespace first, then you avoid this performance hit - but you lose the older 
data already stored in TSM (which I’m sure you know).  We’ve let customers 
choose, because they better than we do the value of that older data..

Hope this helps
Bob


Robert Talda
EZ-Backup Systems Engineer
Cornell University
+1 607-255-8280
r...@cornell.edu


> On Aug 26, 2016, at 2:21 PM, Vandeventer, Harold [OITS] 
> <harold.vandeven...@ks.gov> wrote:
>
> One of my clients has a server running ImageNow.  There are millions of files 
> and several thousand folders that take over 24 hours for the daily 
> incremental.
>
> My goal is to backup a single ImageNow folder and reduce the elapsed time to 
> traverse thousands of folders that don't need to be backed up.
>
> We worked out a setup for a new node in an effort to backup only a given path 
> within the ImageNow structure.
>
> The following dsm.opt statements are in place:
> DOMAIN J:
> EXCLUDE J:\...\*
> INCLUDE J:\IMAGENOW\SUBOB_OSM\...\*
>
> That was successful in backing up only the files and subfolders/files in 
> SUBOB_OSM.  But it also backed up thousands of directories on J:\.  Most of 
> them are in the \IMAGENOW path.
>
> My plan is to add a few EXCLUDE.DIR statements such as:
> EXCLUDE.DIR J:\IMAGENOW\54_OSM
> EXCLUDE.DIR J:\IMAGENOW\DEFAULT_OSM
>
> The question:  will adding EXCLUDE.DIR now, after the node has backed up all 
> those paths, result in a performance improvement?
>
> I suspect Spectrum Protect server will send all the directory names to the 
> node, but hopefully the work on the node side will be much faster.
>
> Or, will we need to delete the filespace, then start over with a fresh 
> "incremental forever" backup to clear out all that directory structure?
>
> Thanks.
> 
> Harold Vandeventer
> Office of Information Technology Services
> 2800 SW Topeka Blvd
> Topeka, KS 66611
> (785) 296-0631
> harold.vandeven...@ks.gov | www.oits.ks.gov
>



CONFIDENTIALITY AND PRIVILEGE NOTICE
This e-mail message, including attachments, if any, is intended for the person 
or entity to which it is addressed and may contain confidential or privileged 
information. Any unauthorized review, use, or disclosure is prohibited. If you 
are not the intended recipient, please contact the sender and destroy the 
original message, including all copies, Thank you.

Fine tuning INCLUDE/EXCLUDE and EXCLUDE.DIR

[Vandeventer, Harold [OITS]]

One of my clients has a server running ImageNow.  There are millions of files 
and several thousand folders that take over 24 hours for the daily incremental.

My goal is to backup a single ImageNow folder and reduce the elapsed time to 
traverse thousands of folders that don't need to be backed up.

We worked out a setup for a new node in an effort to backup only a given path 
within the ImageNow structure.

The following dsm.opt statements are in place:
DOMAIN J:
EXCLUDE J:\...\*
INCLUDE J:\IMAGENOW\SUBOB_OSM\...\*

That was successful in backing up only the files and subfolders/files in 
SUBOB_OSM.  But it also backed up thousands of directories on J:\.  Most of 
them are in the \IMAGENOW path.

My plan is to add a few EXCLUDE.DIR statements such as:
EXCLUDE.DIR J:\IMAGENOW\54_OSM
EXCLUDE.DIR J:\IMAGENOW\DEFAULT_OSM

The question:  will adding EXCLUDE.DIR now, after the node has backed up all 
those paths, result in a performance improvement?

I suspect Spectrum Protect server will send all the directory names to the 
node, but hopefully the work on the node side will be much faster.

Or, will we need to delete the filespace, then start over with a fresh 
"incremental forever" backup to clear out all that directory structure?

Thanks.

Harold Vandeventer
Office of Information Technology Services
2800 SW Topeka Blvd
Topeka, KS 66611
(785) 296-0631
harold.vandeven...@ks.gov | www.oits.ks.gov



CONFIDENTIALITY AND PRIVILEGE NOTICE
This email message including attachments, if any, is intended for the person or 
entity to which it is addressed and may contain confidential and/or privileged 
information. Any unauthorized review, use or disclosure is prohibited. If you 
are not the intended recipient, please contact the sender and destroy the 
original message, including all copies.



CONFIDENTIALITY AND PRIVILEGE NOTICE
This e-mail message, including attachments, if any, is intended for the person 
or entity to which it is addressed and may contain confidential or privileged 
information. Any unauthorized review, use, or disclosure is prohibited. If you 
are not the intended recipient, please contact the sender and destroy the 
original message, including all copies, Thank you.

concurrent delete filespace?

[Vandeventer, Harold [OITS]]

Back in the TSM 5 days, I recall reading somewhere that only one delete 
filespace should be running, i.e., wait for a delete to complete before 
starting another.

Is that still the case with DB2 as the database?



Harold Vandeventer

CONFIDENTIALITY AND PRIVILEGE NOTICE
This email message including attachments, if any, is intended for the person or 
entity to which it is addressed and may contain confidential and/or privileged 
information. Any unauthorized review, use or disclosure is prohibited. If you 
are not the intended recipient, please contact the sender and destroy the 
original message, including all copies.



CONFIDENTIALITY AND PRIVILEGE NOTICE
This e-mail message, including attachments, if any, is intended for the person 
or entity to which it is addressed and may contain confidential or privileged 
information. Any unauthorized review, use, or disclosure is prohibited. If you 
are not the intended recipient, please contact the sender and destroy the 
original message, including all copies, Thank you.

Re: Node Replication Change

[Vandeventer, Harold [OITS]]

Ah, correct, I miss-read the syntax on UPDATE NODE.

Replication is already running from TSM02 to TSM01, so nothing to worry about 
there.

So, the following:
On TSM01: REMOVE REPLNODE 
On TSM02: REMOVE REPLNODE 
On TSM02: UPDATE NODE  REPLSTATE=ENABLED REPLMODE=SYNCSEND
On TSM01: UPDATE NODE  REPLSTATE=ENABLED REPLMODE=SYNCRECEIVE

Run a replication and the mode will change to SEND and RECEIVE respectively.

Thanks Efim.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Efim
Sent: Thursday, May 05, 2016 12:19 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Node Replication Change

Hi,
you can't update node with parameters:  REPLM=RECEIVE and SEND (according 
administration guide). Those parameters will set automatically after first 
replication completed.
I think the right way is remove replnode and when set REPLM=SYNCSEND for source 
and REPLM=SYNCRECEIVE for target node.
Don't forget run on TSM02: SET REPLSERVER TSM01 (if it's not already done (q 
status)).

Efim


> 5 мая 2016 г., в 19:49, Vandeventer, Harold [OITS] 
> <harold.vandeven...@ks.gov> написал(а):
> 
> I'm using Spectrum Protect 6.3.4.300 on Windows servers.
> 
> I've been running NODE replication for months, but need to make a change for 
> a node.
> 
> The current setup: Server TSM01 replicates to Server TSM02 and TSM02 
> replicates to TSM01.
> 
> The change: a node is to be "relocated" to the DR site; thus TSM02 will 
> become its main location, and will replicate back to TSM01.
> 
> No Export/Import to be done.
> 
> Thus, I believe (after reviewing the Administrator's Guide):
> 1: confirm that replication from TSM01 to TSM02 has completed.
> 2: on TSM01: UPDATE NODE  REPLM=RECEIVE
> 3: on TSM02: UPDATE NODE  REPLM=SEND
> 4: Modify the IP in the nodes DSM.OPT to point to TSM02.
> 
> I don't think SYNCREC and SYNCSEND are involved because a node EXPORT has not 
> been used to populate the data on TSM01.  The data already exists, I just 
> need to change which server is sending and which is receiving for the node.
> 
> Thanks for helping out.
> 
> 
> 
> Harold Vandeventer
> Office of Information Technology Services
> 2800 SW Topeka Blvd
> Topeka, KS 66611
> (785) 296-0631
> harold.vandeven...@ks.gov | www.oits.ks.gov
> 
> 
> 
> CONFIDENTIALITY AND PRIVILEGE NOTICE
> This email message including attachments, if any, is intended for the person 
> or entity to which it is addressed and may contain confidential and/or 
> privileged information. Any unauthorized review, use or disclosure is 
> prohibited. If you are not the intended recipient, please contact the sender 
> and destroy the original message, including all copies.
> 
> 
> 
> CONFIDENTIALITY AND PRIVILEGE NOTICE
> This e-mail message, including attachments, if any, is intended for the 
> person or entity to which it is addressed and may contain confidential or 
> privileged information. Any unauthorized review, use, or disclosure is 
> prohibited. If you are not the intended recipient, please contact the sender 
> and destroy the original message, including all copies, Thank you.

Node Replication Change

[Vandeventer, Harold [OITS]]

I'm using Spectrum Protect 6.3.4.300 on Windows servers.

I've been running NODE replication for months, but need to make a change for a 
node.

The current setup: Server TSM01 replicates to Server TSM02 and TSM02 replicates 
to TSM01.

The change: a node is to be "relocated" to the DR site; thus TSM02 will become 
its main location, and will replicate back to TSM01.

No Export/Import to be done.

Thus, I believe (after reviewing the Administrator's Guide):
1: confirm that replication from TSM01 to TSM02 has completed.
2: on TSM01: UPDATE NODE  REPLM=RECEIVE
3: on TSM02: UPDATE NODE  REPLM=SEND
4: Modify the IP in the nodes DSM.OPT to point to TSM02.

I don't think SYNCREC and SYNCSEND are involved because a node EXPORT has not 
been used to populate the data on TSM01.  The data already exists, I just need 
to change which server is sending and which is receiving for the node.

Thanks for helping out.



Harold Vandeventer
Office of Information Technology Services
2800 SW Topeka Blvd
Topeka, KS 66611
(785) 296-0631
harold.vandeven...@ks.gov | www.oits.ks.gov



CONFIDENTIALITY AND PRIVILEGE NOTICE
This email message including attachments, if any, is intended for the person or 
entity to which it is addressed and may contain confidential and/or privileged 
information. Any unauthorized review, use or disclosure is prohibited. If you 
are not the intended recipient, please contact the sender and destroy the 
original message, including all copies.



CONFIDENTIALITY AND PRIVILEGE NOTICE
This e-mail message, including attachments, if any, is intended for the person 
or entity to which it is addressed and may contain confidential or privileged 
information. Any unauthorized review, use, or disclosure is prohibited. If you 
are not the intended recipient, please contact the sender and destroy the 
original message, including all copies, Thank you.

Re: What have they done to Passport!

[Vandeventer, Harold [OITS]]

Yep, looks like a re-do with a major hiccup.

The link to get to passport advantage seems to just reload the initial page.



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan 
Forray
Sent: Tuesday, February 23, 2016 3:07 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] What have they done to Passport!

I haven't been to Passport for a while. All I want to do is download the latest 
7.1 with included licenses (vs patches from the FTP site).

I have been wandering around and clicking for 30+ minutes and can't figure out 
what used to be a simple 3-clicks to get to my entitled software!  It keeps 
wanting to sell me something.  All I want is the software I am entitled to!  
Why is this being made so hard?

--
*Zoltan Forray*
TSM Software & Hardware Administrator
Xymon Monitor 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://infosecurity.vcu.edu/phishing.html

[Confidentiality notice:]
***
This e-mail message, including attachments, if any, is intended for the
person or entity to which it is addressed and may contain confidential
or privileged information.  Any unauthorized review, use, or disclosure
is prohibited.  If you are not the intended recipient, please contact
the sender and destroy the original message, including all copies,
Thank you.
***

Re: Rebalance the TSM DB filespaces

[Vandeventer, Harold [OITS]]

There are two additional tablespaces if you use node replication:
db2 alter tablespace REPLTBLSPACE1 rebalance
db2 alter tablespace REPLIDXSPACE1 rebalance

and the related reduce max commands for them.

Some of the tablespaces provided by Bill's db2 select do not allow a rebalance. 
 The names implying temporary space: TEMPSPACE1, TSMTEMP, LGTMPSP and 
SYSTOOLSTMPSPACE.


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
William Sefranek
Sent: Monday, February 22, 2016 9:48 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Rebalance the TSM DB filespaces

David,

We have performed the DB rebalance a few times without issue and we have run 
all the tablespaces at the same time. But we have our TSM databases on Raid 10 
disks on a Hitachi storage array. You might want to break up the rebalances by 
running each tablespace individually if you are using slower storage.

Also you can use this query to monitor the number of DB extents left to 
rebalance for each tablespace.

db2 "select varchar(tbsp_name, 30) as tbsp_name, dbpartitionnum, 
rebalancer_mode, rebalancer_extents_remaining, rebalancer_extents_processed, 
rebalancer_start_time from
table(snap_get_tbsp_part_v91(NULL,-2)) as t"

The rebalance process is complete when the columns under REBALANCER_MODE = 
NO_REBAL

Thanks,
Bill

On 2/22/2016 10:14 AM, David Ehresman wrote:
> The tsmtutorials.com web page says you can rebalance space usage after adding 
> a new DB filespace by issuing the following commands:
>
>
>*   Perform the rebalance activity during a quiet time. Logon as the 
> server instance owner and execute the DB2 commands below. (on Windows, you 
> need to run these commands from a DB2 Command Window and "set 
> db2instance=server1).
>  db2 connect to tsmdb1
>  db2 set schema tsmdb1
>  db2 alter tablespace SYSCATSPACE rebalance
>  db2 alter tablespace USERSPACE1 rebalance
>  db2 alter tablespace LARGESPACE1 rebalance
>  db2 alter tablespace LARGEIDXSPACE1 rebalance
>  db2 alter tablespace IDXSPACE1 rebalance
>  db2 alter tablespace SYSTOOLSPACE rebalance
>
>*   Depending on the size of the tablespace, the rebalance can take some 
> time to finish. For a large tablespace, the rebalance can take about 30 
> minutes. Run the following command to check the rebalance status
>  db2 "select * from SYSIBMADM.TBSP_UTILIZATION " |grep -i progress
>
>*   If the rebalance is still active, the above command will return the 
> tablespace still in active resizing. Wait until all tablespaces have done the 
> rebalance and execute the following commands to reduce the tablespaces
>  db2 alter tablespace SYSCATSPACE reduce max
>  db2 alter tablespace USERSPACE1 reduce max
>  db2 alter tablespace LARGESPACE1 reduce max
>  db2 alter tablespace LARGEIDXSPACE1 reduce max
>  db2 alter tablespace IDXSPACE1 reduce max
>  db2 alter tablespace SYSTOOLSPACE reduce max
>
>*   After the rebalance/reduce, the file systems should be equally 
> utilized and there are should be no more file systems in 100% full condition.
> - See more at: 
> http://www.tsmtutorials.com/2014/04/how-to-rebalance-tsm-server-databa
> se-tablespaces.html#sthash.pr2hDMzv.dpuf
>
> Has anyone had this work for them?  Anything to watch out for?
>
> David
>
>

--
William Sefranek
University of Buffalo
Enterprise Infrastructure Services
(716)645-5116

[Confidentiality notice:]
***
This e-mail message, including attachments, if any, is intended for the
person or entity to which it is addressed and may contain confidential
or privileged information.  Any unauthorized review, use, or disclosure
is prohibited.  If you are not the intended recipient, please contact
the sender and destroy the original message, including all copies,
Thank you.
***

RFE for new browser support in Monitoring for Spectrum Protect/TSM

[Vandeventer, Harold [OITS]]

I've created an RFE requesting that newer browsers, such as IE11/Edge be 
allowed for use with Monitoring/Reporting.

IBM documents that only IE8 and IE9 are supported, both of which are out of 
support by Microsoft and my network security office.

Other browsers, such as Chrome and Firefox, are not on the IBM officially 
supported browser list.

I've tried IE11, then using Developer mode (press F12) to emulate IE 9, without 
success.

Chrome, the latest version, is also unsuccessful.

The RFE can be found at: 
http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe_ID=83834


Harold Vandeventer
Office of Information Technology Services
(785) 296-0631
harold.vandeven...@ks.gov | 
www.oits.ks.gov



CONFIDENTIALITY AND PRIVILEGE NOTICE
This email message including attachments, if any, is intended for the person or 
entity to which it is addressed and may contain confidential and/or privileged 
information. Any unauthorized review, use or disclosure is prohibited. If you 
are not the intended recipient, please contact the sender and destroy the 
original message, including all copies.


[Confidentiality notice:]
***
This e-mail message, including attachments, if any, is intended for the
person or entity to which it is addressed and may contain confidential
or privileged information.  Any unauthorized review, use, or disclosure
is prohibited.  If you are not the intended recipient, please contact
the sender and destroy the original message, including all copies,
Thank you.
***

Re: Bring back TSM Administrator's Guide

[Vandeventer, Harold [OITS]]

Excellent!

My thoughts exactly re the Information Center.  

One can find what you already know about (to clarify a detail), but getting the 
big picture view requires that 1,000 pages and more of the Admin Guide.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Roger 
Deschner
Sent: Wednesday, February 03, 2016 8:28 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Bring back TSM Administrator's Guide

I'm glad that the last PDFs of this valuable book at Version 7.1.1 are being 
made more widely available. I have already downloaded that PDF to the USB thumb 
drive I carry around everywhere, for access regardless of the network 
condition. This could be in a disaster recovery scenario, or at a client node 
site where I might need to create a new account and password just to access the 
net and read the doc. The fact that it was deemed necessary to make this PDF 
more widely available, points out the problem.

If you are hinting that you are considering publishing an updated 7.1.5 
Administrator's Guide, that would be great! An important thing to update would 
be container storage pools. When to use them, how they compare to other types 
of storage pools (disk, file, tape, VTL...), and how to set them up and manage 
them. Perhaps include them in a new column in Table 5 on Page 77 of the 7.1.1 
Admin Guide. Another would be deduplication, which has a lot of new powerful 
features in 7.1.4, which will make it attractive to users who have not 
deduplicated before.

I rarely use the online Information Center. I find its hierarchical 
micro-partitioning of information to be way too narrowly focused, leading me to 
overlook obvious solutions to the problem at hand.
Especially new solutions such as container storage pools and the new features 
of deduplication. The Information Center is also especially poor in the client 
area. I always go to the PDFs first, even when online with fast network access. 
Therefore I can't give feedback in the way you suggest.

I tried the Custom PDF file creation facility, and I found it disappointing. 
The resulting PDF has only topics I could think of, and omits the ones I really 
need to solve a problem. It requires clairvoyance to make a useful PDF 
containing the answer to a problem that I haven't had yet, and it has no index.

So I am going to reiterate what I said before: Update the Administrator's Guide 
for 7.1.5, and keep it up-to-date going forward as a single book. This book is 
a key asset for the entire Spectrum Protect product, especially as existing 
customers seek to utilize features they haven't used before, and as new 
customers explore the incredible depth of features in the product.

Roger Deschner  University of Illinois at Chicago rog...@uic.edu
==I have not lost my mind -- it is backed up on tape somewhere.=


On Wed, 27 Jan 2016, Clare Byrne wrote:

>Following up on this thread, the 7.1.1 Administrator's Guide PDFs are 
>now available in IBM Knowledge Center at 
>http://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.1/com.ibm.itsm.ts
>m.doc/r_pdfs_tsm.html This is in addition to where they were available 
>before, in the .zip file and on the Tivoli Storage Manager wiki. We 
>hope this makes it easier to find and access the 7.1.1 guides.
>
>A reminder: We are still very much interested in hearing about what the 
>most important subjects from the 7.1.1 Administrator's Guide are for us 
>to consider for updates. Knowing more specifics about your priorities 
>is very important to us to set priorities.
>
>One way to give such feedback privately: Go to any topic (in any 
>version) for Tivoli Storage Manager in IBM Knowledge Center and click 
>the Feedback link in the menu bar at the very bottom. If your comments 
>exceed the 1000-character limit in the feedback form, you can include 
>your email address in the feedback and ask us to contact you.
>
>Clare Byrne
>Information Development for IBM Spectrum Protect Tucson, AZ  US
>
>
>__
>
>Please be assured that we in IBM development are listening and are 
>discussing future actions regarding the Administrator's Guide content 
>since the feedback about the 7.1.3 release that did not include that book.
>I gave some information in a response to that earlier feedback:
>http://www.mail-archive.com/adsm-l@vm.marist.edu/msg99286.html
>
>We are working on a plan to publish a solution guide for the 
>disk-to-tape architecture next. This should fill in some gaps left by 
>the removal of the Administrator's Guide. Timing of the publication is 
>yet to be determined.
>
>We are also discussing how to fill the information needs for those who 
>will not be using one of the four documented architectures. We already 
>point to the 7.1.1 guides from newer releases but we realize this is 
>not ideal. Possible actions include creating additional, supplemental 
>information outside of the solution guides, similar to what we have 
>done for the information 

File expiration in schedule log

[Vandeventer, Harold [OITS]]

I've never had to deal much with the client schedule log.

But, do the statements below (from dsmsched.log) mean that a file was marked to 
be expired, and that a subsequent EXPIRE INVENTORY on the TSM server would have 
removed the file?

01/19/2016 19:23:14 Expiring-->5,898,240 
\\\d$\\ [Sent]
 Several log lines
01/19/2016 19:23:14 Retry #1 Expiring-->5,898,240 
\\\d$\\ [Sent]


We have a default policy with a 30 day deleted files setting, but the fellow 
that owns the file claims he deleted it yesterday.

He's trying to restore and doesn't see the file in the list of available for 
recovery.

Thanks...


Harold Vandeventer
Office of Information Technology Services
(785) 296-0631
harold.vandeven...@ks.gov | 
www.oits.ks.gov



CONFIDENTIALITY AND PRIVILEGE NOTICE
This email message including attachments, if any, is intended for the person or 
entity to which it is addressed and may contain confidential and/or privileged 
information. Any unauthorized review, use or disclosure is prohibited. If you 
are not the intended recipient, please contact the sender and destroy the 
original message, including all copies.


[Confidentiality notice:]
***
This e-mail message, including attachments, if any, is intended for the
person or entity to which it is addressed and may contain confidential
or privileged information.  Any unauthorized review, use, or disclosure
is prohibited.  If you are not the intended recipient, please contact
the sender and destroy the original message, including all copies,
Thank you.
***

Re: VM Server for Monitoring/Reporting?

[Vandeventer, Harold [OITS]]

Thanks to all for some great advice.

I'll use this in my argument to properly provision.  The VM Admins are a stingy 
group.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Stefan 
Folkerts
Sent: Friday, January 08, 2016 8:21 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] VM Server for Monitoring/Reporting?

Good point Rick about not configuring your instance yet, especially if you want 
to be able to connect the instances because if you clone those VM's your unique 
id will be the same and it won't work.

I install the software on VM's, have all the mountpoints ready etc but be sure 
not to clone with the instance configured, that will hurt if you ever want to 
connect the server to server.

And like you said, they do take up a lot of resources and I think you should 
not use the normal storage subsystem since that is what you are protecting but 
taking these things into account it works really well.


On Fri, Jan 8, 2016 at 3:03 PM, Rick Adamson <rickadam...@segrocers.com>
wrote:

> I have to agree with Stefan, make sure you allocate the recommended 
> resources as per IBM best practices and virtualized ISP servers will 
> serve you well.
>
> All of my DR instances have been virtual for several years now, and in 
> production I am preparing to virtual both backup and OC server(s).
>
> An additional benefit for me is I create a VM template with all the 
> Spectrum Protect software loaded, but not configured. When needed it 
> only takes a few minutes to stand up a new or replacement ISP VM.
>
> My only issue was after my virtual backup servers were built my VMWare 
> admins went back and robbed them of CPU and memory resources claiming 
> that the resources were excessive. When they came under full 
> production performance was dismal.  As a part of agreeing to 
> virtualize the production environment I made sure that management 
> understood, and approved, the minimum system/instance requirements as 
> documented in the IBM blueprints document.
>
>
> -Rick Adamson
>
>
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf 
> Of Stefan Folkerts
> Sent: Friday, January 08, 2016 3:19 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] VM Server for Monitoring/Reporting?
>
> I don't understand the need for real metal servers other than when you 
> connect tape or need to do lan-free transport to tape (again, to have 
> supported connection to tape).
> Tape libraries connected to VMware vSphere are not supported (don't 
> know the current state) but the rest is just software running on an 
> OS, why would Spectrum Protect need to run on dedicated metal when 
> other software doesn't?
>
> In my lab setup I even run tape connected on VMware and that works 
> fine since version 5.5 of VMware, but that isn't supported so don't 
> try and do that, you can and probably will run into problems at some 
> stage, I have seen purple screens of death and have seen entire 
> vSphere hosts go down due to library issues on versions prior to 5.5 
> in my lab setup :-)
>
> I have implemented Spectrum Protect servers virtualized, it's 
> supported and it runs fine, just make sure you give it enough 
> resources, you can't treat it like some small VM and I do give it 
> dedicated storage (both for metadata and for data capacity and I mean 
> controllers and storage, not just
> disks) but then it runs just fine.
>
> The advantage is that you automatically have increased availability 
> due to VMware HA and have super fast backups for the machines running 
> on the same physical box.
>
> When it comes to reporting/monitor software I wouldn't think twice 
> about it if it isn't stated that it is unsupported.
>
>
> On Thu, Jan 7, 2016 at 9:51 PM, Vandeventer, Harold [OITS] < 
> harold.vandeven...@ks.gov> wrote:
>
> > I fully understand the need for real metal for the TSM/Spectrum 
> > Protect node-backup and Operation Center servers.
> >
> > Is anyone running something relatively benign like 7.1 
> > Monitoring/Reporting on a VM?
> >
> > I've got an old physical box, but need to add RAM.
> >
> > My management is pushing the "why not VM" solution.
> >
> >
> >
> > [Confidentiality notice:]
> > 
> > **
> > * This e-mail message, including attachments, if any, is intended 
> > for the person or entity to which it is addressed and may contain 
> > confidential or privileged information.  Any unauthorized review, 
> > use, or disclosure is prohibited.  If you are not the intended 
> > recipient, please contact the sender and destroy the original 
> > message, including all copies, Thank you.
> > 
> > **
> > *
> >
>

VM Server for Monitoring/Reporting?

[Vandeventer, Harold [OITS]]

I fully understand the need for real metal for the TSM/Spectrum Protect 
node-backup and Operation Center servers.

Is anyone running something relatively benign like 7.1 Monitoring/Reporting on 
a VM?

I've got an old physical box, but need to add RAM.

My management is pushing the "why not VM" solution.



[Confidentiality notice:]
***
This e-mail message, including attachments, if any, is intended for the
person or entity to which it is addressed and may contain confidential
or privileged information.  Any unauthorized review, use, or disclosure
is prohibited.  If you are not the intended recipient, please contact
the sender and destroy the original message, including all copies,
Thank you.
***

Re: Node replication information?

[Vandeventer, Harold [OITS]]

Welcome back Robert.  Lots of changes from the TSM 5 days.

I don't have any links to docs, but my experience has been...

I'm running Windows, 32 GB RAM, TSM 6.3.4.300.

I run 40 sessions on each Replication process.

The process is replicating a group that may have several members, 2 up to 15 or 
20; semi-random on how I assigned.

I have a script that contains several REPLICATE NODE  commands.  
Each command runs one group, with WAIT=YES, then another, with an exception 
described next.

I have a group that has nodes with a very large numbers of files for those 
nodes, thus the time required to determine what has to be migrated is long.  
The amount of data to replicate isn't huge, just the time required to inventory 
the status on a zillion files.

Therefore, that group is first in the script, with WAIT=NO, to immediately 
start the next group in the script.  Subsequent replicate groups all have 
WAIT=YES.

The only performance issue that I've seen as an issue is monitoring bandwidth 
on the link between the source and target servers.  I've watched Network stats 
in Windows Task Manager and depending on how many replication processes are 
running, the impact on the bandwidth goes up.  I haven't seen any hits on CPU 
or RAM.



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Robert 
Clark
Sent: Thursday, December 17, 2015 4:39 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Node replication information?

After a long hiatus from working with TSM, I am back to working with it again. 
(I left during the TSM 5 timeframe.)



Does anyone have pointers to docs useful in figuring out how node replication 
determines how much to attempt to do in parallel, or general information on how 
to troubleshoot its performance.



Thanks,

[RC]

[Confidentiality notice:]
***
This e-mail message, including attachments, if any, is intended for the
person or entity to which it is addressed and may contain confidential
or privileged information.  Any unauthorized review, use, or disclosure
is prohibited.  If you are not the intended recipient, please contact
the sender and destroy the original message, including all copies,
Thank you.
***

Node replication issue

[Vandeventer, Harold [OITS]]

I've been running node replication, TSM 6.3.4.300 on Windows, for several 
months.

Today, one node is causing trouble.

It has about 54,000 files to be deleted and after a two hour run has deleted 
zero files.

Files to be updated or replicated were successfully processed.

I can see two sessions on the target server, with 0 seconds wait time, but the 
bytes received is not changing over that period.

Has anyone seen this type of issue and have suggestions?

Thanks.


[Confidentiality notice:]
***
This e-mail message, including attachments, if any, is intended for the
person or entity to which it is addressed and may contain confidential
or privileged information.  Any unauthorized review, use, or disclosure
is prohibited.  If you are not the intended recipient, please contact
the sender and destroy the original message, including all copies,
Thank you.
***

Re: Enhancement request

[Vandeventer, Harold [OITS]]

I agree with Francisco's response... 

Briefly, it needs (IMO) to have the capability of the Administration Center.  I 
do use a command line, and the beauty of the old Mozilla browser that I can get 
to work is that it remembers previously issued commands so they are very easy 
to repeat from day to day.

I'm running TSM Server 6.3.4.300 and perhaps the OC doesn't fully fit with 
that version.  But, I find I can get my work done in AdminCenter OC doesn't 
meet my needs.

My primary hassle with AdminCenter is the requirement for an old browser/Java 
that my security guys constantly harass me about.  

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Robert 
Jose
Sent: Wednesday, August 12, 2015 11:34 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Enhancement request

Hello
Thanks Francisco for your feedback. I will get your enhancement requests to the 
appropriate people.

I would be interested to hear of any other enhancements that your feel OC needs 
now rather than later.

Rob Jose
TSM OC UI Developer / L3 Support


ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 08/11/2015
09:57:29 AM:

 From: Francisco Molero fmol...@yahoo.com
 To: ADSM-L@VM.MARIST.EDU
 Date: 08/11/2015 09:58 AM
 Subject: Re: [ADSM-L] Enhancement request Sent by: ADSM: Dist Stor 
 Manager ADSM-L@VM.MARIST.EDU

 Hi,

 I am using OC for a few things. The dashboard is very useful in a at 
 glance you can see how the state of TSM environment, the alert pane is 
 very good and the detail info for Clients and Servers is nice as well.  
 But we should encourage IBM to add more features to OC

 In my opinion OC needs:

 1.- OC should have a job control monitor to stop/start/pause/cancel.
 2.- OC should add the possibility to backup/restore files ( even
 databases/mails/FCM/etc) in a nice way. Only one Console, Please 
 don't add more consoles.
 3.- OC should add install/upgrade/remove clients and DP.
 4.- OC should add modify/delete Admin Tasks.5.- OC should add the 
 possibility to run scripts.6.- OC should add create/remove/modify 
 domains, policy set, mgmts, copygs.
 7.- OC should add any type of stgpools and device class. 8.- OC should 
 add a nice way to checking/checkout tapes.
 9.- OC should have a central reporting.
 ...
 Maybe I forget sth.

 In summary,

 we will need a tool to remove the CLI.

 Fran

   De: Loon, EJ van (ITOPT3) - KLM eric-van.l...@klm.com
  Para: ADSM-L@VM.MARIST.EDU
  Enviado: Martes 11 de agosto de 2015 16:22
  Asunto: Re: Enhancement request

 Hi Remco!
 Is anyone using OC then? ;-)
 Kind regards,
 Eric van Loon
 AF/KLM Storage Engineering

 -Original Message-
 From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf 
 Of Remco Post
 Sent: dinsdag 11 augustus 2015 15:15
 To: ADSM-L@VM.MARIST.EDU
 Subject: Re: Enhancement request

 The server name is quite visibly shown in the CLI part of OC. I’d 
 rather see the OC be enhanced than a developer spend time on the CLI.

  Op 11 aug. 2015, om 14:54 heeft Loon, EJ van (ITOPT3) - KLM Eric-
 van.l...@klm.com het volgende geschreven:
 
  Never mind, I wasn't looking correctly, TSM is part of the IBM RFE
 Community. I have created request 75293 for my enhancement, If you 
 think it's a useful enhancement to have the server name added to the 
 title of a Windows dsmadmc window, please support my request through

http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfeCR_ID=75293
  Kind regards,
  Eric van Loon
  AF/KLM Storage Engineering
 
  From: Loon, EJ van (ITOPT3) - KLM
  Sent: dinsdag 11 augustus 2015 14:42
  To: ADSM-L
  Subject: Enhancement request
 
  Hi guys!
  I would like to submit an enhancement request for the TSM Windows
 Admin Commandline interface (add the connected servername to the title 
 bar), but I can't find how to submit one. IBM has a site called IBM 
 RFE Community for these requests, but TSM is not listed on that 
 site...
  Thanks for any help in advance!
  Kind regards,
  Eric van Loon
  AF/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 

Re: Moving DB , LOG , ARCHLOG

[Vandeventer, Harold [OITS]]

I've used the recommendation made a day or two ago where Tivoli gets shutdown 
and the files copied to the new locations.

Then, map the new locations using the previous drive letters.

Boot and it has worked just fine.

I'm doing this as part of a decommission of an old SAN platform and moving onto 
a new SAN.

No editing of opt file, no messing around within DB2.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Remco 
Post
Sent: Wednesday, July 22, 2015 5:12 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Moving DB , LOG , ARCHLOG

and then, when all is done, check the db2 settings for active log, and archive 
log, fix them and restart, despite what the dsmserv.opt says

Op 22 jul. 2015, om 19:15 heeft Ron Delaware ron.delaw...@us.ibm.com het 
volgende geschreven:

 Robert,
 
 In order to move your TSM database, and logs, you will have to perform a 
 restore db and input the new directories/filespaces that you want the 
 database and logs to reside. 
 
 Moving both the database and recovery log You can move the database, 
 active log, and archive logs that are on the same file system to 
 various directories on different file systems for better protection.
 Procedure
 1. Back up the database by issuing the following command: 
 backup db type=full devclass=files
 2. Halt the server. 
 3. Create directories for the database, active logs, and archive logs. 
 The directories must be accessible to the user ID of the database manager. 
 For example:
 mkdir l:\tsm\db005
 mkdir m:\tsm\db006
 mkdir n:\tsm\db007
 mkdir o:\tsm\db008
 mkdir p:\tsm\activelog
 mkdir q:\tsm\archivelog
 4. Create a file that lists the locations of the database directories. 
 This file is used if the database must be restored. Enter each 
 location on a separate line. For example, these are the contents of the 
 dbdirs.txt file:
 l:\tsm\db005
 m:\tsm\db006
 n:\tsm\db007
 o:\tsm\db008
 5. Remove the database instance by issuing the following command: 
 dsmserv removedb TSMDB1
 6. Issue the DSMSERV RESTORE DB utility to move the database and 
 create the new active log. For example:
 dsmserv restore db todate=today on=dbdirs.txt 
 activelogdir=p:\tsm\activelog 7. Restart the server.
 
  
 Best Regards,
 
 _
 Mail-bijlage.jpeg  Mail-bijlage.jpeg  Mail-bijlage.jpeg
 email: ron.delaw...@us.ibm.com
 
   
 
 
 
 From:Robert Ouzen rou...@univ.haifa.ac.il 
 To:ADSM-L@VM.MARIST.EDU 
 Date:07/22/15 09:44 
 Subject:[ADSM-L] Moving DB , LOG , ARCHLOG 
 Sent by:ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 
 
 
 
 Hello
 
 I am in stage of moving my DB , Activelog and Archivelog from old storage to 
 faster storage,   DB on SSD disks
 
 I am wonder if I can do it in one step, meaning:
 
 
 1.   Creating new volumes for DB on SSD lists, create a list on dbdir.file
 
 2.   Create a new volume of 150G for  activelogas:  X:\tsmactlog
 
 3.   Create a new volume of 400G for archivelog  as:  Y:\tsmarchlog
 
 4.   On dsmserv.opt update those entries as:  ACTIVELOGDirectory
 X:\tsmactlog
 
   
   ARCHLOGDirectory   Y:\tsmarchlog
 
 5.   Run a full backup DB
 
 6.   Halt the server
 
 7.   Run dsmserv removedb  TSMDB1
 
 8.   Run dsmserv restore DB todate=today on=dbdir.file
 
 9.   Restart the server
 
 10.   Move the archivelog from the old directory to the new directory as:
 
 Xcopy /s  OLDDIRECTORY\*  Y:\tsmarchlog
 
 
 
 Or need to do it in 3 steps ? (meaning 3 halt of server)
 
 
 
 1.   ACTIVELOG  change in dsmserv.opt  , halt server and restart server
 
 2.   ARCHIVELOG  change in dsmser.opt , halt server and restart server
 
 3.   DB , backupdb  ,halt server , restore DB on=dbfile , restart server
 
 TSM server version 7.1.1.200 on Windows 2008R2 64B
 
 Best Regards
 
 Robert Ouzen
 
 



-- 

 Met vriendelijke groeten/Kind Regards,

Remco Post
r.p...@plcs.nl
+31 6 248 21 622

[Confidentiality notice:]
***
This e-mail message, including attachments, if any, is intended for the
person or entity to which it is addressed and may contain confidential
or privileged information.  Any unauthorized review, use, or disclosure
is prohibited.  If you are not the intended recipient, please contact
the sender and destroy the original message, including all copies,
Thank you.
***

Windows System State, files vs objects?

[Vandeventer, Harold [OITS]]

I'm deleting filespaces for a Windows 2008 node that has been decommissioned.

Deleting System State is a long process.

Q OCCUP node displays the number of files for each filespace.

During the delete of a filespace, Q PRO reports number of objects deleted.

For a set of files (documents, spreadsheets, etc.) the number of files on Q 
OCCUP and objects deleted in Q PRO appear to match or very closely match.

But, if the filespace is Window System State, those two numbers are 
significantly different.

In the current delete, occup reported about 100,000 files for System State.

But, 170,604 objects have been deleted.

Anyone know how to determine the number of objects that are in that System 
State filespace?  I'm curious how long this delete is going to take and having 
an estimate of the object count would be helpful.

Thanks.


Harold Vandeventer
Systems Programmer
State of Kansas - Office of Information Technology Services
STE 751-S
910 SW Jackson
(785) 296-0631


[Confidentiality notice:]
***
This e-mail message, including attachments, if any, is intended for the
person or entity to which it is addressed and may contain confidential
or privileged information.  Any unauthorized review, use, or disclosure
is prohibited.  If you are not the intended recipient, please contact
the sender and destroy the original message, including all copies,
Thank you.
***

Re: AW: EXPIRE INVENTORY problem

[Vandeventer, Harold [OITS]]

The EXPIRE process finally finished about 6 hours after starting.  It reported 
as successful but was qualified with finished before completion due to being 
cancelled.

I got some info from IBM via the PMR.

1: CAN PRO number and CANCEL EXPIRATION accomplish the same thing.  CAN PRO 
requires the process number, but CANCEL EXPIRATION cancels any currently 
running EXPIRE process.  CANCEL EXPIRATION was created so it could be used in 
scripting where the process number would be unknown.  Similar to the CANCEL 
REPLICATION command.

2: the EXPIRE process works on a filespace-by-filespace basis for a node.
It processes ALL of given filespace, then checks for duration limit.  If below 
the duration limit, it moves on to the next filespace.  If beyond duration, the 
process stops.

It's unknown why it took 6 hours to process a single filespace, the typical 
time on this server is about 1 hour.

So, something odd, hopefully won't see that again.  It really messed up my 
maintenance processing with significant that delay.



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Michael malitz
Sent: Wednesday, May 06, 2015 10:17 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] AW: EXPIRE INVENTORY problem

Hallo Harold,

you should use the command cancel expiration instead of cancel process. 
With cancel expiration you have checkpointing at transaction boundaries.

Rgds Michael Malitz

-Ursprüngliche Nachricht-
Von: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Im Auftrag von Rick 
Harderwijk
Gesendet: Mittwoch, 6. Mai 2015 16:44
An: ADSM-L@VM.MARIST.EDU
Betreff: Re: EXPIRE INVENTORY problem

If you cancel an expiration, does it not log every transaction, so that when 
you cancel, it effectively does a rollback on all the entries in the database? 
That might take some time as well...

On Wed, May 6, 2015 at 4:31 PM, Vandeventer, Harold [OITS]  
harold.vandeven...@ks.gov wrote:

 I'm running TSM 6.3.4.300 on Windows.

 I have a script that issues EXPIRE INVENTORY DURATION=90 RESOURCE=40 
 WAIT=YES.

 It was still running over 2 hours after start.

 I issued a CANCEL PRO and it's been in cancel in progress for over
 30 minutes.

 During all this time, Q PRO is reporting a constant number of nodes 
 processed, objects examined and objects deleted.

 Database and log space look fine, Health Monitor via the AdminCenter 
 GUI looks fine.

 What's happening in that process that would cause this behavior?

 
 Harold Vandeventer
 Systems Programmer
 State of Kansas - Office of Information Technology Services STE 751-S
 910 SW Jackson
 (785) 296-0631


 [Confidentiality notice:]
 **
 * This e-mail message, including attachments, if any, is intended for 
 the person or entity to which it is addressed and may contain 
 confidential or privileged information.  Any unauthorized review, use, 
 or disclosure is prohibited.  If you are not the intended recipient, 
 please contact the sender and destroy the original message, including 
 all copies, Thank you.
 **
 *

EXPIRE INVENTORY problem

[Vandeventer, Harold [OITS]]

I'm running TSM 6.3.4.300 on Windows.

I have a script that issues EXPIRE INVENTORY DURATION=90 RESOURCE=40 WAIT=YES.

It was still running over 2 hours after start.

I issued a CANCEL PRO and it's been in cancel in progress for over 30 minutes.

During all this time, Q PRO is reporting a constant number of nodes processed, 
objects examined and objects deleted.

Database and log space look fine, Health Monitor via the AdminCenter GUI looks 
fine.

What's happening in that process that would cause this behavior?


Harold Vandeventer
Systems Programmer
State of Kansas - Office of Information Technology Services
STE 751-S
910 SW Jackson
(785) 296-0631


[Confidentiality notice:]
***
This e-mail message, including attachments, if any, is intended for the
person or entity to which it is addressed and may contain confidential
or privileged information.  Any unauthorized review, use, or disclosure
is prohibited.  If you are not the intended recipient, please contact
the sender and destroy the original message, including all copies,
Thank you.
***

Re: AW: EXPIRE INVENTORY problem

[Vandeventer, Harold [OITS]]

Thanks for advice Michael and Rick.

The process is still in cancel in progress state, over two hours since 
cancelled.

Normally expire takes only about 60 minutes.

I've opened a PMR with IBM for advice.

I'll update the group when we've resolved the issue.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Michael malitz
Sent: Wednesday, May 06, 2015 10:17 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] AW: EXPIRE INVENTORY problem

Hallo Harold,

you should use the command cancel expiration instead of cancel process. 
With cancel expiration you have checkpointing at transaction boundaries.

Rgds Michael Malitz

-Ursprüngliche Nachricht-
Von: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Im Auftrag von Rick 
Harderwijk
Gesendet: Mittwoch, 6. Mai 2015 16:44
An: ADSM-L@VM.MARIST.EDU
Betreff: Re: EXPIRE INVENTORY problem

If you cancel an expiration, does it not log every transaction, so that when 
you cancel, it effectively does a rollback on all the entries in the database? 
That might take some time as well...

On Wed, May 6, 2015 at 4:31 PM, Vandeventer, Harold [OITS]  
harold.vandeven...@ks.gov wrote:

 I'm running TSM 6.3.4.300 on Windows.

 I have a script that issues EXPIRE INVENTORY DURATION=90 RESOURCE=40 
 WAIT=YES.

 It was still running over 2 hours after start.

 I issued a CANCEL PRO and it's been in cancel in progress for over
 30 minutes.

 During all this time, Q PRO is reporting a constant number of nodes 
 processed, objects examined and objects deleted.

 Database and log space look fine, Health Monitor via the AdminCenter 
 GUI looks fine.

 What's happening in that process that would cause this behavior?

 
 Harold Vandeventer
 Systems Programmer
 State of Kansas - Office of Information Technology Services STE 751-S
 910 SW Jackson
 (785) 296-0631


 [Confidentiality notice:]
 **
 * This e-mail message, including attachments, if any, is intended for 
 the person or entity to which it is addressed and may contain 
 confidential or privileged information.  Any unauthorized review, use, 
 or disclosure is prohibited.  If you are not the intended recipient, 
 please contact the sender and destroy the original message, including 
 all copies, Thank you.
 **
 *

Re: AW: EXPIRE INVENTORY problem

[Vandeventer, Harold [OITS]]

The expire process finished, 6 hours after starting; about 4 hours after the 
cancel was issued.

Act log does indicate success, but that it was cancelled prior to completion.

Between 07:12:43 and 12:12:35, there are no activity log items related to the 
process.



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Michael malitz
Sent: Wednesday, May 06, 2015 10:17 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] AW: EXPIRE INVENTORY problem

Hallo Harold,

you should use the command cancel expiration instead of cancel process. 
With cancel expiration you have checkpointing at transaction boundaries.

Rgds Michael Malitz

-Ursprüngliche Nachricht-
Von: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Im Auftrag von Rick 
Harderwijk
Gesendet: Mittwoch, 6. Mai 2015 16:44
An: ADSM-L@VM.MARIST.EDU
Betreff: Re: EXPIRE INVENTORY problem

If you cancel an expiration, does it not log every transaction, so that when 
you cancel, it effectively does a rollback on all the entries in the database? 
That might take some time as well...

On Wed, May 6, 2015 at 4:31 PM, Vandeventer, Harold [OITS]  
harold.vandeven...@ks.gov wrote:

 I'm running TSM 6.3.4.300 on Windows.

 I have a script that issues EXPIRE INVENTORY DURATION=90 RESOURCE=40 
 WAIT=YES.

 It was still running over 2 hours after start.

 I issued a CANCEL PRO and it's been in cancel in progress for over
 30 minutes.

 During all this time, Q PRO is reporting a constant number of nodes 
 processed, objects examined and objects deleted.

 Database and log space look fine, Health Monitor via the AdminCenter 
 GUI looks fine.

 What's happening in that process that would cause this behavior?

 
 Harold Vandeventer
 Systems Programmer
 State of Kansas - Office of Information Technology Services STE 751-S
 910 SW Jackson
 (785) 296-0631


 [Confidentiality notice:]
 **
 * This e-mail message, including attachments, if any, is intended for 
 the person or entity to which it is addressed and may contain 
 confidential or privileged information.  Any unauthorized review, use, 
 or disclosure is prohibited.  If you are not the intended recipient, 
 please contact the sender and destroy the original message, including 
 all copies, Thank you.
 **
 *

Java version and Admin Center

[Vandeventer, Harold [OITS]]

What's the latest version of Java being used for compatibility with TSM Admin 
Center?

I can run Java 6 Update 39 with Admin Center without issues for Admin Center.

I'm running TSM Servers at 6.3.4.300.
Admin Center is also at 6.3.4.300.

I'm in a bind where a newer Java is required to let me manage some new EMC VNX 
SANs (my other hat).

For a whim, I tried the latest (Java 8 Update 40) and Admin Center isn't very 
happy.

Thanks.



Harold Vandeventer
Systems Programmer
State of Kansas - Office of Information Technology Services
STE 751-S
910 SW Jackson
(785) 296-0631


[Confidentiality notice:]
***
This e-mail message, including attachments, if any, is intended for the
person or entity to which it is addressed and may contain confidential
or privileged information.  Any unauthorized review, use, or disclosure
is prohibited.  If you are not the intended recipient, please contact
the sender and destroy the original message, including all copies,
Thank you.
***

Re: Node cleanup

[Vandeventer, Harold [OITS]]

Thanks Wanda... you always have great recommendations.



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Prather, Wanda
Sent: Tuesday, March 17, 2015 10:21 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] !RE: Node cleanup

Don't see the purpose of renaming it--
If you just do:
exclude.dir  e:\data

That has the same effect.
It excludes them from backup, the existing backups get marked inactive on the 
next backup run, and the countdown clock starts for the number of days to keep 
the last version.  

If it's a lot of data, I've also done it as a 2-step process to get a more 
immediate effect:

Step 1: 
Create a management class called BLACKHOLE, with VEREex 1 VERDel 0 RETex  0 
RETonly 0

That says don't keep any versions after the files are marked inactive.

In dsm.opt add:
include e:\data\...\*   BLACKHOLE
Run an incremental backup (of everything or just that directory is fine).
The files should get REBOUND to the BLACKHOLE management class.  
(You can see that if you open the restore GUI and scroll all the way to the 
right, it says what mgt class the file is bound to.) From now on the new 
BLACKHOLE rules will apply.

Step2: 
Now in dsm.opt,
replace the INCLUDE with 
EXCLUDE.DIR   e:\data\
Bounce scheduler.
Next backup marks the files as inactive, and KABLAM!
 Since they are bound to BLACKHOLE (retextra=0 and retonly=0) they go away 
immediately instead of hanging around longer.
Your space totals will be updated the next time EXPIRE INVENTORY runs.


Wanda Prather
TSM Consultant
ICF International Enterprise and Cybersecurity Systems Division




-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Vandeventer, Harold [OITS]
Sent: Tuesday, March 17, 2015 4:32 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Node cleanup

I've gotten caught in a bill-back hassle with one of our clients.

Quick background:

1.   Node1 has backed up their data for years.

2.   Node2 was created to back up a new server.

3.   Some, but not all, data has been COPIED from the Node1 server to the 
Node2 server.  Not moved, just copied.  They can't access the data, but refuse 
to let server admins delete it.

4.   This has resulted in double-billing because TSM server now has both 
Node1 and Node2 with the data that was copied.

5.   Node1 has to stay in production to backup data that will never be 
relocated.

Will this approach work to clean up TSM DB occupancy for Node1 data?

1.   Rename folder E:\DATA to E:\OLDDATA.

2.   Place an EXCLUDE.DIR E$\OLDDATA in dsm.opt

3.   Stop/start the scheduler.

Will TSM resolve E:\DATA (which no longer exists) and all the files in it and 
its sub-folders as a deleted files and expiration processing would remove 
those files from the TSM DB for Node1?

There are sub-folders to OLDDATA, so the syntax for the EXCLUDE.DIR will need 
to respect that structure.

The expire would delete E:\DATA when the keep the last file version term has 
passed.

Other folders in E$ will continue to backup from Node1.

Thanks for helping out.


Harold Vandeventer
Systems Programmer
State of Kansas - Office of Information Technology Services STE 751-S
910 SW Jackson
(785) 296-0631


[Confidentiality notice:]
***
This e-mail message, including attachments, if any, is intended for the person 
or entity to which it is addressed and may contain confidential or privileged 
information.  Any unauthorized review, use, or disclosure is prohibited.  If 
you are not the intended recipient, please contact the sender and destroy the 
original message, including all copies, Thank you.
***

Node cleanup

[Vandeventer, Harold [OITS]]

I've gotten caught in a bill-back hassle with one of our clients.

Quick background:

1.   Node1 has backed up their data for years.

2.   Node2 was created to back up a new server.

3.   Some, but not all, data has been COPIED from the Node1 server to the 
Node2 server.  Not moved, just copied.  They can't access the data, but refuse 
to let server admins delete it.

4.   This has resulted in double-billing because TSM server now has both 
Node1 and Node2 with the data that was copied.

5.   Node1 has to stay in production to backup data that will never be 
relocated.

Will this approach work to clean up TSM DB occupancy for Node1 data?

1.   Rename folder E:\DATA to E:\OLDDATA.

2.   Place an EXCLUDE.DIR E$\OLDDATA in dsm.opt

3.   Stop/start the scheduler.

Will TSM resolve E:\DATA (which no longer exists) and all the files in it and 
its sub-folders as a deleted files and expiration processing would remove 
those files from the TSM DB for Node1?

There are sub-folders to OLDDATA, so the syntax for the EXCLUDE.DIR will need 
to respect that structure.

The expire would delete E:\DATA when the keep the last file version term has 
passed.

Other folders in E$ will continue to backup from Node1.

Thanks for helping out.


Harold Vandeventer
Systems Programmer
State of Kansas - Office of Information Technology Services
STE 751-S
910 SW Jackson
(785) 296-0631


[Confidentiality notice:]
***
This e-mail message, including attachments, if any, is intended for the
person or entity to which it is addressed and may contain confidential
or privileged information.  Any unauthorized review, use, or disclosure
is prohibited.  If you are not the intended recipient, please contact
the sender and destroy the original message, including all copies,
Thank you.
***

Re: Privilege escalation bug

[Vandeventer, Harold [OITS]]

Is the 5.3 release so old that it is considered not in support?



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Thomas 
Denier
Sent: Wednesday, February 25, 2015 9:56 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Privilege escalation bug

I received a security bulletin from IBM yesterday regarding Tivoli Storage 
Manager Stack-based Buffer Overflow Elevation of Privilege: CVE-2014-6184. The 
affected version/release combinations listed in the bulletin run from 5.4 to 
6.3. We still have one Linux system with 5.3 client code. Can I treat the list 
of affected releases as an explicit assurance that the 5.3 client does not have 
the vulnerability discussed in the bulletin? The alternative possibility that 
worries me is that 5.4 is the oldest level IBM thought it worthwhile to check.

Thomas Denier
Thomas Jefferson University
The information contained in this transmission contains privileged and 
confidential information. It is intended only for the use of the person named 
above. If you are not the intended recipient, you are hereby notified that any 
review, dissemination, distribution or duplication of this communication is 
strictly prohibited. If you are not the intended recipient, please contact the 
sender by reply email and destroy all copies of the original message.

CAUTION: Intended recipients should NOT use email communication for emergent or 
urgent health care matters.

[Confidentiality notice:]
***
This e-mail message, including attachments, if any, is intended for the
person or entity to which it is addressed and may contain confidential
or privileged information.  Any unauthorized review, use, or disclosure
is prohibited.  If you are not the intended recipient, please contact
the sender and destroy the original message, including all copies,
Thank you.
***

Stopping a client backup

[Vandeventer, Harold [OITS]]

I've been fighting a scheduled backup issue for one node.  Probably a firewall 
issue.

But, to keep management happy, a successful TELNET ip portnumber will not 
suffice.

I need to cancel the backup due to bandwidth issues across the wire during 
daytime hours.  The normal schedule won't run until late in the evening.

I've tried cancelling sessions, but the node end is re-establishing sessions to 
keep the backup running.

So, the question: How can I start a scheduled backup, then, once I see it is 
working, cancel it?

Thanks.


Harold Vandeventer
Systems Programmer
State of Kansas - Office of Information Technology Services
STE 751-S
910 SW Jackson
(785) 296-0631


[Confidentiality notice:]
***
This e-mail message, including attachments, if any, is intended for the
person or entity to which it is addressed and may contain confidential
or privileged information.  Any unauthorized review, use, or disclosure
is prohibited.  If you are not the intended recipient, please contact
the sender and destroy the original message, including all copies,
Thank you.
***

Re: Stopping a client backup

[Vandeventer, Harold [OITS]]

 started for node OAK4.VCU.EDU (TDP
  Domino SUN) (Tcp/Ip 192.168.20.139(32780)). (SESSION:

  66801)

02/10/2015 10:01:36  ANR0420W Session 66801 for node OAK4.VCU.EDU (TDP Domino
  SUN) refused - server disabled for user access.
(SESSION:
  66801)

02/10/2015 10:01:36  ANR0406I Session 66802 started for node OAK4.VCU.EDU (TDP
  Domino SUN) (Tcp/Ip 192.168.20.139(32781)). (SESSION:

  66802)

02/10/2015 10:01:36  ANR0420W Session 66802 for node OAK4.VCU.EDU (TDP Domino
  SUN) refused - server disabled for user access.
(SESSION:
  66802)

02/10/2015 10:01:37  ANR0406I Session 66803 started for node OAK4.VCU.EDU (TDP
  Domino SUN) (Tcp/Ip 192.168.20.139(32783)). (SESSION:

  66803)





On Tue, Feb 10, 2015 at 11:28 AM, Andrew Raibeck stor...@us.ibm.com wrote:

 Hi Harold,

 This is interesting... what method are you using the cancel the client 
 sessions? If you cancel the session from the admin client (CANCEL 
 SESSION command), then the client should recognize that the session 
 was cancelled by a TSM server administrator and not re-try the backup 
 (though it may reconnect to report backup status).

 - Andy


 __
 __

 Andrew Raibeck | Tivoli Storage Manager Level 3 Technical Lead | 
 stor...@us.ibm.com

 IBM Tivoli Storage Manager links:
 Product support:

 http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivol
 i_Storage_Manager

 Online documentation:
 http://www.ibm.com/support/knowledgecenter/SSGSG7/welcome
 Product Wiki:

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

 ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 2015-02-10
 11:21:16:

  From: Vandeventer, Harold [OITS] harold.vandeven...@ks.gov
  To: ADSM-L@VM.MARIST.EDU
  Date: 2015-02-10 11:23
  Subject: Re: Stopping a client backup Sent by: ADSM: Dist Stor 
  Manager ADSM-L@VM.MARIST.EDU
 
  I'll investigate LOCK NODE.
 
  I've tried creating an Option Set with COMMRESTARTDURATION and 
  COMMRESTARTINTERVAL but Admin Center 6.3.4.300 insists those are 
  invalid options.
 
  I'm experimenting with my workstation node, and modified my 
  preferences for those comm settings.  Then tried to copy the option 
  name into Admin Center but not a valid option name apparently.
 
  Help in the baclient GUI indicates a server side option can override 
  the node dsm.opt value.
 
  I'll try the new Operations Center, but not holding my breath there.
 
 
 
  -Original Message-
  From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On 
  Behalf Of Skylar Thompson
  Sent: Tuesday, February 10, 2015 9:52 AM
  To: ADSM-L@VM.MARIST.EDU
  Subject: Re: [ADSM-L] Stopping a client backup
 
  LOCK NODE ought to do the trick. Or, if it's just a scheduled 
  task, expire the schedule - UPD SCH domain sch-name EXPIR=today-1.
 
  On Tue, Feb 10, 2015 at 03:47:22PM +, Vandeventer, Harold [OITS]
 wrote:
   I've been fighting a scheduled backup issue for one node.
  Probably a firewall issue.
  
   But, to keep management happy, a successful TELNET ip
  portnumber will not suffice.
  
   I need to cancel the backup due to bandwidth issues across the
  wire during daytime hours.  The normal schedule won't run until late 
  in the evening.
  
   I've tried cancelling sessions, but the node end is re-
  establishing sessions to keep the backup running.
  
   So, the question: How can I start a scheduled backup, then, once I
  see it is working, cancel it?
  
   Thanks.
  
   
   Harold Vandeventer
   Systems Programmer
   State of Kansas - Office of Information Technology Services STE 
   751-S
   910 SW Jackson
   (785) 296-0631
  
  
   [Confidentiality notice:]
   **
   * This e-mail message, including attachments, if any, is 
   intended for the person or entity to which it is addressed and may 
   contain confidential or privileged information.  Any unauthorized 
   review, use, or disclosure is prohibited.  If you are not the 
   intended recipient, please contact the sender and destroy the 
   original message, including all copies, Thank you.
   **
   *
 
  --
  -- Skylar Thompson (skyl...@u.washington.edu)
  -- Genome Sciences Department, System Administrator
  -- Foege Building S046, (206)-685-7354
  -- University of Washington School of Medicine
 




--
*Zoltan Forray*
TSM Software  Hardware Administrator
BigBro / Hobbit / Xymon Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zfor...@vcu.edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will never

Re: Stopping a client backup

[Vandeventer, Harold [OITS]]

Thanks Francisco... I'll try your approach.

One other suggestion also mentioned lock node.

It will impact only the one node, not all the  others that may be connecting.

As you say: patience is a virtue.

And, no problems understanding your English.  Thanks again.

PS: I can't DEFINE CLIENTOPT name  the command line error returns:

define clientopt STOPCOMM COMMRESTARTDURATION 0 FORCE=YES SEQ=1
ANR2056E DEFINE CLIENTOPT: Invalid option name - COMMRESTARTDURATION. Retry 
using the full optionname.

I copied the option name from my own DSM.OPTargh.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Francisco Javier
Sent: Tuesday, February 10, 2015 11:28 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Stopping a client backup

Try to:
1.- lock node
2.- cancel ses

While the node are trying to send the data always will try to connect at the 
TSMSERVER, in your case you are  backing Domino databases, in this case the 
data is large and the node  could try for long time the retry connect to TSM, 
be patient until the session cancel by himself =)

My apologies for my english I still learning ..

Regards



2015-02-10 11:16 GMT-06:00 Vandeventer, Harold [OITS] 
harold.vandeven...@ks.gov:

 I'd not tried to DISABLE SESSIONS.

 It seems the node side COMM settings would continue to reconnect every 
 15 seconds (default) for the 60 minute (default) period.

 I can't keep DISABLE SESSIONS in place for that long.

 Since I can't get Admin Center to let me create an option set with 
 COMMRESTARTDURATION and COMMRESTARTINTERVAL I'll look up the command 
 line approach to creating an option set.

 My TSM server is doing all kinds of stuff. can't be too 
 overpowering or I blow off a few hundred node managers.



 -Original Message-
 From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf 
 Of Zoltan Forray
 Sent: Tuesday, February 10, 2015 11:03 AM
 To: ADSM-L@VM.MARIST.EDU
 Subject: Re: [ADSM-L] Stopping a client backup

 I will add my $.02 worth since I just went through this not 2-hours ago.

 I needed to perform special maintenance on my TSM servers.  I do a 
 DISABLE SESSIONS on all servers and then I CANCEL SESSIONS from the server 
 side.
 The sessions immediately try to reconnect.  TDP clients are the most
 aggressive:

 02/10/2015 09:57:51  ANR2017I Administrator ZFORRAY issued command:
 DISABLE SESSIONS  (SESSION: 66755)

 ..

 02/10/2015 10:01:32  ANR2017I Administrator ZFORRAY issued command: 
 CANCEL

   SESSION 65935  (SESSION: 66792)

 02/10/2015 10:01:32  ANR0490I Canceling session 65935 for node 
 OAK4.VCU.EDU

   (TDP Domino SUN) . (SESSION: 66792)

 02/10/2015 10:01:32  ANR0524W Transaction failed for session 65935 for 
 node

   OAK4.VCU.EDU (TDP Domino SUN) - data transfer

   interrupted. (SESSION: 65935)

 02/10/2015 10:01:32  ANR0405I Session 66792 ended for administrator 
 ZFORRAY

   (WinNT). (SESSION: 66792)

 02/10/2015 10:01:32  ANR0483W Session 65935 for node OAK4.VCU.EDU (TDP 
 Domino
   SUN) terminated - forced by administrator. (SESSION:

   65935)

 02/10/2015 10:01:33  ANR0406I Session 66793 started for node 
 OAK4.VCU.EDU (TDP
   Domino SUN) (Tcp/Ip 192.168.20.139(32771)). (SESSION:

   66793)

 02/10/2015 10:01:33  ANR0420W Session 66793 for node OAK4.VCU.EDU (TDP 
 Domino
   SUN) refused - server disabled for user access.
 (SESSION:
   66793)

 02/10/2015 10:01:33  ANR0406I Session 66794 started for node 
 OAK4.VCU.EDU (TDP
   Domino SUN) (Tcp/Ip 192.168.20.139(32772)). (SESSION:

   66794)

 02/10/2015 10:01:33  ANR0420W Session 66794 for node OAK4.VCU.EDU (TDP 
 Domino
   SUN) refused - server disabled for user access.
 (SESSION:
   66794)

 02/10/2015 10:01:35  ANR0406I Session 66795 started for node 
 OAK4.VCU.EDU (TDP
   Domino SUN) (Tcp/Ip 192.168.20.139(32774)). (SESSION:

   66795)

 02/10/2015 10:01:35  ANR0420W Session 66795 for node OAK4.VCU.EDU (TDP 
 Domino
   SUN) refused - server disabled for user access.
 (SESSION:
   66795)

 02/10/2015 10:01:35  ANR0406I Session 66796 started for node 
 OAK4.VCU.EDU (TDP
   Domino SUN) (Tcp/Ip 192.168.20.139(32775)). (SESSION:

   66796)

 02/10/2015 10:01:35  ANR0420W Session 66796 for node OAK4.VCU.EDU (TDP 
 Domino
   SUN) refused - server disabled for user access.
 (SESSION:
   66796)

 02/10/2015 10:01:35  ANR0406I Session 66797 started for node 
 OAK4.VCU.EDU (TDP
   Domino SUN) (Tcp/Ip 192.168.20.139(32776)). (SESSION:

   66797

Re: Stopping a client backup

[Vandeventer, Harold [OITS]]

I had used the CANCEL SESSION  command from Admin Center Command prompt 
line.

It continually re-established sessions and I finally let it roll to completion. 
 That was for a drive that had previously backed up, with almost no change, so 
I wasn't too worried about bandwidth.

The node I'm trying to test now is new, so a LOT of data to be transferred.

I don't have access to the node, it's several blocks away, no RDP allowed.  

The node manager is in house today, but some political issues (partly based 
on the fact backup didn't run last night) are keeping her in a meeting (getting 
yelled at) rather than being able to actually work and help solve the trouble.

I'm confident the normal schedule for tonight will run, I have a successful 
TELENT ip port test.  But mgmt on the other end is yelling/screaming.

Several have offered suggestions;  I'll fire off a schedule and try again.

Thanks to all.


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Andrew 
Raibeck
Sent: Tuesday, February 10, 2015 10:42 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Stopping a client backup

Replying to my own post when you cancel a scheduled backup session, here is 
what I would expect to see. Note the key message, ANS1369E.

-
Normal File--  file_size file_name  ** Unsuccessful **

ANS1809W A session with the TSM server has been disconnected. An attempt will 
be made to reestablish the connection.
... failedtion attempt will be made in 00:00:00

Total number of objects inspected:2,640
Total number of objects backed up:  207
   ...  [snip ending stats]
Elapsed processing time:   00:02:07
ANS1369E Session Rejected: The session was canceled by the server administrator.

ANS1512E Scheduled event 'STANDARD' failed.  Return code = 12.
Sending results for scheduled event 'STANDARD'.
Results sent to server for scheduled event 'STANDARD'.

TSM Backup-Archive Client Version 7, Release 1, Level 1.1 Querying server for 
next scheduled event.
Node Name: RAIBECK
-

Regards,

- Andy



Andrew Raibeck | Tivoli Storage Manager Level 3 Technical Lead | 
stor...@us.ibm.com

IBM Tivoli Storage Manager links:
Product support:
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager

Online documentation:
http://www.ibm.com/support/knowledgecenter/SSGSG7/welcome
Product Wiki:
https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%20Storage%20Manager

ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 2015-02-10
11:28:51:

 From: Andrew Raibeck/Hartford/IBM@IBMUS
 To: ADSM-L@VM.MARIST.EDU
 Date: 2015-02-10 11:37
 Subject: Re: Stopping a client backup
 Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU

 Hi Harold,

 This is interesting... what method are you using the cancel the client 
 sessions? If you cancel the session from the admin client (CANCEL 
 SESSION command), then the client should recognize that the session 
 was cancelled by a TSM server administrator and not re-try the backup 
 (though it may reconnect to report backup status).

 - Andy





 Andrew Raibeck | Tivoli Storage Manager Level 3 Technical Lead | 
 stor...@us.ibm.com

 IBM Tivoli Storage Manager links:
 Product support:
 http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/
 Tivoli_Storage_Manager

 Online documentation:
 http://www.ibm.com/support/knowledgecenter/SSGSG7/welcome
 Product Wiki:
 https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%
 20Storage%20Manager

 ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 2015-02-10
 11:21:16:

  From: Vandeventer, Harold [OITS] harold.vandeven...@ks.gov
  To: ADSM-L@VM.MARIST.EDU
  Date: 2015-02-10 11:23
  Subject: Re: Stopping a client backup Sent by: ADSM: Dist Stor 
  Manager ADSM-L@VM.MARIST.EDU
 
  I'll investigate LOCK NODE.
 
  I've tried creating an Option Set with COMMRESTARTDURATION and 
  COMMRESTARTINTERVAL but Admin Center 6.3.4.300 insists those are 
  invalid options.
 
  I'm experimenting with my workstation node, and modified my 
  preferences for those comm settings.  Then tried to copy the option 
  name into Admin Center but not a valid option name apparently.
 
  Help in the baclient GUI indicates a server side option can override 
  the node dsm.opt value.
 
  I'll try the new Operations Center, but not holding my breath there.
 
 
 
  -Original Message-
  From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On 
  Behalf Of Skylar Thompson
  Sent: Tuesday, February 10, 2015 9:52 AM
  To: ADSM-L@VM.MARIST.EDU
  Subject: Re: [ADSM-L] Stopping a client backup
 
  LOCK NODE ought to do the trick. Or, if it's just a scheduled 
  task, expire the schedule

Re: Stopping a client backup

[Vandeventer, Harold [OITS]]

An update for everyone...

Success I used CANCEL SESSION and it worked.  Didn't have to go so far as 
LOCK NODE.

I created a schedule via DEFINE CLIENTACTION.

As soon as I saw the first connection come up, I cancelled that session.

Act log reported the session was cancelled by administrator.

A new session was immediately created.  But that session lasted only a few 
seconds.

My assumption is it was reporting back to the node sched.log or error.log.

Anyway, no additional sessions created.

How this differs from yesterday:

The node yesterday had proceeded far enough to be actively backing up data.

The node today (a different one) was only in the initial session and had not 
yet started any backup of data.

Thanks to everyone for all the suggestions... this is a great team!

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Francisco Javier
Sent: Tuesday, February 10, 2015 11:39 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Stopping a client backup

If the memory don't fail me you cann't modify the option file while the session 
is active. And yes it's only will affect to the node in question.

Regards


2015-02-10 11:36 GMT-06:00 Vandeventer, Harold [OITS] 
harold.vandeven...@ks.gov:

 Thanks Francisco... I'll try your approach.

 One other suggestion also mentioned lock node.

 It will impact only the one node, not all the  others that may be 
 connecting.

 As you say: patience is a virtue.

 And, no problems understanding your English.  Thanks again.

 PS: I can't DEFINE CLIENTOPT name  the command line error returns:

 define clientopt STOPCOMM COMMRESTARTDURATION 0 FORCE=YES SEQ=1 
 ANR2056E DEFINE CLIENTOPT: Invalid option name - COMMRESTARTDURATION.
 Retry using the full optionname.

 I copied the option name from my own DSM.OPTargh.

 -Original Message-
 From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf 
 Of Francisco Javier
 Sent: Tuesday, February 10, 2015 11:28 AM
 To: ADSM-L@VM.MARIST.EDU
 Subject: Re: [ADSM-L] Stopping a client backup

 Try to:
 1.- lock node
 2.- cancel ses

 While the node are trying to send the data always will try to connect 
 at the TSMSERVER, in your case you are  backing Domino databases, in 
 this case the data is large and the node  could try for long time the 
 retry connect to TSM, be patient until the session cancel by himself 
 =)

 My apologies for my english I still learning ..

 Regards



 2015-02-10 11:16 GMT-06:00 Vandeventer, Harold [OITS] 
 harold.vandeven...@ks.gov:

  I'd not tried to DISABLE SESSIONS.
 
  It seems the node side COMM settings would continue to reconnect 
  every
  15 seconds (default) for the 60 minute (default) period.
 
  I can't keep DISABLE SESSIONS in place for that long.
 
  Since I can't get Admin Center to let me create an option set with 
  COMMRESTARTDURATION and COMMRESTARTINTERVAL I'll look up the command 
  line approach to creating an option set.
 
  My TSM server is doing all kinds of stuff. can't be too 
  overpowering or I blow off a few hundred node managers.
 
 
 
  -Original Message-
  From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On 
  Behalf Of Zoltan Forray
  Sent: Tuesday, February 10, 2015 11:03 AM
  To: ADSM-L@VM.MARIST.EDU
  Subject: Re: [ADSM-L] Stopping a client backup
 
  I will add my $.02 worth since I just went through this not 2-hours ago.
 
  I needed to perform special maintenance on my TSM servers.  I do a 
  DISABLE SESSIONS on all servers and then I CANCEL SESSIONS from the
 server side.
  The sessions immediately try to reconnect.  TDP clients are the most
  aggressive:
 
  02/10/2015 09:57:51  ANR2017I Administrator ZFORRAY issued command:
  DISABLE SESSIONS  (SESSION: 66755)
 
  ..
 
  02/10/2015 10:01:32  ANR2017I Administrator ZFORRAY issued command:
  CANCEL
 
SESSION 65935  (SESSION: 66792)
 
  02/10/2015 10:01:32  ANR0490I Canceling session 65935 for node 
  OAK4.VCU.EDU
 
(TDP Domino SUN) . (SESSION: 66792)
 
  02/10/2015 10:01:32  ANR0524W Transaction failed for session 65935 
  for node
 
OAK4.VCU.EDU (TDP Domino SUN) - data transfer
 
interrupted. (SESSION: 65935)
 
  02/10/2015 10:01:32  ANR0405I Session 66792 ended for administrator 
  ZFORRAY
 
(WinNT). (SESSION: 66792)
 
  02/10/2015 10:01:32  ANR0483W Session 65935 for node OAK4.VCU.EDU 
  (TDP Domino
SUN) terminated - forced by administrator.
 (SESSION:
 
65935)
 
  02/10/2015 10:01:33  ANR0406I Session 66793 started for node 
  OAK4.VCU.EDU (TDP
Domino SUN) (Tcp/Ip 192.168.20.139(32771)).
 (SESSION:
 
66793)
 
  02/10/2015 10:01:33  ANR0420W Session 66793 for node OAK4.VCU.EDU 
  (TDP Domino
SUN) refused - server disabled for user access.
  (SESSION

Re: Stopping a client backup

[Vandeventer, Harold [OITS]]

I'll investigate LOCK NODE.

I've tried creating an Option Set with COMMRESTARTDURATION and 
COMMRESTARTINTERVAL but Admin Center 6.3.4.300 insists those are invalid 
options.  

I'm experimenting with my workstation node, and modified my preferences for 
those comm settings.  Then tried to copy the option name into Admin Center 
but not a valid option name apparently.  

Help in the baclient GUI indicates a server side option can override the node 
dsm.opt value.

I'll try the new Operations Center, but not holding my breath there.



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Skylar 
Thompson
Sent: Tuesday, February 10, 2015 9:52 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Stopping a client backup

LOCK NODE ought to do the trick. Or, if it's just a scheduled task, expire 
the schedule - UPD SCH domain sch-name EXPIR=today-1.

On Tue, Feb 10, 2015 at 03:47:22PM +, Vandeventer, Harold [OITS] wrote:
 I've been fighting a scheduled backup issue for one node.  Probably a 
 firewall issue.

 But, to keep management happy, a successful TELNET ip portnumber will not 
 suffice.

 I need to cancel the backup due to bandwidth issues across the wire during 
 daytime hours.  The normal schedule won't run until late in the evening.

 I've tried cancelling sessions, but the node end is re-establishing sessions 
 to keep the backup running.

 So, the question: How can I start a scheduled backup, then, once I see it is 
 working, cancel it?

 Thanks.

 
 Harold Vandeventer
 Systems Programmer
 State of Kansas - Office of Information Technology Services STE 751-S
 910 SW Jackson
 (785) 296-0631


 [Confidentiality notice:]
 ***
 This e-mail message, including attachments, if any, is intended for the
 person or entity to which it is addressed and may contain confidential
 or privileged information.  Any unauthorized review, use, or disclosure
 is prohibited.  If you are not the intended recipient, please contact
 the sender and destroy the original message, including all copies,
 Thank you.
 ***

--
-- Skylar Thompson (skyl...@u.washington.edu)
-- Genome Sciences Department, System Administrator
-- Foege Building S046, (206)-685-7354
-- University of Washington School of Medicine

Re: Stopping a client backup

[Vandeventer, Harold [OITS]]

I had tried to cancel by deleting the schedule; but sessions continued to 
re-fire.

I'll try this on my workstation node, where breaking things is a bit more 
acceptable.

Thanks.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Rick 
Adamson
Sent: Tuesday, February 10, 2015 10:18 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Stopping a client backup

The re-established connections probably occur because the scheduled backup 
event is still active.
Take a look at the schedule duration and make sure that it expires before 
undesirable hours.

For example:
Let's say you have a schedule for 5:00am and a duration of 6 hours.
You notice it is still running at 8:30am and try to cancel it, since it is 
still in the defined 6 hour window, the schedule is still active, the process 
restarts.
If you lower the duration to 3 hours, and cancel it at 8:30, it is now beyond 
the defined window for the backup.
The event will be flagged as failed and when the client tries to re-establish 
the connection it will disconnect since there is no active schedule to 
execute.


Rick Adamson
   

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Vandeventer, Harold [OITS]
Sent: Tuesday, February 10, 2015 10:47 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Stopping a client backup

I've been fighting a scheduled backup issue for one node.  Probably a firewall 
issue.

But, to keep management happy, a successful TELNET ip portnumber will not 
suffice.

I need to cancel the backup due to bandwidth issues across the wire during 
daytime hours.  The normal schedule won't run until late in the evening.

I've tried cancelling sessions, but the node end is re-establishing sessions to 
keep the backup running.

So, the question: How can I start a scheduled backup, then, once I see it is 
working, cancel it?

Thanks.


Harold Vandeventer
Systems Programmer
State of Kansas - Office of Information Technology Services STE 751-S
910 SW Jackson
(785) 296-0631


[Confidentiality notice:]
***
This e-mail message, including attachments, if any, is intended for the person 
or entity to which it is addressed and may contain confidential or privileged 
information.  Any unauthorized review, use, or disclosure is prohibited.  If 
you are not the intended recipient, please contact the sender and destroy the 
original message, including all copies, Thank you.
***

Re: Stopping a client backup

[Vandeventer, Harold [OITS]]

Thanks Yann.

I had based my attempt on creating a server-side option set based on the help 
in the client-side GUI.
Actually, I can't find the help item now. 

I THOUGHT I had read that server could override those but apparently not.

Thanks again to all.





-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Meunier, Yann
Sent: Tuesday, February 10, 2015 11:53 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Stopping a client backup

Hi,

You can find a list of options available here : 
http://www-01.ibm.com/support/knowledgecenter/?lang=fr#!/SSGSG7_7.1.0/com.ibm.itsm.client.doc/c_opt_setbyserver.html
I think the option COMMRESTARTDURATION is available on the client side.

Best Regards,
Yann MEUNIER

-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de 
Vandeventer, Harold [OITS] Envoyé : mardi 10 février 2015 18:36 À : 
ADSM-L@VM.MARIST.EDU Objet : Re: [ADSM-L] Stopping a client backup

Thanks Francisco... I'll try your approach.

One other suggestion also mentioned lock node.

It will impact only the one node, not all the  others that may be connecting.

As you say: patience is a virtue.

And, no problems understanding your English.  Thanks again.

PS: I can't DEFINE CLIENTOPT name  the command line error returns:

define clientopt STOPCOMM COMMRESTARTDURATION 0 FORCE=YES SEQ=1 ANR2056E DEFINE 
CLIENTOPT: Invalid option name - COMMRESTARTDURATION. Retry using the full 
optionname.

I copied the option name from my own DSM.OPTargh.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Francisco Javier
Sent: Tuesday, February 10, 2015 11:28 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Stopping a client backup

Try to:
1.- lock node
2.- cancel ses

While the node are trying to send the data always will try to connect at the 
TSMSERVER, in your case you are  backing Domino databases, in this case the 
data is large and the node  could try for long time the retry connect to TSM, 
be patient until the session cancel by himself =)

My apologies for my english I still learning ..

Regards



2015-02-10 11:16 GMT-06:00 Vandeventer, Harold [OITS] 
harold.vandeven...@ks.gov:

 I'd not tried to DISABLE SESSIONS.

 It seems the node side COMM settings would continue to reconnect every
 15 seconds (default) for the 60 minute (default) period.

 I can't keep DISABLE SESSIONS in place for that long.

 Since I can't get Admin Center to let me create an option set with 
 COMMRESTARTDURATION and COMMRESTARTINTERVAL I'll look up the command 
 line approach to creating an option set.

 My TSM server is doing all kinds of stuff. can't be too 
 overpowering or I blow off a few hundred node managers.



 -Original Message-
 From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf 
 Of Zoltan Forray
 Sent: Tuesday, February 10, 2015 11:03 AM
 To: ADSM-L@VM.MARIST.EDU
 Subject: Re: [ADSM-L] Stopping a client backup

 I will add my $.02 worth since I just went through this not 2-hours ago.

 I needed to perform special maintenance on my TSM servers.  I do a 
 DISABLE SESSIONS on all servers and then I CANCEL SESSIONS from the server 
 side.
 The sessions immediately try to reconnect.  TDP clients are the most
 aggressive:

 02/10/2015 09:57:51  ANR2017I Administrator ZFORRAY issued command:
 DISABLE SESSIONS  (SESSION: 66755)

 ..

 02/10/2015 10:01:32  ANR2017I Administrator ZFORRAY issued command:
 CANCEL

   SESSION 65935  (SESSION: 66792)

 02/10/2015 10:01:32  ANR0490I Canceling session 65935 for node 
 OAK4.VCU.EDU

   (TDP Domino SUN) . (SESSION: 66792)

 02/10/2015 10:01:32  ANR0524W Transaction failed for session 65935 for 
 node

   OAK4.VCU.EDU (TDP Domino SUN) - data transfer

   interrupted. (SESSION: 65935)

 02/10/2015 10:01:32  ANR0405I Session 66792 ended for administrator 
 ZFORRAY

   (WinNT). (SESSION: 66792)

 02/10/2015 10:01:32  ANR0483W Session 65935 for node OAK4.VCU.EDU (TDP 
 Domino
   SUN) terminated - forced by administrator. (SESSION:

   65935)

 02/10/2015 10:01:33  ANR0406I Session 66793 started for node 
 OAK4.VCU.EDU (TDP
   Domino SUN) (Tcp/Ip 192.168.20.139(32771)). (SESSION:

   66793)

 02/10/2015 10:01:33  ANR0420W Session 66793 for node OAK4.VCU.EDU (TDP 
 Domino
   SUN) refused - server disabled for user access.
 (SESSION:
   66793)

 02/10/2015 10:01:33  ANR0406I Session 66794 started for node 
 OAK4.VCU.EDU (TDP
   Domino SUN) (Tcp/Ip 192.168.20.139(32772)). (SESSION:

   66794)

 02/10/2015 10:01:33  ANR0420W Session 66794 for node OAK4.VCU.EDU (TDP 
 Domino
   SUN) refused - server disabled for user

Re: TSM Scheduled SQL Backups

[Vandeventer, Harold [OITS]]

Our guys have each SQL DB on a different drive on the server.

They use SQL Maintenance Plan (I think that's what it's called) to have SQL 
create a backup to a folder on the same drive as that DB.

Then, install TSM client, not the TSM  Data Protection SQL.

They configure a TSM  Option file on each drive.

One TSM node for each, using different listening ports.

The node backup is configured to skip the live DB, only backing up the output 
created by the SQL Maint plan.

Granted, not live, but acceptable for our DBs.


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of David 
Ehresman
Sent: Wednesday, January 14, 2015 2:30 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] TSM Scheduled SQL Backups

Has anyone done TSM Server Scheduling of SQL backups where there are multiple 
SQL databases on a single server, each using a unique TSM node name for 
backups?  Any hints?  I'm a TSM server admin but know next to nothing about SQL 
or TSM for SQL.

David

[Confidentiality notice:]
***
This e-mail message, including attachments, if any, is intended for the
person or entity to which it is addressed and may contain confidential
or privileged information.  Any unauthorized review, use, or disclosure
is prohibited.  If you are not the intended recipient, please contact
the sender and destroy the original message, including all copies,
Thank you.
***

Re: SAN hardware hints

[Vandeventer, Harold [OITS]]

Thanks for a long reply I manage our TSM environment but also SAN space.  
Your comments about charge back, performance stats, and support will be helpful 
there too.

Re the microcode updates: are you Win boxes 2008 or 2008 R2?

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Rhodes, Richard L.
Sent: Friday, January 09, 2015 7:43 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] SAN hardware hints

We use EMC storage.  Most of our TSM databases and disk pools are on VNX/VNX2.  
In general we like them, especially since they came out with the VNX2 - they 
finally have enough processor power to drive the array.  

We use all fat luns.  We have a charge back system for storage and thin 
provisioning doesn't fit well with charge back.  I don't see that it would 
really matter with TSM.  I would think you would fatten out any thin luns 
fairly quickly as you use your pools.  My understanding is that there is a 
small performance hit as you do initial writes as it allocates backend storage, 
but that's a one time hit. We use all raw volumes for disk pools volumes.  If 
you use OS level files for disk pool volumes, don't you have to format them 
first?  That would fatten up any think vols right then!  For DB2 files, thin 
luns would be good since DB2 allocates files as needed.

All your VNX storage will be in a big VNX pool stripped across all the disks, 
so you get lots of spindles/heads working for you.  

We do purchase some SSD storage for Fast Cache on each VNX.  EMC keeps wanting 
us to use VNX FAST VP to migrate hot spots up onto SSD storage, but we've 
stayed away from that.  I believe the slice/chunk size that FAST VP moves is 
256MB.  That's a very large hot spot chunk.   We've been using FAST CACHE - 
just a normal read type cache - that caches in 64k chunks.  This seem a much 
better use of the SSD.

On some VNX2 systems we use snapshots - mostly for databases.  They have a new 
snapshot type that performs a redirect-on-write which supposedly much more 
efficient than the older type which uses copy-on-write. 

What we don't like about the VNX is performance tools.  Yes they have them - 
even give some away free.  But when you start to use them to dig they come up 
lacking.

We've had some problems with some AIX and Windows 2008 systems surviving a 
microcode upgrade.  The upgrade process reboots one SP, then the other.  
There's a gap between the reboots, but sometimes some servers don't recover 
paths before the second SP reboot.  We've been working with support about this, 
but they haven't been exactly responsive.

Support - it's all been moved overseas, and can be anything from good to bad.  
It can be very frustrating.  


Rick














-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Vandeventer, Harold [OITS]
Sent: Thursday, January 08, 2015 3:56 PM
To: ADSM-L@VM.MARIST.EDU
Subject: SAN hardware hints

I've just learned we'll be migrating our systems to new SAN hardware; 
specifically EMC VNX.

A little reading indicates some features such as thin-provisioning vs thick- 
provisioning of LUNs will be available.

Anyone out there using EMC VNX for their TSM storage pools and/or database 
LUNs?  Any hints about thin vs thick regarding TSM performance?

Thanks.


Harold Vandeventer
Systems Programmer
State of Kansas - Office of Information Technology Services STE 751-S
910 SW Jackson
(785) 296-0631


[Confidentiality notice:]
***
This e-mail message, including attachments, if any, is intended for the person 
or entity to which it is addressed and may contain confidential or privileged 
information.  Any unauthorized review, use, or disclosure is prohibited.  If 
you are not the intended recipient, please contact the sender and destroy the 
original message, including all copies, Thank you.
***


-The information contained in this 
message is intended only for the personal and confidential use of the 
recipient(s) named above. If the reader of this message is not the intended 
recipient or an agent responsible for delivering it to the intended recipient, 
you are hereby notified that you have received this document in error and that 
any review, dissemination, distribution, or copying of this message is strictly 
prohibited. If you have received this communication in error, please notify us 
immediately, and delete the original message.

SAN hardware hints

[Vandeventer, Harold [OITS]]

I've just learned we'll be migrating our systems to new SAN hardware; 
specifically EMC VNX.

A little reading indicates some features such as thin-provisioning vs thick- 
provisioning of LUNs will be available.

Anyone out there using EMC VNX for their TSM storage pools and/or database 
LUNs?  Any hints about thin vs thick regarding TSM performance?

Thanks.


Harold Vandeventer
Systems Programmer
State of Kansas - Office of Information Technology Services
STE 751-S
910 SW Jackson
(785) 296-0631


[Confidentiality notice:]
***
This e-mail message, including attachments, if any, is intended for the
person or entity to which it is addressed and may contain confidential
or privileged information.  Any unauthorized review, use, or disclosure
is prohibited.  If you are not the intended recipient, please contact
the sender and destroy the original message, including all copies,
Thank you.
***

Admin Center Login problem

[Vandeventer, Harold [OITS]]

I'm using TSM Admin Center, recent release, 6.3.4.300.  Windows server on the 
back side, browser is Firefox 3.6.28.

It works fairly well, 99% of the time.

Occasionally, I'll click a link in Admin Center and the app seems to lock up.  
Can't get any clicking to work.

This morning, that problem repeated and now, 3 hours later, I still get the 
log out the other user with the same user ID Prompt.

But, that accomplishes nothing.

I can login with a different user account.

Anyone know a trick to get past this problem on my regular AdminCenter account?

Thanks..



Harold Vandeventer
Systems Programmer
State of Kansas - Office of Information Technology Services
STE 751-S
910 SW Jackson
(785) 296-0631


[Confidentiality notice:]
***
This e-mail message, including attachments, if any, is intended for the
person or entity to which it is addressed and may contain confidential
or privileged information.  Any unauthorized review, use, or disclosure
is prohibited.  If you are not the intended recipient, please contact
the sender and destroy the original message, including all copies,
Thank you.
***

Re: Monitoring Agent, 2 on a single TSM Server?

[Vandeventer, Harold [OITS]]

I'm building a new reporting server, and need to keep the current, older 
version, in production for a while.

I also need to get data into the new monitoring server so I can test my custom 
reports and begin collecting historical data for future reporting.  

That lets me simply disable report delivery schedules on the old system and 
enable on the new, without a significant issue.  I don't need the long term 
history from the old server, just several days that would be collected on the 
new system.  

Sounds like my only option is to put multiple local monitoring agents on the 
new system.  Then, when ready to swing production to the new system, delete the 
local agents and upgrade the remote agents on the TSM servers.  The only issue 
would be identical naming of the Agent I suppose.



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Lee 
Miller
Sent: Thursday, October 30, 2014 8:08 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Monitoring Agent, 2 on a single TSM Server?

You can do that on AIX and Linux, by installing the code into different 
directories.  You can't however do that on Windows.

But what issue are you dealing with between the versions?


Lee Miller
Tivoli Storage Manager for System Backup and Recovery Development and IBM 
Tivoli Monitoring for Tivoli Storage Manager
Phone: 817-874-7484



From:   Vandeventer, Harold [OITS] harold.vandeven...@ks.gov
To: ADSM-L@VM.MARIST.EDU
Date:   10/30/2014 03:58 PM
Subject:[ADSM-L] Monitoring Agent, 2 on a single TSM Server?
Sent by:ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU



Is it possible to install two Monitoring Agents on a single TSM server?

My hope: leave the current remote agent that pushes data from TSM 6.3.x to the 
production Monitoring/Reporting/Admin Center server where production reports 
are produced.

But, also install a second Remote Monitoring Agent (related to TSM 7.1.1) on 
that same TSM 6.3 server and configure it to push data to a new 
Monitoring/Reporting server.

This would let me workout the wrinkles in new reporting and continue to use 
Remote Agents, not several local agents.

Alternative, I suppose: create a second local Agent on the new Monitoring 
server and in time delete it, when I upgrade the Remote Agent to the new 
release.

Thanks.


Harold Vandeventer
Systems Programmer
State of Kansas - Office of Information Technology Services STE 751-S
910 SW Jackson
(785) 296-0631


[Confidentiality notice:]
***
This e-mail message, including attachments, if any, is intended for the person 
or entity to which it is addressed and may contain confidential or privileged 
information.  Any unauthorized review, use, or disclosure is prohibited.  If 
you are not the intended recipient, please contact the sender and destroy the 
original message, including all copies, Thank you.
***

Monitoring Agent, 2 on a single TSM Server?

[Vandeventer, Harold [OITS]]

Is it possible to install two Monitoring Agents on a single TSM server?

My hope: leave the current remote agent that pushes data from TSM 6.3.x to the 
production Monitoring/Reporting/Admin Center server where production reports 
are produced.

But, also install a second Remote Monitoring Agent (related to TSM 7.1.1) on 
that same TSM 6.3 server and configure it to push data to a new 
Monitoring/Reporting server.

This would let me workout the wrinkles in new reporting and continue to use 
Remote Agents, not several local agents.

Alternative, I suppose: create a second local Agent on the new Monitoring 
server and in time delete it, when I upgrade the Remote Agent to the new 
release.

Thanks.


Harold Vandeventer
Systems Programmer
State of Kansas - Office of Information Technology Services
STE 751-S
910 SW Jackson
(785) 296-0631


[Confidentiality notice:]
***
This e-mail message, including attachments, if any, is intended for the
person or entity to which it is addressed and may contain confidential
or privileged information.  Any unauthorized review, use, or disclosure
is prohibited.  If you are not the intended recipient, please contact
the sender and destroy the original message, including all copies,
Thank you.
***

Jazz install during TSM 7.1.1 Monitoring install

[Vandeventer, Harold [OITS]]

I'm having trouble with the Jazz 1.1.0.3 install on Windows 2008 R2 SP1.

The error in results.txt refers to a failed os.localhostInHostsFile.

I've tried these lines in the HOSTS file:
IPoftheserver  DSKTAC0P2
IPoftheserver  DSKTAC0P2.Dss.Ks.Gov
IPoftheserver  DSKTAC0P2.dss.ks.gov
IPoftheserver  localhost

None of them seem to match the string that Jazz install is apparently looking 
for.

The value of machine name at the top of results.txt has DSKTAC02P.  Not the 
fully qualified name.

I tried the mixed-case version because a PING command ping command returns that 
mixed-case name.

Anyone having similar trouble, or had it and found the solution?

Thanks.




Harold Vandeventer
Systems Programmer
State of Kansas - Office of Information Technology Services
STE 751-S
910 SW Jackson
(785) 296-0631


[Confidentiality notice:]
***
This e-mail message, including attachments, if any, is intended for the
person or entity to which it is addressed and may contain confidential
or privileged information.  Any unauthorized review, use, or disclosure
is prohibited.  If you are not the intended recipient, please contact
the sender and destroy the original message, including all copies,
Thank you.
***

Script snipet for current hour

[Vandeventer, Harold [OITS]]

Does anyone have a bit of script code that evaluates the current hour when 
the script is running?

Something like
IF SELECT HOUR(CURRENT_TIMESTAMP) FROM LOG  16 GOTO ...

I've poked around ADSM.QuickFacts and see some potential hints.  SELECT 
HOUR(CURRENT_TIMESTAMP) FROM LOG will return the current hour, but I can't get 
an if test to evaluate that hour saved as a script.

My goal: A script runs and it schedules a secondary script to run at a future 
time.

When the secondary script runs, it tests for various conditions (active node 
sessions, reclamation, etc.) and MIGHT reschedule itself for STARTT=NOW+00:15.

But, that secondary script will ideally also test for the time that it started. 
 If the start time is past a given time of day (say 16:00), I want the script 
to skip its intended purpose and delete the schedule that fired it off.

Thanks.


Harold Vandeventer
Systems Programmer
State of Kansas - Office of Information Technology Services
STE 751-S
910 SW Jackson
(785) 296-0631


[Confidentiality notice:]
***
This e-mail message, including attachments, if any, is intended for the
person or entity to which it is addressed and may contain confidential
or privileged information.  Any unauthorized review, use, or disclosure
is prohibited.  If you are not the intended recipient, please contact
the sender and destroy the original message, including all copies,
Thank you.
***

Re: Script snipet for current hour

[Vandeventer, Harold [OITS]]

Thanks... about the time I sent my original post it occurred that I could 
simply create a new schedule, to run at 16:00, that issues delete schedule 
 type=a.

So simple I didn't see the solution.

Thanks again.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Thomas 
Denier
Sent: Tuesday, October 21, 2014 10:29 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Script snipet for current hour

You can run something like:

select database_name from db where hour(current timestamp)16

The return code will be 0 if the hour is greater than 16 and 11 otherwise.

Thomas Denier
Thomas Jefferson University Hospital

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Vandeventer, Harold [OITS]
Sent: Tuesday, October 21, 2014 11:20 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Script snipet for current hour

Does anyone have a bit of script code that evaluates the current hour when 
the script is running?

Something like
IF SELECT HOUR(CURRENT_TIMESTAMP) FROM LOG  16 GOTO ...

I've poked around ADSM.QuickFacts and see some potential hints.  SELECT 
HOUR(CURRENT_TIMESTAMP) FROM LOG will return the current hour, but I can't get 
an if test to evaluate that hour saved as a script.

My goal: A script runs and it schedules a secondary script to run at a future 
time.

When the secondary script runs, it tests for various conditions (active node 
sessions, reclamation, etc.) and MIGHT reschedule itself for STARTT=NOW+00:15.

But, that secondary script will ideally also test for the time that it started. 
 If the start time is past a given time of day (say 16:00), I want the script 
to skip its intended purpose and delete the schedule that fired it off.
The information contained in this transmission contains privileged and 
confidential information. It is intended only for the use of the person named 
above. If you are not the intended recipient, you are hereby notified that any 
review, dissemination, distribution or duplication of this communication is 
strictly prohibited. If you are not the intended recipient, please contact the 
sender by reply email and destroy all copies of the original message.

CAUTION: Intended recipients should NOT use email communication for emergent or 
urgent health care matters.

[Confidentiality notice:]
***
This e-mail message, including attachments, if any, is intended for the
person or entity to which it is addressed and may contain confidential
or privileged information.  Any unauthorized review, use, or disclosure
is prohibited.  If you are not the intended recipient, please contact
the sender and destroy the original message, including all copies,
Thank you.
***

Node Sessions cancelled issue

[Vandeventer, Harold [OITS]]

I am seeing an occasional ANS1369E Session Rejected: The session was canceled 
by the server administrator. in the nodes DSMSCHED.LOG file.

At least two nodes have seen the trouble, I've not yet asked if others see it.

They seem occur at random times during the backup window, but not every 
evening.  Most backup is fine, but 1 or 2 a week for these two nodes; some 
weeks none.

Looking at the Activity log I do not see any CANCEL SESSIONS nor DISABLE 
SESSIONS around the same times.  Those commands are issued a few hours later in 
early morning and would impact all backup activity.

The Activity log is recording the end of backup statistics for a given backup; 
but the dsmsched.log recorded the statistics, followed by the ANS1369E.

It seems like the backup finished, any guesses what would raise the ANS1369E?

Thanks.






Harold Vandeventer
Systems Programmer
State of Kansas - Office of Information Technology Services
STE 751-S
910 SW Jackson
(785) 296-0631


[Confidentiality notice:]
***
This e-mail message, including attachments, if any, is intended for the
person or entity to which it is addressed and may contain confidential
or privileged information.  Any unauthorized review, use, or disclosure
is prohibited.  If you are not the intended recipient, please contact
the sender and destroy the original message, including all copies,
Thank you.
***

Re: tsm archive log full, causes repeated backups

[Vandeventer, Harold [OITS]]

Can you create the ARCHFAILOVERLOGDirectory?

That would give you additional space without moving your current files from 
ARCHIVELOG to the new volume.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Tim 
Brown
Sent: Tuesday, August 26, 2014 11:57 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] tsm archive log full, causes repeated backups

Since it appears that my archive log drive is full, I found the steps to follow 
relocate to larger drive.

Create an new archive log directory.
Update the dsmserv.opt option file for the new archive log directory.
Halt and restart the server.
Move the archive logs from the old directory to the new directory. Preserve any 
subdirectory structure. Use and verify a recursive copy directory command.


By doing this , after the server restarts and before moving the archive logs 
wont the backup still continue.

Tim

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Rhodes, Richard L.
Sent: Tuesday, 26 August, 2014 12:26 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] tsm archive log full, causes repeated backups

Cound something wrong with your archive log filesystem?  Might it be unmounted 
or something?

Rick



-Original Message-
From: ADSM: Dist Stor Manager 
[https://urldefense.proofpoint.com/v1/url?u=http://mailto:ADSM-L%40VM.MARIST.EDUk=pCpgOv%2FKLW5dYRss05kLEw%3D%3D%0Ar=tQq0J85k4w4CeO1cI0sWanGhPyb3Fq7EC6ctgNHLxNs%3D%0Am=wLQwo6jEM4gBohY6PaUggUKrw4TZKeuDMgOs7FtRQdQ%3D%0As=37a9c6f9d2e7c472c894e68ee88ab04eb74a4c87016a83326c058eb0e36cd30d]
 On Behalf Of Tim Brown
Sent: Tuesday, August 26, 2014 12:13 PM
To: ADSM-L@VM.MARIST.EDUmailto:ADSM-L@VM.MARIST.EDU
Subject: Re: tsm archive log full, causes repeated backups

There have actually been 5 backups completed  in a row since server was started 
all with success! ?

All started due to ANR0299I A full database backup will be started.  The 
archive log space used is 99 % and the archive log space used threshold is  80 
percent.


Tim

-Original Message-
From: ADSM: Dist Stor Manager 
[https://urldefense.proofpoint.com/v1/url?u=http://mailto:ADSM-L%40VM.MARIST.EDUk=pCpgOv%2FKLW5dYRss05kLEw%3D%3D%0Ar=tQq0J85k4w4CeO1cI0sWanGhPyb3Fq7EC6ctgNHLxNs%3D%0Am=wLQwo6jEM4gBohY6PaUggUKrw4TZKeuDMgOs7FtRQdQ%3D%0As=37a9c6f9d2e7c472c894e68ee88ab04eb74a4c87016a83326c058eb0e36cd30d]
 On Behalf Of Prather, Wanda
Sent: Tuesday, 26 August, 2014 12:05 PM
To: ADSM-L@VM.MARIST.EDUmailto:ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] tsm archive log full, causes repeated backups

That usually means your activity log is enormous!  :) But restarting the 
server would have killed any reorg or pinning transaction.

Try 2 db backups in a row now, your archive log should clear.

W

-Original Message-
From: ADSM: Dist Stor Manager 
[https://urldefense.proofpoint.com/v1/url?u=http://mailto:ADSM-L%40VM.MARIST.EDUk=pCpgOv%2FKLW5dYRss05kLEw%3D%3D%0Ar=tQq0J85k4w4CeO1cI0sWanGhPyb3Fq7EC6ctgNHLxNs%3D%0Am=59fjuhngA9cOaKKoSEEx7QKvB8n8WS8AJcQc7dKkvOg%3D%0As=b9b987e96026d7ceb61565c822db7a14a1f95296ced725cff1999c4c0687b4eb]
 On Behalf Of Tim Brown
Sent: Tuesday, August 26, 2014 11:32 AM
To: ADSM-L@VM.MARIST.EDUmailto:ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] tsm archive log full, causes repeated backups

I had even restarted the tsm server today

If I enter with just =today it comes right back If I enter with today-1 the 
query hangs

Tim

-Original Message-
From: ADSM: Dist Stor Manager 
[https://urldefense.proofpoint.com/v1/url?u=http://mailto:ADSM-L%40VM.MARIST.EDUk=pCpgOv%2FKLW5dYRss05kLEw%3D%3D%0Ar=tQq0J85k4w4CeO1cI0sWanGhPyb3Fq7EC6ctgNHLxNs%3D%0Am=59fjuhngA9cOaKKoSEEx7QKvB8n8WS8AJcQc7dKkvOg%3D%0As=b9b987e96026d7ceb61565c822db7a14a1f95296ced725cff1999c4c0687b4eb]
 On Behalf Of Prather, Wanda
Sent: Tuesday, 26 August, 2014 11:16 AM
To: ADSM-L@VM.MARIST.EDUmailto:ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] tsm archive log full, causes repeated backups

You could have a reorg running and pinning the log.

Try:  q actlog begindate=today-2 search=reorg

-Original Message-
From: ADSM: Dist Stor Manager 
[https://urldefense.proofpoint.com/v1/url?u=http://mailto:ADSM-L%40VM.MARIST.EDUk=pCpgOv%2FKLW5dYRss05kLEw%3D%3D%0Ar=tQq0J85k4w4CeO1cI0sWanGhPyb3Fq7EC6ctgNHLxNs%3D%0Am=QJwU6pc4k02OIaQLlHzQMrXul8%2BYJojUNnuh%2Fs91wxo%3D%0As=a65decc3894f7c9fae1a61e6b2087a6511ffef0e590b9e0aa9b8acbbf7846978]
 On Behalf Of Tim Brown
Sent: Tuesday, August 26, 2014 11:10 AM
To: ADSM-L@VM.MARIST.EDUmailto:ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] tsm archive log full, causes repeated backups

6.3.1

Tim

-Original Message-
From: ADSM: Dist Stor Manager 
[https://urldefense.proofpoint.com/v1/url?u=http://mailto:ADSM-L%40VM.MARIST.EDUk=pCpgOv%2FKLW5dYRss05kLEw%3D%3D%0Ar=tQq0J85k4w4CeO1cI0sWanGhPyb3Fq7EC6ctgNHLxNs%3D%0Am=QJwU6pc4k02OIaQLlHzQMrXul8%2BYJojUNnuh%2Fs91wxo%3D%0As=a65decc3894f7c9fae1a61e6b2087a6511ffef0e590b9e0aa9b8acbbf7846978]
 On Behalf 

Re: tsm archive log full, causes repeated backups

[Vandeventer, Harold [OITS]]

I lean to your halt system, move folder approach.

Dangerous to have a full C: drive I suspect; Windows won't be happy trying to 
do anything on a full boot disk.  

You'll have better luck giving Windows room to do its work; while letting TSM 
deal with the new x:\ path.



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Tim 
Brown
Sent: Tuesday, August 26, 2014 12:24 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] tsm archive log full, causes repeated backups

There is one on another drive that is full , OOPS C:

c:\tsmarchlogfailover

If I create a new one on a new drive  x:\tsmarchlogfailover and update 
dsmserv.opt will it eventually free up the files on c:

never realized it was on C: to begin with, have had this environment for over 2 
years

Or Is it better to

Halt system
Move c:\tsmarchlogfailover to x:\tsmarchlogfailover with windows copying
Update dsmserv.opt to ARCHFAILOVERLOGDirectoryx:\tsmarchlogfailover
Restart TSM

Tim


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Vandeventer, Harold [OITS]
Sent: Tuesday, 26 August, 2014 1:09 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] tsm archive log full, causes repeated backups

Can you create the ARCHFAILOVERLOGDirectory?

That would give you additional space without moving your current files from 
ARCHIVELOG to the new volume.

-Original Message-
From: ADSM: Dist Stor Manager 
[https://urldefense.proofpoint.com/v1/url?u=http://mailto:ADSM-L%40VM.MARIST.EDUk=pCpgOv%2FKLW5dYRss05kLEw%3D%3D%0Ar=tQq0J85k4w4CeO1cI0sWanGhPyb3Fq7EC6ctgNHLxNs%3D%0Am=wa93BxyEvkOqRkwWlA4IOnrE6sLSsibrrmWz%2FIk7bwQ%3D%0As=c7c5ea195c1c97a6797c0a13b9eca8d3101c70631667dc56a1859cf2ed67133f]
 On Behalf Of Tim Brown
Sent: Tuesday, August 26, 2014 11:57 AM
To: ADSM-L@VM.MARIST.EDUmailto:ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] tsm archive log full, causes repeated backups

Since it appears that my archive log drive is full, I found the steps to follow 
relocate to larger drive.

Create an new archive log directory.
Update the dsmserv.opt option file for the new archive log directory.
Halt and restart the server.
Move the archive logs from the old directory to the new directory. Preserve any 
subdirectory structure. Use and verify a recursive copy directory command.


By doing this , after the server restarts and before moving the archive logs 
wont the backup still continue.

Tim

-Original Message-
From: ADSM: Dist Stor Manager 
[https://urldefense.proofpoint.com/v1/url?u=http://mailto:ADSM-L%40VM.MARIST.EDUk=pCpgOv%2FKLW5dYRss05kLEw%3D%3D%0Ar=tQq0J85k4w4CeO1cI0sWanGhPyb3Fq7EC6ctgNHLxNs%3D%0Am=wa93BxyEvkOqRkwWlA4IOnrE6sLSsibrrmWz%2FIk7bwQ%3D%0As=c7c5ea195c1c97a6797c0a13b9eca8d3101c70631667dc56a1859cf2ed67133f]
 On Behalf Of Rhodes, Richard L.
Sent: Tuesday, 26 August, 2014 12:26 PM
To: ADSM-L@VM.MARIST.EDUmailto:ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] tsm archive log full, causes repeated backups

Cound something wrong with your archive log filesystem?  Might it be unmounted 
or something?

Rick



-Original Message-
From: ADSM: Dist Stor Manager 
[https://urldefense.proofpoint.com/v1/url?u=http://mailto:ADSM-L%40VM.MARIST.EDUk=pCpgOv%2FKLW5dYRss05kLEw%3D%3D%0Ar=tQq0J85k4w4CeO1cI0sWanGhPyb3Fq7EC6ctgNHLxNs%3D%0Am=wLQwo6jEM4gBohY6PaUggUKrw4TZKeuDMgOs7FtRQdQ%3D%0As=37a9c6f9d2e7c472c894e68ee88ab04eb74a4c87016a83326c058eb0e36cd30d]
 On Behalf Of Tim Brown
Sent: Tuesday, August 26, 2014 12:13 PM
To: 
ADSM-L@VM.MARIST.EDUhttps://urldefense.proofpoint.com/v1/url?u=http://mailto:ADSM-L%40VM.MARIST.EDUk=pCpgOv%2FKLW5dYRss05kLEw%3D%3D%0Ar=tQq0J85k4w4CeO1cI0sWanGhPyb3Fq7EC6ctgNHLxNs%3D%0Am=wa93BxyEvkOqRkwWlA4IOnrE6sLSsibrrmWz%2FIk7bwQ%3D%0As=c7c5ea195c1c97a6797c0a13b9eca8d3101c70631667dc56a1859cf2ed67133fmailto:ADSM-L@VM.MARIST.EDUhttps://urldefense.proofpoint.com/v1/url?u=http://mailto:ADSM-L%40VM.MARIST.EDUk=pCpgOv%2FKLW5dYRss05kLEw%3D%3D%0Ar=tQq0J85k4w4CeO1cI0sWanGhPyb3Fq7EC6ctgNHLxNs%3D%0Am=wa93BxyEvkOqRkwWlA4IOnrE6sLSsibrrmWz%2FIk7bwQ%3D%0As=c7c5ea195c1c97a6797c0a13b9eca8d3101c70631667dc56a1859cf2ed67133f
Subject: Re: tsm archive log full, causes repeated backups

There have actually been 5 backups completed  in a row since server was started 
all with success! ?

All started due to ANR0299I A full database backup will be started.  The 
archive log space used is 99 % and the archive log space used threshold is  80 
percent.


Tim

-Original Message-
From: ADSM: Dist Stor Manager 
[https://urldefense.proofpoint.com/v1/url?u=http://mailto:ADSM-L%40VM.MARIST.EDUk=pCpgOv%2FKLW5dYRss05kLEw%3D%3D%0Ar=tQq0J85k4w4CeO1cI0sWanGhPyb3Fq7EC6ctgNHLxNs%3D%0Am=wLQwo6jEM4gBohY6PaUggUKrw4TZKeuDMgOs7FtRQdQ%3D%0As=37a9c6f9d2e7c472c894e68ee88ab04eb74a4c87016a83326c058eb0e36cd30d]
 On Behalf Of Prather, Wanda
Sent: Tuesday, 26 August, 2014 12:05 PM
To: 
ADSM-L@VM.MARIST.EDUhttps://urldefense.proofpoint.com/v1/url?u=http://mailto:ADSM-L%40VM.MARIST.EDUk

Re: tsm archive log full, causes repeated backups

[Vandeventer, Harold [OITS]]

Your TSM service account has appropriate permissions on J:\tsm\   

It looks like a failure to deal with a move/copy from I: to J:.

I've not looked at ADM1848W yet.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Tim 
Brown
Sent: Tuesday, August 26, 2014 1:38 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] tsm archive log full, causes repeated backups

Server does not stay up!!


2014-08-26-14.37.09.781000   Instance:SERVER1   Node:000
PID:8188(db2syscs.exe)   TID:12844   Appid:none
data protection services  sqlpgArchiveLogFile Probe:3150 

ADM1848W  Failed to archive log file S0102568.LOG to 
J:\tsm\archlog\archmeth1\SERVER1\TSMDB1\NODE\C000\ from I:\tsm\log\.
 

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Vandeventer, Harold [OITS]
Sent: Tuesday, 26 August, 2014 2:20 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] tsm archive log full, causes repeated backups

I lean to your halt system, move folder approach.

Dangerous to have a full C: drive I suspect; Windows won't be happy trying to 
do anything on a full boot disk.  

You'll have better luck giving Windows room to do its work; while letting TSM 
deal with the new x:\ path.



-Original Message-
From: ADSM: Dist Stor Manager 
[https://urldefense.proofpoint.com/v1/url?u=http://mailto:ADSM-L%40VM.MARIST.EDUk=pCpgOv%2FKLW5dYRss05kLEw%3D%3D%0Ar=tQq0J85k4w4CeO1cI0sWanGhPyb3Fq7EC6ctgNHLxNs%3D%0Am=Rveuv9wfhvxes5bW3Vceme%2FE5xpU4rGtsaHlis93bkY%3D%0As=a8fccf485976041a5944375b4dad8fab77e7f224babc60c0ce739ab7422886f6]
 On Behalf Of Tim Brown
Sent: Tuesday, August 26, 2014 12:24 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] tsm archive log full, causes repeated backups

There is one on another drive that is full , OOPS C:

c:\tsmarchlogfailover

If I create a new one on a new drive  x:\tsmarchlogfailover and update 
dsmserv.opt will it eventually free up the files on c:

never realized it was on C: to begin with, have had this environment for over 2 
years

Or Is it better to

Halt system
Move c:\tsmarchlogfailover to x:\tsmarchlogfailover with windows copying
Update dsmserv.opt to ARCHFAILOVERLOGDirectoryx:\tsmarchlogfailover
Restart TSM

Tim


-Original Message-
From: ADSM: Dist Stor Manager 
[https://urldefense.proofpoint.com/v1/url?u=http://mailto:ADSM-L%40VM.MARIST.EDUk=pCpgOv%2FKLW5dYRss05kLEw%3D%3D%0Ar=tQq0J85k4w4CeO1cI0sWanGhPyb3Fq7EC6ctgNHLxNs%3D%0Am=Rveuv9wfhvxes5bW3Vceme%2FE5xpU4rGtsaHlis93bkY%3D%0As=a8fccf485976041a5944375b4dad8fab77e7f224babc60c0ce739ab7422886f6]
 On Behalf Of Vandeventer, Harold [OITS]
Sent: Tuesday, 26 August, 2014 1:09 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] tsm archive log full, causes repeated backups

Can you create the ARCHFAILOVERLOGDirectory?

That would give you additional space without moving your current files from 
ARCHIVELOG to the new volume.

-Original Message-
From: ADSM: Dist Stor Manager 
[https://urldefense.proofpoint.com/v1/url?u=http://mailto:ADSM-L%40VM.MARIST.EDUk=pCpgOv%2FKLW5dYRss05kLEw%3D%3D%0Ar=tQq0J85k4w4CeO1cI0sWanGhPyb3Fq7EC6ctgNHLxNs%3D%0Am=wa93BxyEvkOqRkwWlA4IOnrE6sLSsibrrmWz%2FIk7bwQ%3D%0As=c7c5ea195c1c97a6797c0a13b9eca8d3101c70631667dc56a1859cf2ed67133f]
 On Behalf Of Tim Brown
Sent: Tuesday, August 26, 2014 11:57 AM
To: 
ADSM-L@VM.MARIST.EDUhttps://urldefense.proofpoint.com/v1/url?u=http://mailto:ADSM-L%40VM.MARIST.EDUk=pCpgOv%2FKLW5dYRss05kLEw%3D%3D%0Ar=tQq0J85k4w4CeO1cI0sWanGhPyb3Fq7EC6ctgNHLxNs%3D%0Am=Rveuv9wfhvxes5bW3Vceme%2FE5xpU4rGtsaHlis93bkY%3D%0As=a8fccf485976041a5944375b4dad8fab77e7f224babc60c0ce739ab7422886f6
Subject: Re: [ADSM-L] tsm archive log full, causes repeated backups

Since it appears that my archive log drive is full, I found the steps to follow 
relocate to larger drive.

Create an new archive log directory.
Update the dsmserv.opt option file for the new archive log directory.
Halt and restart the server.
Move the archive logs from the old directory to the new directory. Preserve any 
subdirectory structure. Use and verify a recursive copy directory command.


By doing this , after the server restarts and before moving the archive logs 
wont the backup still continue.

Tim

-Original Message-
From: ADSM: Dist Stor Manager 
[https://urldefense.proofpoint.com/v1/url?u=http://mailto:ADSM-L%40VM.MARIST.EDUk=pCpgOv%2FKLW5dYRss05kLEw%3D%3D%0Ar=tQq0J85k4w4CeO1cI0sWanGhPyb3Fq7EC6ctgNHLxNs%3D%0Am=wa93BxyEvkOqRkwWlA4IOnrE6sLSsibrrmWz%2FIk7bwQ%3D%0As=c7c5ea195c1c97a6797c0a13b9eca8d3101c70631667dc56a1859cf2ed67133f]
 On Behalf Of Rhodes, Richard L.
Sent: Tuesday, 26 August, 2014 12:26 PM
To: 
ADSM-L@VM.MARIST.EDUhttps://urldefense.proofpoint.com/v1/url?u=http://mailto:ADSM-L%40VM.MARIST.EDUk=pCpgOv%2FKLW5dYRss05kLEw%3D%3D%0Ar=tQq0J85k4w4CeO1cI0sWanGhPyb3Fq7EC6ctgNHLxNs%3D%0Am=Rveuv9wfhvxes5bW3Vceme%2FE5xpU4rGtsaHlis93bkY%3D%0As=a8fccf485976041a5944375b4dad8fab77e7f224babc60c0ce739ab7422886f6
Subject: Re

Re: tsm archive log full, causes repeated backups

[Vandeventer, Harold [OITS]]

I don't find an ADM1848W message in TSM messages.

Anything in Windows Event Log?

Can you set the TSM service to not auto-start, boot the server, then login on 
the console and try a foreground start of TSM?

You'd see the live log messages appear in that console window.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Tim 
Brown
Sent: Tuesday, August 26, 2014 1:53 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] tsm archive log full, causes repeated backups

I and J were there from before, I just added o:\tsmarchlogfailover and updated 
its security To be same as I and J

Still fails!

Tim

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Vandeventer, Harold [OITS]
Sent: Tuesday, 26 August, 2014 2:43 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] tsm archive log full, causes repeated backups

Your TSM service account has appropriate permissions on J:\tsm\   

It looks like a failure to deal with a move/copy from I: to J:.

I've not looked at ADM1848W yet.

-Original Message-
From: ADSM: Dist Stor Manager 
[https://urldefense.proofpoint.com/v1/url?u=http://mailto:ADSM-L%40VM.MARIST.EDUk=pCpgOv%2FKLW5dYRss05kLEw%3D%3D%0Ar=tQq0J85k4w4CeO1cI0sWanGhPyb3Fq7EC6ctgNHLxNs%3D%0Am=ME1i88Kh0C%2FpdlqzlDH7Qe0lQVUx%2FvOnA93xeGZCf1c%3D%0As=a674a0142797528c922793fb86fce66015a3b1cf9e92b2635a73ab9081f58096]
 On Behalf Of Tim Brown
Sent: Tuesday, August 26, 2014 1:38 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] tsm archive log full, causes repeated backups

Server does not stay up!!


2014-08-26-14.37.09.781000   Instance:SERVER1   Node:000
PID:8188(db2syscs.exe)   TID:12844   Appid:none
data protection services  sqlpgArchiveLogFile Probe:3150 

ADM1848W  Failed to archive log file S0102568.LOG to 
J:\tsm\archlog\archmeth1\SERVER1\TSMDB1\NODE\C000\ from I:\tsm\log\.
 

-Original Message-
From: ADSM: Dist Stor Manager 
[https://urldefense.proofpoint.com/v1/url?u=http://mailto:ADSM-L%40VM.MARIST.EDUk=pCpgOv%2FKLW5dYRss05kLEw%3D%3D%0Ar=tQq0J85k4w4CeO1cI0sWanGhPyb3Fq7EC6ctgNHLxNs%3D%0Am=ME1i88Kh0C%2FpdlqzlDH7Qe0lQVUx%2FvOnA93xeGZCf1c%3D%0As=a674a0142797528c922793fb86fce66015a3b1cf9e92b2635a73ab9081f58096]
 On Behalf Of Vandeventer, Harold [OITS]
Sent: Tuesday, 26 August, 2014 2:20 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] tsm archive log full, causes repeated backups

I lean to your halt system, move folder approach.

Dangerous to have a full C: drive I suspect; Windows won't be happy trying to 
do anything on a full boot disk.  

You'll have better luck giving Windows room to do its work; while letting TSM 
deal with the new x:\ path.



-Original Message-
From: ADSM: Dist Stor Manager 
[https://urldefense.proofpoint.com/v1/url?u=http://mailto:ADSM-L%40VM.MARIST.EDUk=pCpgOv%2FKLW5dYRss05kLEw%3D%3D%0Ar=tQq0J85k4w4CeO1cI0sWanGhPyb3Fq7EC6ctgNHLxNs%3D%0Am=Rveuv9wfhvxes5bW3Vceme%2FE5xpU4rGtsaHlis93bkY%3D%0As=a8fccf485976041a5944375b4dad8fab77e7f224babc60c0ce739ab7422886f6]
 On Behalf Of Tim Brown
Sent: Tuesday, August 26, 2014 12:24 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] tsm archive log full, causes repeated backups

There is one on another drive that is full , OOPS C:

c:\tsmarchlogfailover

If I create a new one on a new drive  x:\tsmarchlogfailover and update 
dsmserv.opt will it eventually free up the files on c:

never realized it was on C: to begin with, have had this environment for over 2 
years

Or Is it better to

Halt system
Move c:\tsmarchlogfailover to x:\tsmarchlogfailover with windows copying
Update dsmserv.opt to ARCHFAILOVERLOGDirectoryx:\tsmarchlogfailover
Restart TSM

Tim


-Original Message-
From: ADSM: Dist Stor Manager 
[https://urldefense.proofpoint.com/v1/url?u=http://mailto:ADSM-L%40VM.MARIST.EDUk=pCpgOv%2FKLW5dYRss05kLEw%3D%3D%0Ar=tQq0J85k4w4CeO1cI0sWanGhPyb3Fq7EC6ctgNHLxNs%3D%0Am=Rveuv9wfhvxes5bW3Vceme%2FE5xpU4rGtsaHlis93bkY%3D%0As=a8fccf485976041a5944375b4dad8fab77e7f224babc60c0ce739ab7422886f6]
 On Behalf Of Vandeventer, Harold [OITS]
Sent: Tuesday, 26 August, 2014 1:09 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] tsm archive log full, causes repeated backups

Can you create the ARCHFAILOVERLOGDirectory?

That would give you additional space without moving your current files from 
ARCHIVELOG to the new volume.

-Original Message-
From: ADSM: Dist Stor Manager 
[https://urldefense.proofpoint.com/v1/url?u=http://mailto:ADSM-L%40VM.MARIST.EDUk=pCpgOv%2FKLW5dYRss05kLEw%3D%3D%0Ar=tQq0J85k4w4CeO1cI0sWanGhPyb3Fq7EC6ctgNHLxNs%3D%0Am=wa93BxyEvkOqRkwWlA4IOnrE6sLSsibrrmWz%2FIk7bwQ%3D%0As=c7c5ea195c1c97a6797c0a13b9eca8d3101c70631667dc56a1859cf2ed67133f]
 On Behalf Of Tim Brown
Sent: Tuesday, August 26, 2014 11:57 AM
To: 
ADSM-L@VM.MARIST.EDUhttps://urldefense.proofpoint.com/v1/url?u=http://mailto:ADSM-L%40VM.MARIST.EDUk=pCpgOv%2FKLW5dYRss05kLEw%3D%3D%0Ar=tQq0J85k4w4CeO1cI0sWanGhPyb3Fq7EC6ctgNHLxNs%3D%0Am