Re: v6.3.5 backup/restore question

[Sheridan, Peter T.]

I have successfully restored a 6.3.5 server with BA client version 7.1.0 ? Are 
u sure the BA client matches between prod server and DR server ? What error 
messages you getting ?  

Peter Sheridan
CUNA Mutual Group 
608-577-0539
peter.sheri...@cunamutual.com

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Rhodes, Richard L.
Sent: Thursday, May 12, 2016 9:37 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] v6.3.5 backup/restore question

We've been trying to restore a v6.3.5 TSM server onto a DR server with no 
success.

The PROD server is TSM v6.3.5 but the BA client is v7.1.4.
The DR serve is the same, TSM v6.3.5 with BA client v7.1.4.
Is this allowed?  Doesn't the API client have to match the TSM server level?

Thanks

Rick







-

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.

Version of TSM for VE

[Sheridan, Peter T.]

I am currently running TSM server version 6.3.5 and was wondering what version 
of TSM for VE I should use seeing I am just starting out with the product. I 
was also wondering if anybody has written a quick guide of steps as some of the 
online documentation can be confusing. 

Thanks Pete

Peter Sheridan
CUNA Mutual Group 
608-577-0539
peter.sheri...@cunamutual.com

Re: Move node to new domain

[Sheridan, Peter T.]

Another wild guess and doubt it will matter but if you do q filespace on the 
node do u see orphaned filespaces that you might be able to delete and clean 
things up ? 

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of Tim 
Brown
Sent: Tuesday, August 20, 2013 10:55 AM
To: ADSM-L@vm.marist.edu
Subject: Re: [ADSM-L] Move node to new domain

Yes still seeing orphaned references

Tim

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Ehresman,David E.
Sent: Tuesday, 20 August, 2013 11:31 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Move node to new domain

Tim,

Have you done an "audit vol XXX fix=yes" on the volumes in question?  That 
should fix discrepancies between TSM tables

David

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Nick 
Laflamme
Sent: Tuesday, August 20, 2013 11:07 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Move node to new domain

The most alarming thing I see about Tim's question is the discrepancy between Q 
NODEDATA and Q CONTENT. Q NODEDATA says that there's data for that user in that 
volume; Q CONTENT contradicts that. He doesn't show the full output of the Q 
CONTENT command, but if what he says is true, I'd suggest he open a PMR.

Note that none of that has anything to do with changing which policy domain a 
node is assigned to. :-)

Nick


2013/8/20 Tim Brown 

> I am having difficulty sending to adsm-l so if you already got this 
> please ignore!
>
>
>
>
>
> We recently moved a node from domain dm1  to domain dm2  but are still 
> seeing nodedata references in dm1 that we cant remove.
>
>
>
> If we issue Q CONTENT D:\DM1_PRIM1\0001EAD4.BFS   >0001EAD4.TXT
> theres not any references to node NODE1 in the resulting txt file.
>
>
>
> How can we resolve this ?
>
>
>
> Q NODEDATA NODE1
>
>
>
> Node NameVolume NameStorage Pool
>   Physical
>
> Name
>Space
>
>
>Occupied
>
>
>  (MB)
>
>  -- 
>   
>
>
>
>
>
> NODE1 D:\DM1_PRIM1\0001EAD4.BFS  DM1_PRIM
> 0.02
>
> NODE1D:\DM1_PRIM2\000165B3.BFS  DM1_PRIM
>   0.11
>
> NODE1D:\DM1_PRIM2\0001EA8D.BFS  DM1_PRIM
>  128.83
>
>
>
> NODE1 M:\DM2_PRIM1\00017F02.BFS  DM2_PRIM
> 11,138.03
>
> NODE1 M:\DM2_PRIM1\000180C5.BFS  DM2_PRIM
>  148.23
>
> NODE1 M:\DM2_PRIM1\000180C6.BFS  DM2_PRIM
>  889.02
>
> NODE1M:\DM2_PRIM1\000180C7.BFS  DM2_PRIM
>434.84
>
> NODE1   M:\DM2_PRIM1\000184AD.BFS  DM2_PRIM
>   1,070.09
>
> NODE1 M:\DM2_PRIM1\000184B5.BFS  DM2_PRIM
>   0.45
>
> NODE1 M:\DM2_PRIM1\00018A84.BFS  DM2_PRIM
>  294.61
>
> NODE1M:\DM2_PRIM1\00019714.BFS  DM2_PRIM
>918.17
>
> NODE1  M:\DM2_PRIM1\00019785.BFS  DM2_PRIM
>  413.25
>
> NODE1M:\DM2_PRIM1\00019C9D.BFS  DM2_PRIM
>531.94
>
> NODE1 M:\DM2_PRIM1\0001A9D5.BFS  DM2_PRIM
>  527.01
>
> NODE1 M:\DM2_PRIM1\0001B9F8.BFS  DM2_PRIM
>  510.82
>
> NODE1M:\DM2_PRIM1\0001BB2B.BFS  DM2_PRIM
>   1,555.39
>
> NODE1  M:\DM2_PRIM1\0001BB2C.BFS  DM2_PRIM
>  324.95
>
> NODE1  M:\DM2_PRIM1\0001BF76.BFS  DM2_PRIM
> 1,029.69
>
> NODE1 M:\DM2_PRIM1\0001CA6A.BFS  DM2_PRIM
>  816.66
>
> NODE1   M:\DM2_PRIM1\0001D165.BFS  DM2_PRIM
>331.11
>
> NODE1M:\DM2_PRIM1\0001DE62.BFS  DM2_PRIM
>   1,141.98
>
> NODE1   M:\DM2_PRIM1\0001E9B9.BFS  DM2_PRIM
>67.84
>
>
>
>
>
>
>
> Thanks,
>
>
>
> Tim Brown
>
> Supervisor Computer Operations
>
> Central Hudson Gas & Electric
>

