Priority list for TSM work (February)

Outstanding Actions (on DEV environment)  
PriorityTasksOwnersCompleteOutcome
1Determine options for compression Andy and Mark raising calls with Oracle and IBM for this

Y

 

Compression can be used - ref Mark L email 06/02; confirmation from Oracle
2Confirm backup strategy for Linux db servers. (Only backup database and archive logs on Standby once a day).Dev Tech/Tech ManY 
3Determine if migrating Solaris database servers to TSM backupsDev Tech/Tech ManY 
4Implement agreed configDev Tech:Gillian  
5Confirm Inclusion and Exclusion List for dev db serversDev Tech: Gillian/ITI: Andy  
6Confirm timings and pre/post  commands for db servers to ensure full complete rman backup (consisting of backup pieces) being backed up to TSMDev Tech: Gillian/ITI: Andy  
7Confirm requirements for Monthly backups Dev Tech: Gillian/ITI: Andy  
8Test deletion of expired backups from TSMDev Tech: Gillian  
9Access to interrogate files systems to see backups pieces ITI: Andy  
10

Test recovery of Oracle database

   
11

Test recovery of MySQL database

   
12Dev Tech/Tech Man/ITI sign off of dev environmentAll  

 

Other Outstanding Actions (from 04/02 meeting)

No.ActionsOwnersCompleteNotes
1

Access to view backup pieces created by RMAN on TSM filesystem. To check obsolete backup pieces deleted and check size. 

 

 

Confirm if we can review content of rman TSM filesystems via dsmj or other method 

Andy - to confirm the cross check connectivity for restore purposes

Gillian - report if something else is missing.

 

 

Andy

 

Jira INF105-10

Unidesk I150203-1085

2Review space/time for backups to run on Dev. Confirm we have enough space on TSM storage. (Compression currently off for rman and TSM). 

Andy: Confirm with IBM if we can run compression on RMAN data

Andy: Confirm with IBM if we can compress server side on non RMAN data

Gillian: Confirm with Oracle if RMAN can write compressed to TSM, is there a license cost?

Gillian: Confirm the compression ratio we have seen in RMAN - what ratio do we expect?

 JIRA INF105-7
3Access to IBM support - latest position, delays getting support, Andy having to act as middle manMartin: get devolved support sorted out. JIRA INF105-1
4Update tdpo.opt file on all database servers - all with standard naming convention APPS_<SERVERNAME>_RMAN and TDPO_FS, TDPO_NODE and TDPO_OWNER all same case. Has this been carried out on all servers?Andy & Gillian: recreate all the naming strings so they are uniform JIRA INF105-5 and INF105-8
5Increase setting on database servers to 10 mount points - has this been carried out on all servers?

Andy: to confirm that all DB servers are on the mount point.

Gillian/Mark: to confirm plan to move all backups to run from standbys & exclude archive logs as they are already multi-sited

  
6Java 1.7 to be installed on all servers to allow the dsmj restore gui to be run. - has this been carried out on all servers ?

Andy: to come up with a plan to have a uniform java installation that is non intrusive to existing java installs.

Gillian: to test

 Jira INF105-2
7

Monthly backups. Has this been implemented? Plan to backups on 1st of each month. Are our backup retention periods of 30 days for dev and 42 days for test/live sufficient?

Determine if pre-post commands required to enforce consistency of monthly rman backups being taken. Can monthly backup consist of our level 0 on Friday to avoid scheduling an additional backup?  

Andy: to confirm backupsets work for RMAN

 

 

Gillian/Mark: to investigate if we need a special level 0 backup of RMAN to create the backupset from

 Jira INF105-3
8Backup Alerts. Files changing reported as error alongside other errors. How do we want to resolve? Andy to change script to differentiate between files changing error and other errors or add exclusions?

Gillian: identify the acceptable open files changing to be excluded.

Andy: edit the reporting script to grep out the open file changed error

 Jira INF105-4
9Freeing up space in /backup: The 3600's will be relocated. A replacement area(s) can be provisioned from Compellent. Discuss how this will be scheduledAndy: new 100GB slice to temp backup files - check it is configured uniformly  
10

Review dsm.sys on all database servers to make sure we have correct exclusion list

Andy & Gillian: work through this Jira INF105-13
11Backups overrunning - mainly Ardvreck - is there an ongoing issue with this server. Can this be resolved?Julieta/Heather - look at exclusion & review it. (Low priority) Jira INF105-11
12

Determine plan for Solaris database servers. Leave until after Linux db servers migrated? Migrate to TSM or option leave on networker?

 

Heather/Iain/Martin   

 

Project Info

Project
Decommission Obsolete Infrastructure
Code
INF105
Programme
ISG - IS Applications Infrastructure (INF)
Project Manager
David Watters
Project Sponsor
Stefan Kaempf
Current Stage
Close
Status
Closed
Start Date
08-Sep-2014
Planning Date
n/a
Delivery Date
n/a
Close Date
29-Jul-2016
Programme Priority
1
Overall Priority
Normal
Category
Compliance