HP StoreOnce 4430 HP StoreOnce Backup System Concepts and Configuration Guidel - Page 95

Seeding using physical tape or portable disk drive

Page 95 highlights

1. Plan the final master replication mappings from sources to target that are required and document them. Use an appropriate naming convention e.g. SVTL1, SNASshare1, TVTL1, TNASshare1. 2. At each remote site perform a full system backup to the source StoreOnce appliance and then configure a 1:1 mapping relationship with the floating StoreOnce appliance " e.g. SVTL1 on Remote Site A -> FTVTL1 on floating StoreOnce. FTVTL1 = floating target VTL1. 3. Seeding remote site A to the floating StoreOnce appliance will take place over the GbE link and should take only a few hours. 4. On the Source StoreOnce appliance at the remote site DELETE the replication mappings - this effectively isolates the data that is now on the floating StoreOnce appliance. 5. Repeat the process steps 1-4 at Remote sites B and C. 6. When the floating StoreOnce appliance arrives at the central site, the floating StoreOnce appliance effectively becomes the Source device to replicate INTO the StoreOnce appliance at the data center site. 7. On the Floating StoreOnce appliance we will have devices (previously named as FTVTL1, FTNASshare 1) that we can see from the Web Management Interface. Using the same master naming convention as we did in step 1, set up replication which will necessitate the creation of the necessary devices (VTL or NAS) on the StoreOnce 4220 at the Data Center site e.g. TVTL1, TNASshare 1. 8. This time when replication starts up the contents of the floating StoreOnce appliance will be replicated to the data center StoreOnce appliance over the GbE connection at the data center site and will take several hours. In this example Remote Site A, B, C data will be replicated and seeded into the StoreOnce 4220. When this replication step is complete, DELETE the replication mappings on the floating StoreOnce appliance, to isolate the data on the floating StoreOnce appliance and then DELETE the actual devices on the floating StoreOnce appliance, so the device is ready for the next batch of remote sites. 9. Repeat steps 1-8 for the next series of remote sites until all the remote site data has been seeded into the StoreOnce 4220. 10. Now we have to set up the final replication mappings using our agreed naming convention decided in Step 1. This time we go to the Remote sites and configure replication again to the Data Center site but being careful to use the agreed naming convention at the data center site e.g. TVTL1, TNASshare1 etc. This time when we set up replication the StoreOnce 4220 at the target site presents a list of possible target replication devices available to the remote site A. So in this example we would select TVTL1 or TNASshare1 from the drop-down list presented to Remote Site A when we are configuring the final replication mappings. This time when the replication starts almost all the necessary data is already seeded on the StoreOnce 4220 for Remote site A and the synchronization process happens very quickly. NOTE: If using this approach with Catalyst stores that do not rely on "mappings", the Floating StoreOnce appliance can be simply used to collect all the Catalyst Items at the Remote sites if a consolidation model is to be deployed. If not, create a separate Catalyst store on the Floating StoreOnce Appliance for each site. Seeding using physical tape or portable disk drive In this method of seeding we use a removable piece of media (like LTO physical tape or removable RDX disk drive acting as a disk Library or file library*) to move data from the remote sites to the central data center site. This method requires the use of the backup application software and additional hardware to put the data onto the removable media. * Different backup software describes "disk targets for backup" in different ways e.g. HP Data Protector calls StoreOnce NAS shares " DP File Libraries", Commvault Simpana calls StoreOnce NAS shares "Disk libraries." Seeding using physical tape or portable disk drive 95

  • 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

1.
Plan the final master replication mappings from sources to target that are required and
document them. Use an appropriate naming convention e.g. SVTL1, SNASshare1, TVTL1,
TNASshare1.
2.
At each remote site perform a full system backup to the source StoreOnce appliance and then
configure a 1:1 mapping relationship with the floating StoreOnce appliance ” e.g. SVTL1 on
Remote Site A -> FTVTL1 on floating StoreOnce. FTVTL1 = floating target VTL1.
3.
Seeding remote site A to the floating StoreOnce appliance will take place over the GbE link
and should take only a few hours.
4.
On the Source StoreOnce appliance at the remote site DELETE the replication mappings – this
effectively isolates the data that is now on the floating StoreOnce appliance.
5.
Repeat the process steps 1-4 at Remote sites B and C.
6.
When the floating StoreOnce appliance arrives at the central site, the floating StoreOnce
appliance effectively becomes the Source device to replicate INTO the StoreOnce appliance
at the data center site.
7.
On the Floating StoreOnce appliance we will have devices (previously named as FTVTL1,
FTNASshare 1) that we can see from the Web Management Interface. Using the same master
naming convention as we did in step 1, set up replication which will necessitate the creation
of the necessary devices (VTL or NAS) on the StoreOnce 4220 at the Data Center site e.g.
TVTL1, TNASshare 1.
8.
This time when replication starts up the contents of the floating StoreOnce appliance will be
replicated to the data center StoreOnce appliance over the GbE connection at the data center
site and will take several hours. In this example Remote Site A, B, C data will be replicated
and seeded into the StoreOnce 4220. When this replication step is complete, DELETE the
replication mappings on the floating StoreOnce appliance, to isolate the data on the floating
StoreOnce appliance and then DELETE the actual devices on the floating StoreOnce appliance,
so the device is ready for the next batch of remote sites.
9.
Repeat steps 1-8 for the next series of remote sites until all the remote site data has been
seeded into the StoreOnce 4220.
10.
Now we have to set up the final replication mappings using our agreed naming convention
decided in Step 1. This time we go to the Remote sites and configure replication again to the
Data Center site but being careful to use the agreed naming convention at the data center
site e.g. TVTL1, TNASshare1 etc.
This time when we set up replication the StoreOnce 4220 at the target site presents a list of possible
target replication devices available to the remote site A. So in this example we would select TVTL1
or TNASshare1 from the drop-down list presented to Remote Site A when we are configuring the
final replication mappings. This time when the replication starts almost all the necessary data is
already seeded on the StoreOnce 4220 for Remote site A and the synchronization process happens
very quickly.
NOTE:
If using this approach with Catalyst stores that do not rely on “mappings”, the Floating
StoreOnce appliance can be simply used to collect all the Catalyst Items at the Remote sites if a
consolidation model is to be deployed. If not, create a separate Catalyst store on the Floating
StoreOnce Appliance for each site.
Seeding using physical tape or portable disk drive
In this method of seeding we use a removable piece of media (like LTO physical tape or removable
RDX disk drive acting as a disk Library or file library*) to move data from the remote sites to the
central data center site. This method requires the use of the backup application software and
additional hardware to put the data onto the removable media.
* Different backup software describes “disk targets for backup” in different ways e.g. HP Data
Protector calls StoreOnce NAS shares “ DP File Libraries”, Commvault Simpana calls StoreOnce
NAS shares “Disk libraries.”
Seeding using physical tape or portable disk drive
95