Re: TDP for Exchange 2010 DAG full database backup experiencing intermittent failures

[Sheridan, Peter T.]

Our company had the exact same issues and eventually we gave up and decided to 
not run them in parallel. We did decide to add the /skipintegritycheck flag to 
the backups which basically cut the backup times in half.  This flag, however, 
will not do any integrity checks but we were willing to take the risks.

We are also experiencing VSS issues from time to time and have not been able to 
find  a resolution. Another banging head against the wall for many months with 
no answers from either IBM or Microsoft support.  IBM support has been really 
good I must admit but getting help from the Microsoft side has been almost 
impossible.  Basically, if we have VSS issues we re-run the backups manually 
the next day.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of Del 
Hoobler
Sent: Thursday, July 25, 2013 8:31 AM
To: ADSM-L@vm.marist.edu
Subject: Re: [ADSM-L] TDP for Exchange 2010 DAG full database backup 
experiencing intermittent failures

Hi Steve,

Have you checked to make sure that none of the parallel backup sessions are 
snapping the same volumes? If so, these cannot overlap at all.
Also, are you using multiple CAD/AGENTS or just one? Using multiple could cause 
conflicts because they do not coordinate with each other.
You could try adding more time (30 minutes) between the launch of the sessions.

The Event Log entries below do concern me as it seems that VSS itself is having 
issues. If VSS does not clean up correctly, it can block subsequent VSS 
operations.

If possible, reboot the server and take a look at this:

   http://technet.microsoft.com/en-us/library/ee264216%28WS.10%29.aspx

If you continue to have issues, a PMR is probably the next step.

Thanks,

Del



"ADSM: Dist Stor Manager"  wrote on 07/25/2013
06:43:47 AM:

