HP D2D D2D Best Practices for VTL, NAS and Replication implementations (EH985- - Page 84

Backup requirements specification - iscsi

Get HP D2D PDF manuals and user guides View all HP D2D manuals
Add to My Manuals
Save this manual to your list of manuals

Page 84 highlights

Backup requirements specification Remote Sites A/D NAS emulations required Server 1 - Filesystem 1, 100 GB, spread across 3 mount points Server 2 - SQL data, 100GB Server 3 - Filesystem 2, 100GB, spread across 2 mount points Server 4 -- Special App Data , 100GB Rotation Scheme - Weekly Fulls, 10% Incrementals during week, Keep 4 weeks Fulls and 1 monthly backup 12 hour backup window Remote sites B/C iSCSI VTL emulations required Server 1- Filesystem, 200 GB, spread across 2 mount points C,D Server 2 - SQL data, 200GB Server 3 - Special App data, 200GB Rotation Scheme - Weekly Fulls, 10% Incrementals during week, Keep 4 weeks Fulls and 1 monthly backup 12 hour backup window Data Center E Fibre Channel VTL emulations required for local backups Server 1 - 500GB Exchange => Lib 1 - 4 backup streams Server 2 - 500GB Special App => Lib 2 - 1 backup stream Rotation Scheme - 500GB Daily Full, retained for 1 month. 12 hour backup window Replication target for sites A, B, C, D (this means we have to size for replication capacity AND local backups on Site E) Monthly archive required at Site E from D2D to Physical Tape One of the key parameters in sizing a solution such as this is trying to estimate the daily block level change rate for data in each backup job. In this example we will use the default value of 2% in the HP StorageWorks sizing tool. http://h30144.www3.hp.com/SWDSizerWeb/default.htm 84

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
84
Backup requirements specification
Remote Sites A/D
NAS emulations required
Server 1
–
Filesystem 1, 100 GB, spread across 3 mount points
Server 2
–
SQL data, 100GB
Server 3
–
Filesystem 2, 100GB, spread across 2 mount points
Server 4
–
- Special App Data , 100GB
Rotation Scheme
–
Weekly Fulls, 10% Incrementals during week, Keep 4 weeks Fulls and 1 monthly backup
12 hour backup window
Remote sites B/C
iSCSI VTL emulations required
Server 1
–
Filesystem, 200 GB, spread across 2 mount points C,D
Server 2
–
SQL data, 200GB
Server 3
–
Special App data, 200GB
Rotation Scheme
–
Weekly Fulls, 10% Incrementals during week, Keep 4 weeks Fulls and 1 monthly backup
12 hour backup window
Data Center E
Fibre Channel VTL emulations required for local backups
Server 1 - 500GB Exchange => Lib 1
-
4 backup streams
Server 2 - 500GB Special App => Lib 2
–
1 backup stream
Rotation Scheme
–
500GB Daily Full, retained for 1 month.
12 hour backup window
Replication target for sites A, B, C, D (this means we have to size for replication capacity AND local backups on
Site E)
Monthly archive required at Site E from D2D to Physical Tape
One of the key parameters in sizing a solution such as this is trying to estimate the daily block level change rate
for data in each backup job. In this example we will use the default value of 2% in the HP StorageWorks sizing
tool.