Re: TSM 5.3.4 Policy problem

[Remco Post]

On 18 dec 2009, at 07:18, William ZHANG wrote:

> Hi All,
> 
> Thanks for your help!
> 
> When I input:
> ACTIVATE POLICYSET DOM_SRC SET_SRV
> 
> TSM give a message:
> ANR1557W The space management migration destination in management class
> MC_90DAYS does
> Not refer to a defined storage pool: SPACEMGPOOL.
> If this pooll does not exist when policy set SET_SRV is activated, clients
> will fail
> When using this management class to migrate space-managed files to the
> server.
> 
> But actually,my stgpool are DISK_SRV and LTO3_BCK_SRV, not SPACEMGPOOL,


so, read very carefully what this says: "clients to migrate 
space-managed files ...".

Space management is also called HSM for Unix. So, when you use HSM for Unix, 
this warning is significant. If you don't use HSM for Unix (most likely), of 
you do but it points to a different management class (I'd think that you won't 
be asking this question in that case), you can safely ignore this message.

-- 
Met vriendelijke groeten/Kind Regards,

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

Re: collocation increases tape mounts while backup

[Steven Langdale]

Indeed you are correct.  Though isn't that collocation going to go out of 
the window on the 2nd days migrations?  The daily chunks of data will be 
together, but all node data would be on the same tape until it gets 
filled.

I cannot agree more on you last sentence! :)

Steven 