> From: "Schaub, Steve" 
> To: ADSM-L@vm.marist.edu,
> Date: 07/25/2013 06:44 AM
> Subject: Re: TDP for Exchange 2010 DAG full database backup 
> experiencing intermittent failures Sent by: "ADSM: Dist Stor Manager" 
> 
>
> Ray,
> I changed the timer to 11 minutes per your note, but still seeing
failures.
> Thanks,
> -steve
>
> -Original Message-
> From: Storer, Raymond [mailto:stor...@nibco.com]
> Sent: Tuesday, July 23, 2013 1:24 PM
> To: ADSM: Dist Stor Manager
> Cc: Schaub, Steve
> Subject: RE: [ADSM-L] TDP for Exchange 2010 DAG full database backup 
> experiencing intermittent failures
>
> Steve, according to the link below parallel backups are supported; 
> however, you should allow a minimum of ten minutes between backups.
>
> http://pic.dhe.ibm.com/infocenter/tsminfo/v6r4/topic/
> com.ibm.itsm.mail.exc.doc/c_dpfcm_bup_vssplan_exc.html
>
>
> Ray Storer
> NIBCO INC.
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf 
> Of Schaub, Steve
> Sent: Tuesday, July 23, 2013 11:27 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: [ADSM-L] TDP for Exchange 2010 DAG full database backup 
> experiencing intermittent failures
>
> Exchange 2010 w/DAG
> Tsm server 6.2.4
> Tsm client 6.4.0.0
> Tdp client 6.4.0.0
>
> The script that runs our nightly full backups is having intermittent 
> failures.  Different servers, different databases each night, but all 
> the failures have the same API error message.  The way the powershell 
> script works on each server is to perform a full db backup of a 
> different set of databases each night (so even though it runs nightly, 
> they are actually weekly fulls).  The backups are run as Powershell 
> jobs, in order to enable multiple backup concurrency (currently set to 
> a max of 4 concurrent backup jobs).  The script waits 2 minutes after 
> each job is submitted before running the next job in order to give the 
> snapshot time to complete.  Some nights everything works, some nights 
> 1 failure, some 2, 3, etc.  There are some VSS errors in the event 
> log, but according to the TSM logs, the snapshot was successful?
>
> Are there any issues with running concurrent TDP backups on 6.4.0.0?
> Here are all the pertinent logs:
>
> tdperror.log
> 07/22/2013 20:17:38 ANS1235E An unknown system error has occurred from 
> which TSM cannot recover.
> 07/22/2013 20:23:48 ANS1909E The scheduled command failed.
> 07/22/2013 20:23:48 ANS1512E Scheduled event 'EXCHANGE2010_FULL'
> failed.  Return code = 1.
>
> BkupExchange2010_Full_Day22.log
> IBM Tivoli Storage Manager for Mail:
> Data Protection for Microsoft Exchange Server Version 6, Release 4,
Level 0.0
> (C) Copyright IBM Corporation 1998, 2012. All rights reserved.
> ACN5057I The c:\program files\tivoli\tsm\TDPExchange\tdpexc.log log 
> file has been pruned successfully.
> Querying Exchange Server to gather component information, please wait...
> Connecting to TSM Server as node 'BCMSG107_MAIL'...
> Connecting to Local DSM Agent 'BCMSG107'...
> Using backup node 'EXCHANGE2010'...
> Starting component backup...
> Beginning VSS backup of 'DB061' (DBC

Re: TDP Exchange 2010 scheduled backups fail rc=1819

[Sheridan, Peter T.]

Is your proxy configured correctly ? 

grant proxynode target= agent=

Like Margaret recommends , make sure your CAD and remote agent is setup 
properly. 


Configure Schedule Services:
 1. Open Command Prompt as Administrator
 2. Enter - CD C:\Program Files\Tivoli\tsm\baclient
 3. Enter - dsmcutil install CAD /name:"TSM CAD NAME" /node:enter your proxy 
agent /password:enter your password for node /optfile: 
/autostart:yes /startnow:yes
 4. Enter - dsmcutil install remoteagent /name:"TSM AGENT NAME" /node:enter 
your proxy agent /password:enter your password /optfile:dsm.opt 
/partnername:"TSM CAD"
 5. Open Services Manager and stop/start TSM CAD


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of Clark, 
Margaret
Sent: Tuesday, January 15, 2013 3:47 PM
To: ADSM-L@vm.marist.edu
Subject: Re: [ADSM-L] TDP Exchange 2010 scheduled backups fail rc=1819

I suppose you're not using a client acceptor service that somehow slipped past 
you?  (Grasping at straws)  - Margaret

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Bill 
Boyer
Sent: Tuesday, January 15, 2013 1:12 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TDP Exchange 2010 scheduled backups fail rc=1819

The TSM Scheduler service is running under the domain userid in the 
"organization Management" group. If I logon as that userid I can run the 
backups. But running them as a scheduled task fails. That's what's 
strangesame userid... works logged on...fails as service.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Rick 
Adamson
Sent: Tuesday, January 15, 2013 11:40 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TDP Exchange 2010 scheduled backups fail rc=1819

Also, remember that the account used for the scheduler has to be a member of 
the Exchange Security Group "Organization Management", which in our case is a 
security group in our root domain.
~Rick

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Clark, 
Margaret
Sent: Tuesday, January 15, 2013 11:03 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TDP Exchange 2010 scheduled backups fail rc=1819

We saw RC=1819 when the scheduler was started using the local system account, 
and the local system account did not have access to the Exchange system.
- Margaret

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Bill 
Boyer
Sent: Tuesday, January 15, 2013 5:10 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] TDP Exchange 2010 scheduled backups fail rc=1819

Windows 2008 R2 server running Exchange 2010. Installed the agent and my 
Exchange admin gave me a userid with the permissions. Running the backup while 
logged in as the user works fine, but when I run it as a scheduled backup I get 
RC=1819. The TSM Scheduler service is configured to run as the same domain 
userid I used to successfully backup while logged on.



Never seen this one before. Scheduler fails with the same userid that works if 
I logon locally. My Windows guy is stumped, too.



Any ideas?



Bill Boyer
DSS, Inc.
(610) 927-4407
"Enjoy life. It has an expiration date." - ??

Re: TDP Exchange 2010 scheduled backups fail rc=1819

[Sheridan, Peter T.]

Is there any way you typed the password incorrectly for the service ? Did you 
try and delete service and recreate it ? 

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of Clark, 
Margaret
Sent: Tuesday, January 15, 2013 3:47 PM
To: ADSM-L@vm.marist.edu
Subject: Re: [ADSM-L] TDP Exchange 2010 scheduled backups fail rc=1819

I suppose you're not using a client acceptor service that somehow slipped past 
you?  (Grasping at straws)  - Margaret

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Bill 
Boyer
Sent: Tuesday, January 15, 2013 1:12 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TDP Exchange 2010 scheduled backups fail rc=1819

The TSM Scheduler service is running under the domain userid in the 
"organization Management" group. If I logon as that userid I can run the 
backups. But running them as a scheduled task fails. That's what's 
strangesame userid... works logged on...fails as service.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Rick 
Adamson
Sent: Tuesday, January 15, 2013 11:40 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TDP Exchange 2010 scheduled backups fail rc=1819

