TSM og replikering

448 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
448
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

TSM og replikering

  1. 1. IBM og Peanuts ønsker velkommen til seminarTivoli Storage Manager 6.4Agenda:•  Om IBM og Peanuts v/Olaf Frøseth og Jan E. Danielsen•  TSM 6.3 og 6.4•  De-duplisering og replkering over WAN/LAN•  Ny TSM rapportering•  TSM og Virtualisering•  Demonstrasjon av løsningen v/Roger Stakkestad
  2. 2. Li#  om  Disaster  Recovery  med  TSM  •  BMR  (Bare  Machine  Recovery)  •  TSM  CopyPool  og  fysisk   flyBng  av  tape  offsite  •  TSM  elektronisk  VaulFng  •  TSM  SAN  speiling  •  TSM  replikering  over  LAN/ WAN   –  Hot  standby   –  SLA-­‐basert  replikering  
  3. 3. TSM  node  replikering   • Site A • Site B • Database • TSM Server A • TSM Server B • Database Node C Node B Node A DB2 DB2 Metadata and deduplicated data Node X Node Y• Storage Hierarchy • Storage Hierarchy 1.  Initial replication – all objects are copied to target Backup, Archive, and Space Management Objects 2.  Deleted objects are deleted from target 3.  Modified objects are updated on the target 4.  Newly stored objects are copied during next replication
  4. 4. SLA-­‐basert  replikering  •  Rules  determine  which  files  are  eligible  for  replicaFon  •  Default  backs  up  all  types  (backup,  archive,  HSM)  of  data  for  enabled  nodes   –  ENABLED,  DISABLED  or  PURGEDATA  (all  data  for  that  data  type  is  deleted)  •  6  replicaFon  rules:   –  4  general  use  (ALL_DATA,  ACTIVE_DATA,  ALL_DATA_HIGH_PRIORTY,   ACTIVE_DATA_HIGH_PRIORITY)   –  Default  –  follow  the  replicaFon  rule  hierarchy  unFl  a  non-­‐Default  rule  is  specified   –  None  –  replicaFon  not  performed,  no  data  replicated  •  A#ributes  of  the  rule  tell  the  process  how  tRule Hierarchy Replication o  process  the  file   –  Priority  (High  or  Normal)   –  Replicate  acFve-­‐data  only?   –  State  (enabled  or  disabled)  
  5. 5. TSM  node  replikering  •  DeduplicaFon   –  If  source  has  dedupe  enabled  but  target  does  not   •  Data  is  reconstructed  before  being  sent   –  If  target  has  dedupe  enabled  but  source  does  not   •  Only  the  chunks  not  already  on  the  desFnaFon  server  will  be  sent   –  If  both  source  and  target  have  dedup  enabled   •  Only  the  chunks  of  data  that  are  not  stored  already  in  the  desFnaFon  pool  are  transferred  •  ExpiraFon   –  Files  bound  to  same  mgmt  class,  if  exists,  on  target  server,  otherwise  to  target  server’s   default  mgmtclass   –  Source  server  manages  file  expiraFon  and  deleFon  for  the  replicated  files  on  the  target   server  •  Flexible  ImplementaFon   –  Many-­‐to-­‐1  transfer  to  target  server    (can  only  have  one  target  server)   –  Can  have  server  A  and  server  B  protect  each  other   –  If  import/export  data  exists,  can  uFlize  forcesync  •  Admin  Console  or  Command  line  configuraFon  /  monitoring  •  Scheduled  or  manual  node  replicaFon   –  Single  process  is  started  for  replicaFon   –  High  priority  data  is  replicated  before  data  with  normal  priority   –  Only  one  replicate  node  process  at  a  Fme  
  6. 6. Fleksible  konfigurasjonsmuligheter   Source to Target Between active Sources Many to One Round Robin
  7. 7. Disaster  Recovery  as  a  Service   TSM for VE + TSM b/a WAN replikering Storage Manager 6 Lokal backup Storage Manager 6 TSM B/AClients and TDPs TSM for VE + TSM b/a DR restore
  8. 8. TSM som skyen

×