Steven Langdale
Global Information Services
EAME SAN/Storage Planning and Implementation
( Phone : +44 (0)1733 584175
( Mob: +44 (0)7876 216782
ü Conference: +44 (0)208 609 7400 Code: 331817
+ Email: steven.langd...@cat.com

 



Richard Sims  
Sent by: "ADSM: Dist Stor Manager" 
17/12/2009 22:47
Please respond to
"ADSM: Dist Stor Manager" 


To
ADSM-L@VM.MARIST.EDU
cc

Subject
Re: [ADSM-L] collocation increases tape mounts while backup




Caterpillar: Confidential Green Retain Until: 16/01/2010 



On Dec 17, 2009, at 5:31 PM, Steven Langdale wrote:

> In that case you must be using collocation (albeit  by accident).

Not really...  Remember that, within Migpr, migration operates
serially by node, and thus you get a certain amount of same-node data
clumped together on sequential media.  It's not collocation, but
affords some temporal node data co-residency which incidentally helps
restoral times in the short term.  Of course, one should architect
storage utilization, and not depend upon happenstance.

Richard Sims

tsm tdp oracle rman backups

[Tim Brown]

Anyone performing full and incrmental backups of Oracle

We run a level 0 on Friday night and a combination of level 1's and 2's
the othter nights.

We just started inc backups, prior to that we were doing fulls each night.

We would run a delete obsolete rman command after the full backps to keep 3 
levels
This wasnt changed when we went to incremental. I noticed in one of the log 
files
this morning that rman deleted one the backup pieces created during the level 0 
backup

I dont think this should be the case. If we wanted to restore the level 0 we 
would be missing files

What are the optimum RMAN retention policies and TSM retention policies for 
Oracle

They must be different between using always full backups or a combination of 
full and inc


RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 3
Deleting the following obsolete backups and copies:
Type KeyCompletion TimeFilename/Handle
 -- -- 
Backup Set   31844  12-DEC-09
  Backup Piece   31844  12-DEC-09  df_705420601_31958_1  <=full
Backup Set   32011  15-DEC-09
  Backup Piece   32011  15-DEC-09  bul0ucfs_1_1   <== inc
deleted backup piece
backup piece handle=df_705420601_31958_1 recid=31844 stamp=705420603
deleted backup piece
backup piece handle=bul0ucfs_1_1 recid=32011 stamp=705638909
Deleted 2 objects

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.  Thank you.

Re: tsm tdp oracle rman backups

[Grigori Solonovitch]

Hello Tim,
I see "RMAN retention policy is set to redundancy 3" in provided log.
This means that you requested RMAN to provide a possibility to restore/recover 
database for only 3 last days. In my opinion, this value is too low. I have 
full backup every 2 weeks and daily incremental backups between full baqckups. 
Retention policy is set to redundancy 31. As a result, I can restore database 
to any point in time for the last month. Note that amount of data is only a 
little more than for your case, because I am keeping only 3 full backups like 
you.
By the way, everything is correct if 3 days is your target and you are running 
full backup every night. It does not matter how many additional incremental 
backups you are performing every day and which level. RMAN will keep last 3 
full backups and all incremental backups between them. Incremetal backups 
between full backups can only reduce recovery time, because it is much faster 
to restore incremental backup than to restore and apply appropriate archived 
redo logs. At the same, tine it means RMAN will expire one full backup and all 
incrementals between this full backup and next one every day.

For example, If you have:

15/12/2009 Full Backup
15/12/2009 Incremental backup level 1
16/12/2009 Full Backup
16/12/2009 Incremental backup level 1
16/12/2009 Incremental backup level 2
16/12/2009 Incremental backup level 1
17/12/2009 Full Backup
17/12/2009 Incremental backup level 1
17/12/2009 Incremental backup level 1
18/12/2009 Full Backup

If you run:

19/12/2009 Full Backup
19/12/2009 Expire Inventory

all next backups:

15/12/2009 Full Backup
15/12/2009 Incremental backup level 1

will be removed definately, because they are not required more to be able to 
restore for requested 3 days:

16/12/2009 Full Backup
16/12/2009 Incremental backup level 1
16/12/2009 Incremental backup level 2
16/12/2009 Incremental backup level 1
17/12/2009 Full Backup
17/12/2009 Incremental backup level 1
17/12/2009 Incremental backup level 1
18/12/2009 Full Backup
19/12/2009 Full Backup

Of course, I suppose you have correct setting for related copy group for your 
case, at least 0 0 4 4.

Kindets regards,
Grigori


From: ADSM: Dist Stor Manager [ads...@vm.marist.edu] On Behalf Of Tim Brown 
[tbr...@cenhud.com]
Sent: Friday, December 18, 2009 11:46 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] tsm tdp oracle rman backups

Anyone performing full and incrmental backups of Oracle

We run a level 0 on Friday night and a combination of level 1's and 2's
the othter nights.

We just started inc backups, prior to that we were doing fulls each night.

We would run a delete obsolete rman command after the full backps to keep 3 
levels
This wasnt changed when we went to incremental. I noticed in one of the log 
files
this morning that rman deleted one the backup pieces created during the level 0 
backup

I dont think this should be the case. If we wanted to restore the level 0 we 
would be missing files

What are the optimum RMAN retention policies and TSM retention policies for 
Oracle

They must be different between using always full backups or a combination of 
full and inc


RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 3
Deleting the following obsolete backups and copies:
Type KeyCompletion TimeFilename/Handle
 -- -- 
Backup Set   31844  12-DEC-09
  Backup Piece   31844  12-DEC-09  df_705420601_31958_1  <=full
Backup Set   32011  15-DEC-09
  Backup Piece   32011  15-DEC-09  bul0ucfs_1_1   <== inc
deleted backup piece
backup piece handle=df_705420601_31958_1 recid=31844 stamp=705420603
deleted backup piece
backup piece handle=bul0ucfs_1_1 recid=32011 stamp=705638909
Deleted 2 objects

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.  Thank you.

Please consider the environment before printing this Email.

"This email message and any attachments transmitted with it may contain 
confidential and proprietary information, intended only for the named 
recipient(s). If you have received this message in error, or if you are not the 
named recipient(s), please delete this email after notifying the sender 
immediately. BKME cannot guarantee the integrity of this communication and 
accepts no liability for any damage caused by this email or its attachments due 
to viruses

Re: TDP for Exchange AD error

[Grigori Solonovitch]

Hello Mario,
It lloks there is a bug in TDP for Mail 6.1.1. We have faced exactly the same 
problem immediately after upgrading to 6.1.1 (command line is working fine, but 
GUI gives this strange message). After short investigation I have recommnded 
our Exhange Admin to report this problem to IBM and they provided some 
workaround immediately. I know exactly that he is able to use backup/recovery 
from GUI with this workaround, but PMR is still opened. I am very sorry, I 
couldn't provide more detailed information, because we have weekends and 
holiday till Monday hire. If you need to use GUI urgently just contact IBM and 
they will help you.
Regards,
Grigori


From: ADSM: Dist Stor Manager [ads...@vm.marist.edu] On Behalf Of Mario Behring 
[mariobehr...@yahoo.com]
Sent: Thursday, December 17, 2009 4:33 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] TDP for Exchange AD error

Hi list,

I´ve just installed the TDP for Exchange 6.1.1.0 on a Windows 2003 Server 
running MSCS.when trying to verify my installation I got the error message 
below:


C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc query exchange 
/excserv=excluster

IBM Tivoli Storage Manager for Mail:
Data Protection for Microsoft Exchange Server
Version 6, Release 1, Level 1.0
(C) Copyright IBM Corporation 1998, 2009. All rights reserved.

Querying Exchange Server to gather storage group information, please wait...

The operation could not be performed because object 'EXCLUSTER' could not be 
found on domain controller 'domain.controller.local'.


The object 'EXCLUSTER' is the actual Cluster Nodename, not the machine 
hostname, as recommended by TDP for Exchange Installation and Configuration 
Guide. This is a 2 node MSCS simple configuration.

I´ve checked the AD and the object exists there.

Any ideas?

Mario





Please consider the environment before printing this Email.

"This email message and any attachments transmitted with it may contain 
confidential and proprietary information, intended only for the named 
recipient(s). If you have received this message in error, or if you are not the 
named recipient(s), please delete this email after notifying the sender 
immediately. BKME cannot guarantee the integrity of this communication and 
accepts no liability for any damage caused by this email or its attachments due 
to viruses, any other defects, interception or unauthorized modification. The 
information, views, opinions and comments of this message are those of the 
individual and not necessarily endorsed by BKME."