Also, remember that the account used for the scheduler has to be a member of 
the Exchange Security Group "Organization Management", which in our case is a 
security group in our root domain.
~Rick

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Clark, 
Margaret
Sent: Tuesday, January 15, 2013 11:03 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TDP Exchange 2010 scheduled backups fail rc=1819

We saw RC=1819 when the scheduler was started using the local system account, 
and the local system account did not have access to the Exchange system.
- Margaret

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Bill 
Boyer
Sent: Tuesday, January 15, 2013 5:10 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] TDP Exchange 2010 scheduled backups fail rc=1819

Windows 2008 R2 server running Exchange 2010. Installed the agent and my 
Exchange admin gave me a userid with the permissions. Running the backup while 
logged in as the user works fine, but when I run it as a scheduled backup I get 
RC=1819. The TSM Scheduler service is configured to run as the same domain 
userid I used to successfully backup while logged on.



Never seen this one before. Scheduler fails with the same userid that works if 
I logon locally. My Windows guy is stumped, too.



Any ideas?



Bill Boyer
DSS, Inc.
(610) 927-4407
"Enjoy life. It has an expiration date." - ??

Re: More files in copy pool than primary pool?

[Sheridan, Peter T.]

What is retention set on copy pools versus primary pools ? 

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of Allen 
S. Rout
Sent: Monday, December 10, 2012 8:42 AM
To: ADSM-L@vm.marist.edu
Subject: Re: [ADSM-L] More files in copy pool than primary pool?

On 12/06/2012 11:19 AM, Ehresman,David E. wrote:
> No move data involved.
>
> In fact, the problem persists after deleting all the copy pool volumes for 
> this node and doing a fresh backup stg.
>

If you're doing that level of evaluation, then I suggest you q contents for the 
node on the various volumes, and reconcile them.

- Allen S. Rout

Re: Tsm for VE 6.4

[Sheridan, Peter T.]

Can somebody please tell me where I can find the software for VE 6.4 ? I am on 
the ftp website but can't locate the software. Thanks Pete. 

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of Robert 
Ouzen
Sent: Friday, November 30, 2012 11:00 AM
To: ADSM-L@vm.marist.edu
Subject: Re: [ADSM-L] Tsm for VE 6.4

Hi James

Yes I figured it and did it , resolved the problem ...

Anyway thanks a lot

Robert

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of jmayhew
Sent: Friday, November 30, 2012 5:53 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Tsm for VE 6.4

I had a similar problem and I had to unregister and reregister the vCenter 
plugin. On a windows server you can do so by running the script:

C:\Program Files (x86)\Common 
Files\Tivoli\TDPVMware\VMwarePlugin\unregister_vcenter.cmd

usage: unregister_vcenter.cmd   

AND

C:\Program Files (x86)\Common 
Files\Tivoli\TDPVMware\VMwarePlugin\register_vcenter.cmd

register_vcenter.cmd

I hope that this helps!

James

+--
|This was sent by jmay...@mail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--

Re: expire question

[Sheridan, Peter T.]

I am not 100% sure but think if you delete a file from the client itself
it will be deleted without having to run expiration.   

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of
Tim Brown
Sent: Wednesday, March 14, 2012 2:34 PM
To: ADSM-L@vm.marist.edu
Subject: [ADSM-L] expire question

If a file is bound to a mgmt class like below, and you never ran expire
inventory

can the number of retain extra versions be greater then 2



It's the expire inventory that actually deletes them right and not the
client backup





PolicyPolicyMgmt  Copy  Versions Versions   Retain
Retain

DomainSet Name  Class Group Data DataExtra
Only

NameName  NameExists  Deleted Versions
Version

- - - -   
---

DEVTEST   ACTIVEDEVTEST   STANDARD 4   2   365
365



Thanks,



Tim Brown
Systems Specialist - Project Leader
Central Hudson Gas & Electric
284 South Ave
Poughkeepsie, NY 12601
Email: tbr...@cenhud.com <>
Phone: 845-486-5643
Fax: 845-486-5921
Cell: 845-235-4255




This message contains confidential information and is only for the
intended recipient. If the reader of this message is not the intended
recipient, or an employee or agent responsible for delivering this
message to the intended recipient, please notify the sender immediately
by replying to this note and deleting all copies and attachments.

Re: TSM 6.2 Administration Center

[Sheridan, Peter T.]

I could not get the 6.3 administration center to work in my environment using 
either IE or firefox. As a result, went back to the latest 6.2 version.  

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of Erwann 
SIMON
Sent: Tuesday, March 13, 2012 3:33 PM
To: ADSM-L@vm.marist.edu
Subject: Re: [ADSM-L] TSM 6.2 Administration Center

Hi Michael,

Consider using Administration Center 6.3 instead of 6.2 as it's'supported with 
newer browsers ans TSM 6.2 server.

--Message d'origine--
De: Michael P Hizny
Expéditeur : ADSM: Dist Stor Manager
À: ADSM-L@VM.MARIST.EDU
Répondre à: ADSM: Dist Stor Manager
Objet: [ADSM-L] TSM 6.2 Administration Center
Envoyé: 13 mars 2012 21:20

We recently upgrade TSM to version 6.2 and have found out that the
Administration Center web interface will not work with any newer browsers.
It is certified to work with ie 6.0 and Firefox 2.0.  Has anyone come up
with a work around to get it to work with ie7, 8, or 9? Or Chrome?


--
Best regards / Cordialement / مع تحياتي
Erwann SIMON

Re: Ang: [ADSM-L] TDP 6.3 and Exchange 2010?

[Sheridan, Peter T.]

This is great and thanks for your help. I will give it a try in the next week. 

By any chance, do you have active/passive Databases in a dag across different 
physical Exchange servers ? Was wondering if there are different setup 
requirements for this type of scenario ?   

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of 
Vandeventer, Harold [BS]
Sent: Monday, March 12, 2012 2:23 PM
To: ADSM-L@vm.marist.edu
Subject: Re: [ADSM-L] Ang: [ADSM-L] TDP 6.3 and Exchange 2010?

I've not looked for a Redbook, we fought the initial setup for several days, 
using PMRs to get through several of the steps.

The TSM server is 6.2.3.0, running on Windows 2008 R2.

The major points that I recall:

Created a new Domain, with only one Mgmt Class, thus the default.

In that domain:
Created a nodename that is used at the BA-Client.  Let's call this 
"ExchangeServer1".

Created a second nodename that is used at the TDP-Client.  Let's call this 
"ExchangeServerTDP".

ExchangeServerTDP displays ExchangeServer1 as a Proxy Authority:  Via the 
AdminCenter GUI, open ExchangeServerTDP, click Proxy Authority, add 
ExchangeSever1.

Both nodes (ExchangeServerTDP and ExchangeServer1) were given "client owner" 
authority level in the TSM server Administrators list.

Created two schedules: one for C:\EXCFULL.CMD; one for C:\EXCINCR.CMD.

Assigned the schedules to ExchangeServerTDP.

I didn't do all the TDP install and VSS setup testing; that was done by the 
Exchange Server admin. I can only work with the TSM Server side details.  The 
TDP install apparently created the excfull.cmd and excincr.cmd files as 
examples for customization.  I recall the Exchange Admin was impressed by the 
6.3 TDP GUI and how some initial testing for VSS setup was fairly easy.

Our knees were very bloody getting through all of it; and at the moment 
scheduled backup appears to be successful only if the TDP Scheduler Service has 
"logon as" set to a domain account that has Exchange permissions. We've not 
seen that as a requirement in the setup guide.

Recall the phrase: Your mileage may vary!  Good luck with it.


Harold Vandeventer
Systems Programmer
State of Kansas - Department of Administration - Office of Information 
Technology Services
harold.vandeven...@da.ks.gov
(785) 296-0631

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Sheridan, Peter T.
Sent: Monday, March 12, 2012 1:27 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Ang: [ADSM-L] TDP 6.3 and Exchange 2010?

Do any of you have a runbook or set of procedures to follow to get TSM setup to 
backup Exchange 2010 ? I have see the manual/power shell script, etc.. but am 
still struggling with the setup. 

Thanks in advance for any help, Pete.  

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of Daniel 
Sparrman
Sent: Monday, March 12, 2012 9:39 AM
To: ADSM-L@vm.marist.edu
Subject: [ADSM-L] Ang: [ADSM-L] TDP 6.3 and Exchange 2010?

Hi

That wont work since you will need domain-level administrator rights to backup 
Exchange 2010.

Either create a new account with domain-level administrator rights and the role 
"Administrator" in Exchange, or use your existing Administrator account.

Local System doesnt have domain-level administrator rights.

Regards

Daniel Sparrman


Daniel Sparrman
Exist i Stockholm AB
Växel: 08-754 98 00
Fax: 08-754 97 30
daniel.sparr...@exist.se
http://www.existgruppen.se
Posthusgatan 1 761 30 NORRTÄLJE


-"ADSM: Dist Stor Manager"  skrev: - 
Till: ADSM-L@VM.MARIST.EDU
Från: "Vandeventer, Harold [BS]" 
Sänt av: "ADSM: Dist Stor Manager" 
Datum: 03/12/2012 15:35
Ärende: [ADSM-L] TDP 6.3 and Exchange 2010?


Is anyone using TDP 6.3 to run VSS backup against Exchange 2010 DAG?

We're fighting a problem where a scheduled backup is reported as "successful" 
from the TSM server perspective, but according to the TDP/Exchange manager the 
backup never runs.  He doesn't see any corresponding backup history in the TDP 
GUI.

Setting the TDP Scheduler service to Log On As a domain account (not "Local 
System") seems to let scheduled backup work, but the TDP/Exchange manager wants 
to avoid password change polices by using Local System as he has for years with 
Exchange 2007.

We've got a PMR open, with no progress other than "try a domain account".


Harold Vandeventer

Re: Ang: [ADSM-L] TDP 6.3 and Exchange 2010?

[Sheridan, Peter T.]

Do any of you have a runbook or set of procedures to follow to get TSM setup to 
backup Exchange 2010 ? I have see the manual/power shell script, etc.. but am 
still struggling with the setup. 

Thanks in advance for any help, Pete.  

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of Daniel 
Sparrman
Sent: Monday, March 12, 2012 9:39 AM
To: ADSM-L@vm.marist.edu
Subject: [ADSM-L] Ang: [ADSM-L] TDP 6.3 and Exchange 2010?

Hi

That wont work since you will need domain-level administrator rights to backup 
Exchange 2010.

Either create a new account with domain-level administrator rights and the role 
"Administrator" in Exchange, or use your existing Administrator account.

Local System doesnt have domain-level administrator rights.

Regards

Daniel Sparrman


Daniel Sparrman
Exist i Stockholm AB
Växel: 08-754 98 00
Fax: 08-754 97 30
daniel.sparr...@exist.se
http://www.existgruppen.se
Posthusgatan 1 761 30 NORRTÄLJE


-"ADSM: Dist Stor Manager"  skrev: - 
Till: ADSM-L@VM.MARIST.EDU
Från: "Vandeventer, Harold [BS]" 
Sänt av: "ADSM: Dist Stor Manager" 
Datum: 03/12/2012 15:35
Ärende: [ADSM-L] TDP 6.3 and Exchange 2010?


Is anyone using TDP 6.3 to run VSS backup against Exchange 2010 DAG?

We're fighting a problem where a scheduled backup is reported as "successful" 
from the TSM server perspective, but according to the TDP/Exchange manager the 
backup never runs.  He doesn't see any corresponding backup history in the TDP 
GUI.

Setting the TDP Scheduler service to Log On As a domain account (not "Local 
System") seems to let scheduled backup work, but the TDP/Exchange manager wants 
to avoid password change polices by using Local System as he has for years with 
Exchange 2007.

We've got a PMR open, with no progress other than "try a domain account".


Harold Vandeventer

Re: Deployment Engine Failed to initialize

[Sheridan, Peter T.]

Would people recommend going with 6.2.3 or 6.3 ?  

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of
Colwell, William F.
Sent: Tuesday, February 28, 2012 10:22 AM
To: ADSM-L@vm.marist.edu
Subject: Re: [ADSM-L] Deployment Engine Failed to initialize

I agree with Zoltan.  I have 2 very large instances at 6.1.5.10 in
production

doing large amounts of dedup processing.  I am aware of the reorg issues
but it

doesn't bother me, I am not interested in reorging the tables.  In any
case

6.3 doesn't solve all the reorg issues, see apar ic81261 and flash
1580639.



Thanks,



Bill Colwell

Draper Lab



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Zoltan Forray/AC/VCU
Sent: Tuesday, February 28, 2012 9:39 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Deployment Engine Failed to initialize



WOW - such harsh words about 6.1 !   I don't agree..my main
production

6.x system is 6.1.5.10 with no issues.  At least it hasn't had this
wacky,

problem my other 6.2.x servers have had with a DB backup randomly,

intermittently failing with no discernible reason(note, there are
docs

that say you really need to be at least at 6.1.4.1 to resolve some big

problems, especially with reorgs)





Zoltan Forray

TSM Software & Hardware 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 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







From:   "Prather, Wanda" 

To: ADSM-L@VM.MARIST.EDU

Date:   02/28/2012 05:57 AM

Subject:Re: [ADSM-L] Deployment Engine Failed to initialize

Sent by:"ADSM: Dist Stor Manager" 







What Remco said.

Nothing Good will Happen on 6.1.

I finally got a production system stable on 6.1.3 by disabling reorgs,
but

that was Windows.

I wouldn't even think of doing it on Linux.



W



-Original Message-

From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of

Remco Post

Sent: Monday, February 27, 2012 5:10 PM

To: ADSM-L@VM.MARIST.EDU

Subject: Re: [ADSM-L] Deployment Engine Failed to initialize



Hi,



do not use TSM server 6.1, not even if you have no other options. 6.1
does

not even begin to approach alpha quality software. IBM should never have

shipped it. I can't think of a single good reason to install 6.1. Go
with

6.2.3 or newer or 6.3 something.







On 27 feb. 2012, at 22:57, George Huebschman wrote:



> We are getting the "Deployment Engine Failed to Initialize" when

> running ./install.bin for TSM Server 6.1 on a clean new RHEL server.

> I see lots of noise out here about this error, in and out of the TSM

world.

>

> (We have another TSM installation of TSM 6.3 on a VM  that isn't even

> QA as such, just a practice install.) Documetation specifies that

> there be 2GB available in the home directory.

> We only have 1.6 GB, BUT so does the successful 6.3 install.

> We had the error on the first and subsequent 3 attempts to run the

> install.  We did not find any .lock or .lck files.

> I am told that SELINUX is set to permissive.

>

> Except for the home directory, the other space guidelines were met.

> The install is being done as root.

>

> Looking at the TSM related posts about this issue, I didn't notice any

> for releases after 6.1.

> Is that because I didn't look hard enough?  Or, was documentation

> improved, or was a bug fixed?

> Should I talk someone into 6.2 to get past this?

>

> Most of my experience has been with 5.* I have read the install guide

> (most of it) for 6.2, which is what I thought we were installing.  Do

> I need to step back in documentation?

>

>

> --

> George Huebschman

>

> "When you have a choice, spend money where you would prefer to work if

> you had NO choice."



--

Met vriendelijke groeten/Kind Regards,



Remco Post

r.p...@plcs.nl

+31 6 248 21 622

Re: tsm and disk only

[Sheridan, Peter T.]

You do not want to store everything on disk (without migrating off) as
there is no true way to reclaim.  

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of
Tim Brown
Sent: Thursday, February 09, 2012 9:41 AM
To: ADSM-L@vm.marist.edu
Subject: [ADSM-L] tsm and disk only

Is anyone using in a TSM disk only configuration but yet with tapes for
long term storage, archive..



I am looking to see if one does, what TSM processes they use for tape



Snapshots

Full backups, alternate TSM nodes, Server_Inc  Server_Full



How often weekly, monthly, quarterly..



Thanks,



Tim Brown
Systems Specialist - Project Leader
Central Hudson Gas & Electric
284 South Ave
Poughkeepsie, NY 12601
Email: tbr...@cenhud.com <>
Phone: 845-486-5643
Fax: 845-486-5921
Cell: 845-235-4255




This message contains confidential information and is only for the
intended recipient. If the reader of this message is not the intended
recipient, or an employee or agent responsible for delivering this
message to the intended recipient, please notify the sender immediately
by replying to this note and deleting all copies and attachments.

Re: Migrating from AIX to Linux (again)

[Sheridan, Peter T.]

Does anybody have any comparisons on running TSM V6.3 on the AIX
platform versus Windows 2008 ? We have been running on AIX for
approximately 15 years and our company would like us to convert to
windows. Trying to give them a comparison in terms of hardware needed,
disaster recovery times, etc... 

Thanks.  

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of
Robert A. Clark
Sent: Thursday, November 17, 2011 11:30 AM
To: ADSM-L@vm.marist.edu
Subject: Re: [ADSM-L] Migrating from AIX to Linux (again)

A link farm? Maybe www.butterflysoftware.net?

[RC]




st...@stevenharris.info 
Sent by: ADSM-L@VM.MARIST.EDU
11/16/2011 11:57 PM
Please respond to
ADSM-L@VM.MARIST.EDU


To
ADSM-L@VM.MARIST.EDU
cc

Subject
Re: [ADSM-L] Migrating from AIX to Linux (again)






You have to move off TSM 5 sooner or later.  Any reasonably sized TSM
installation takes too long to practically convert in place so you are
forced to install TSM 6 on a new server, start new backups and then
export/import the old data.  This is an ideal time to change platform in
the process.

Other than that take a look at www.butterflysoftware.com

Regards

Steve

Steven Harris
TSM Admin, Canberra Australia



On 17/11/2011 8:43 AM, Hans Christian Riksheim wrote:
> I am not of any help here but you say you are moving to Linux because
> it is cheaper.
>
> Our Power servers running TSM accounts for less than 3% of the yearly
> total cost for our backup infrastructure. Then we include licenses and
> man hours in addition to hardware and data center costs(floor space,
> power and cooling).
>
> Cutting off a little of those 3% is not an option for us if it means
> moving away from a rock solid platform. Even if Linux on Dell was
> handed to us free of charge we would stay on Power. But YMMV.
>
> Anyone else done the same calculation and found out what the cost of
> the physical servers amount to compared to total cost for the TSM
> infrastructure? Maybe you should.
>
> Hans Chr.
>
>
>
> On Wed, Nov 16, 2011 at 4:47 PM, Dury, John C. 
wrote:
>> Our current environment looks like this:
>> We have a production TSM server that all of our clients backup to 
throughout the day. This server has 2 SL500 tape libraries attached via 
fiber. One is local and the other at a remote site which is connected by

dark fiber. The backup data is sent to the remote SL500 library several 
times a day in an effort to keep them in sync.  The strategy is to bring

up the TSM DR server at the remote site and have it do backups and 
recovers from the SL500 at that site in case of a DR scenario.
>>
>> I've done a lot of reading in the past and some just recently on the 
possible ways to migrate from an AIX TSM server to a Linux TSM server. I

understand that in earlier versions (we are currently at 5.5.5.2) of the

TSM server it allowed you to backup the DB on one platform (AIX for 
instance) and restore on another platform (Linux for instance) and if
you 
were keeping the same library, it would just work but apparently that
was 
removed by IBM in the TSM server code to presumably prevent customers
from 
moving to less expensive hardware. (Gee, thanks IBM!).
>> I posted several years ago about any possible ways to migrate the TSM

Server from AIX to Linux.
>> The feasible solutions were as follows:
>>
>> 1.   Build new linux server with access to same tape library and 
then export nodes from one server to the other and then change each node

as it's exported, to backup to the new TSM Server instead.  Then the old

data in the old server can be purged. A lengthy and time consuming
process 
depending on the amount of data in your tape library.
>>
>> 2.   Build a new TSM linux server and point all TSM clients to it

but keep the old TSM server around in case of restores for a specified 
period of time until it can be removed.
>>
>> There may have been more options but those seemed the most reasonable

given our environment. Our biggest problem with scenario 1 above is 
exporting the data that lives on the remote SL500 tape library would
take 
much longer as the connection to that tape library is slower than the 
local library.  I can probably get some of our SLAs adjusted to not have

to export all data and only the active data but that remains to be seen.
>>
>> My question. Has any of this changed with v6 TSM or has anyone come
up 
with a way to do this in a less painful and time consuming way? Hacking 
the DB so the other platform code doesn't block restoring an AIX TSM DB
on 
a Linux box? Anything?
>>
>> Thanks again and sorry to revisit all of this again. Just hoping 
something has changed in the last few years.
>> John
>>



If you are not the intended addressee, please inform us immediately that
you have received this e-mail in error, and delete it. We thank you for
your cooperation.  

TSM and Exchange 2010

[Sheridan, Peter T.]

I know that there has been much discussion about this topic but was
wondering if anybody has a step-by-step guide or an IBM Redbook to
reference for using TSM to backup/restore Exchange 2010. I have read the
users guide and am still quite confused. 
 
My main confusion deals with how NOT to get multiple backups of the same
database that can reside on difficult physical machines in a DAG
configuration. Do you have to define a separate schedule and node name
for each DB in a DAG and only backup the passive (or active copy) ? So,
if I have a four node DAG with four databases in the following
configuration: 
 
S1S2   S3  S4 
--
DB1 (A)   DB1 (P)DB2 (A) DB2 (P)
DB3 (P)   DB3 (A)DB4 (P) DB4 (A) 
 
 
Do you create eight node names: S1, S2, S3, S4, DB1, DB2, DB3, and DB4.
To get only one copy of DB1 backed up, run one schedule on S1 to backup
Passive copy of DB1 and similar schedule on S2 to backup passive copy of
DB2. Each night you will run two attempts but only get the passive copy
even though you do not know what physical server it resides. Was also
wondering if you need to run the schedules at different times since you
will be trying to backup the same TSM nodename from 2 different physical
servers ?   
 
Difficult to explain but hope it makes sense. My goal is to only backup
the passive copy of a DB even though that DB can reside on either
physical server S1 or S2. Plus, any instructions to setup TDP for
exchange 2010. 
 
Thanks Pete. 
 
Thanks Pete.  
 
 

Re: Select statement to only list backups with particular event status

[Sheridan, Peter T.]

Here is a select statement that I use to get all of this info for the
last 24 hours: 

select * from events where status!='Completed' and status!='Future' and
status!='Pending' and status!='Started' and scheduled_start >=
'2010-01-01' and scheduled_start >= current_timestamp - 24 hours


 

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Richard Sims
Sent: Tuesday, June 29, 2010 12:45 PM
To: ADSM-L@vm.marist.edu
Subject: Re: [ADSM-L] Select statement to only list backups with
particular event status

The only way to see status=Started jobs is if you perform a query while
they are under way: if you really wanted that, a cron job capture would
take care of it.  Running a query after all scheduled backups have
finished will report final status of Completed (or Missed or Failed),
which is probably what you get at 09:00.  And, of course, the Events
table does not contain information for backups which are independently
performed on the client.

Such event information is superficial, of course...  The client
administrator should be reviewing backup logs (and the dsmerror.log!)
for anomalies which may be delaying backups (e.g., retries) or be
causing individual files or whole file systems to not get backed up (as
in a Domain omission or forgotten, old Exclude).

Richard Sims   http://people.bu.edu/rbs

On Jun 29, 2010, at 1:28 PM, Moyer, Joni M wrote:

> Hi Richard,
> 
> Is there any other way to do a report that would list missed, failed,
in progress and started backups then on a daily basis running it from
the prior day at 6PM until the current time the script is run at 9AM?  I
currently run q event at 9AM which catches the missed & failed backups,
but nothing that currently accounts for anything that is in progress or
has been started.
> 
> Any suggestions/ideas are appreciated!  This one has me stumped!

Re: Exchange 2010 tips

[Sheridan, Peter T.]

I was wondering if anybody has tried to configure the new Exchange 2010
TCP in a cluster. My main question is about the localdsmagentnode
option. My understanding is that it should point to the physical node
and was wondering how that works when it is failed over from node to
node ?