Product environmental attributes - IT Eco Declaration 2004
Brand Manufacturer Manufacturers representative Contact person Postal address Postal code /City/ Country Telephone (incl. country code) Mobile phone (incl. country code) Fax (incl. country code) Internet site Additional information Hewlett-Packard Hewlett-Packard Name: e-mail: Name: e-mail: itecodeclaration.ww@hp.com Hans Wendschlag , HP Sweden Logo
+ + + http://www.hp.se/environment Latest version of this document can be found at: www.hp.se/itecodeclarations or http://www.hp.com/hpinfo/globalcitizenship/environment/productdata/itecoservers.ht ml. The company environmental profile, which is issued for the company and isn't product related, can also be found at the first website. Check Item 14 for explanatory information regarding specific item responses.
This declaration covers the below listed Information Technology product categories* with specified product identity (ID) such as type/model number.
Computer system unit CPU Display/ monitor Printer Black/white Product identity Copier Colour Mobile/portable computer Keyboard Fax Multifunction product Pages per minute: Scanner Server Digital Projector Camera Other IT product, specify: Tape Storage
HP StorageWorks 6000 Virtual Library System

June 2004

Issue date September 1, 2005 Guideline document (Version of Guideline document used for completion of this declaration (month, year)) This IT Eco Declaration consists of three documents: Company environmental profile: Divided into two sections, legal and market requirements
Product environmental attributes: Divided into two sections, legal and market requirements Guideline document with extensive clarifications, comments and references.
The latest version of all these documents can be downloaded from: www.itecodeclaration.org
Notes: Voluntary vs compulsory requirements: Items marked V are voluntary to answer, all other items must be answered. The latest version of the Guideline document must be used. Specify in table above according to which version of the guideline
document this declaration has been completed.
This version of the IT Eco Declaration is adjusted to the document Product-related Environmental Attributes, issued by the European
Association for Standardizing Information and Communication Systems (ECMA), TR/70, version 1999.
This version of the IT Eco Declaration meets the basic principles of ISO14021:1999, Environmental labels and declarations Self-
declared environmental claims (Type II environmental labelling).
When references are given to standards like ISO, IEC and EN, the latest version should always be referred to.
For telecommunication products, use eco declaration for telecommunication products.
This IT Eco Declaration version can be used from October and shall be used for products announced after December 1 2003.
The IT Eco Declaration is a system for declaration of environmental aspects of IT and telecom products, developed by the Nordic IT organisations, IT-Fretagen in Sweden, ITB in Denmark, IKT-Norge in Norway and TTK ry in Finland. This IT Eco Declaration may only be used after having signed a contract with at least one of these organisations.

Association of the Swedish IT and Telecom Industry www.itforetagen.se
Norwegian IT-companies Organisation www.ikt-norge.no
IT-Brancheforeningen Kontor & Data www.itb.dk
Finnish Association of Office Technology Traders www.ttkry.com

Version June 2004

Page 1 (4)
Copyright Association of the Swedish IT and Telecom Industry 2000. Reproduction of this form without permission is prohibited by the copyright law 1960:729. The prohibition includes any kind of reproduction, by electronic or any other means.
Product identity Issue date
September 1, 2005 Logo Requirement met Yes No n.a.
Product environmental attributes - Legal requirements
Item P1 P1.1 P1.2 P1.3 P1.4 P1.5 Additional information regarding each item may be found under P14. Environmental conscious design Product parts are free from, i.e. less than 0.1% by weight (b.w.), CFCs & HCFCs, asbestos, PCB & PCT (3093/94/EEC, 76/769/EEC, 6th amendment, 99/77/EEC, 82/828/EEC) Components are free from, i.e. less than 0.1% b.w., mercury (Hg), except for small amounts of mercury which are allowed in light sources. (SE SFS 1998:944) Cadmium (Cd) content of colorants, stabilizers, and surface treatments does not exceed, 0.01% b.w., as specified in 76/769/EEC, 10th amendment, 1991/338/EEC. Paints are free from lead (Pb), i.e. less than 0.1% b.w., (76/769/EEC, 8th amendment, 89/677/EEC) Paints, coatings, plastics, rubbers and seals are free from flame retardants and/or plasticizers containing Short Chain Chlorinated Paraffines (SCCPs) with more than 0,1% by weight, 10-13 carbon atoms, minimum 48% chlorine by weight, CAS number 63449-39-8 (NO MVD regulation 1544, 2000.12.13 and FI 416/2003). If the product is intended for direct and prolonged skin contact, the surfaces do not release nickel (Ni) above levels specified in (76/769/EEC, 8th amendment, 94/27/EEC) Batteries If hazardous batteries are used in the product, they are labelled. (93/86/EEC). If batteries are used in the product they are free (<0.0005% by weight) from mercury (Hg) (98/101/EC) Electrical safety, EMC and connection to the telephone network The product meets the Low Voltage Directive (LVD) regarding electrical safety (73/23/EEC & 93/68/EEC) The product meets the EMC Directive regarding electromagnetic compatibility (89/336/EEC) If product is intended for connection to a public telecom network or contains a radio transmitter, it meets the EU R&TTE Directive (1999/5/EC) The product is CE-marked (93/68/EEC) Consumable materials If a photo conductor (drum, belt etc.) is used in the product, it is free (<0.01% by mass) from cadmium (Cd) (76/769/EEC and 91/338/EEC) If an ink is used in the product, it is free (<0.01% by mass) from cadmium (Cd) (91/338/EEC) If toner/ink (or corresponding) are used in the product, they are classified and if required labelled in accordance with EU directives Packaging materials The sum of the concentration levels of lead, cadmium, mercury, and hexavalent chromium present in packaging or packaging components does not exceed 0.01% by weight (100 ppm). (94/62/EC). The product packaging material is free from CFC/HCFC.

P1.6 P2 P2.1 P2.2 P3 P3.1 P3.2 P3.3 P3.4 P4 P4.1 P4.2 P4.3 P5 P5.1 P5.2
This product meets above listed legal requirements

Page 2 (4)

Product Identity Issue date
Product environmental attributes - Market requirements

Item P6 P6.

1 P6.

2 P6.

3 P6.

4 P6.

6 P6.7
V = Voluntary to answer. Additional information regarding each item may be found under P14. Environmental conscious design Disassembly, recycling
Gluing/welding of different material has been avoided.
Plastic materials in covers/housing are free from surface coating.
Mechanical plastic parts >100g, consist of one material or of easily separable materials.
Plastic parts >25g, have material codes according to ISO 11469.
If labels are required they should be separable. (This requirement does not apply to safety labels).

Product lifetime

Upgrading of the product can be done with commonly available tools
Processor, memory and cards of various types can be changed/upgraded.
Hard disk, CD/DVD drives and / or floppy drive can be changed/upgraded.

P6.5 V

Plastic parts are free from metal inlays or have inlays that can be removed with commonly available tools.

P6.10 V

Spare parts are available after end of production for: P6.11

Material requirements

Plastic parts >25g are free from PBB/PBDE, i.e less than 0.1% b.w.

5 years

P6.12 V
Plastic parts >25g are free from flame retardant substances/preparations above 0.1% classified as R45/46,
R50/51/52/53 and R60/61 (67/548/EEC)

P6.13

Chemical specification of flame retardants in plastic parts >25g according to ISO 1043-4 declared below:
Product cover/ housing: FR(40) Printed circuit boards: FR(16) V Other plastic parts: FR(40) P6.14 P6.15 P6.16 V P6.17 V P6.18 V P7 P7.1 P7.2 V P8 P8.1 V Product cover/housing material type, specified according to ISO 1043-1 Material type >PC+ABS Material type PC Electrical cable insulation material specification Light sources are free from mercury, i.e less than 0.1% b.w. If mercury is used specify: Number of lamps & max. mercury per lamp Mechanical plastic parts > 25g are free from lead (Pb), i.e. less than 0.1% b.w.

Batteries Product is free from batteries defined as hazardous (91/157/EEC)
Batteries are used that meet the European eco-label (EU Flower) criteria (2001/687/EC & 2001/686/EC)
Energy consumption n.a. Maximum power W V Operation Off mode Low power mode W Deep sleep mode Sleep mode W If the product is in Stand by mode, it reverts to: Low power mode in min Sleep mode in Deep sleep mode in min V Off mode in 2-sided printing/copying (duplex) from 1-sided originals is an integrated product function. n.a. W W W min min Material type ABS Other PVC mg
Product parts are free from beryllium (Be) and beryllium oxide (BeO), i.e. less than 0.1% b.w.

V P8.2 P8.3

P8.4 P8.5 V P8.6 V V
Information about the energy save function is given in the user documentation. (Not applicable when no instruction is needed to operate the energy save function, i.e. the energy save
function cannot be adjusted or inhibited by the user.)
The product meets the requirements of ENERGY STAR.
The product meets the requirements of GEEA.
Display meets the energy save requirements of the European eco-label (EU Flower) (2001/686/EC &

2001/687/EC).

Desktop or portable computer meets the energy save requirements of the European eco-label (EU Flower)
(2001/686/EC & 2001/687/EC)

Page 3 (4)

Product environmental attributes - Market requirements (continued)
Item P9 P9.1 P9.2 V V = Voluntary to answer. Additional information regarding each item may be found under P14. Noise characteristics (Measured and declared according to ISO 7779 and ISO 9296) Declared A-Weighted Sound Power Level, LWAd (1B = 10 dB) Operating mode: LWAd : 7 B Idling mode: LWAd : 6.9 B The product meets the acoustic noise requirement of:
TCO Blue Angel European eco-label (EU Flower) Nordic Swan
P9.3 V Declared A-Weighted Sound Pressure Level, LpAm (measured at the operator position if applicable; otherwise measured at the 1m bystander positions). Operating mode: LpAm: 53 dB Idling mode: LpAm: 50 dB Test position: LpAm: Operator position Bystander positions
Test position for PC tower LpAm:
Table top Floor standing P10 Emissions P10.1 , other standard , specify:
Chemical emission test performed according to RAL-UZ The test covers: Dust

Ozone Styrene TVOC Benzene P10.2 V The product meets the requirement for chemical emission in: TCO Blue Angel Nordic Swan P10.3 Display/monitor/portable computer meets the requirement for low frequency electromagnetic fields in: MPR-II TCO prEN50279- A , -B , -C Consumable materials The photo conductor is free from selenium. If the photo conductor contains selenium there is a system for waste recovery.

P11 P11.1 P11.2

P11.3 V Safety Data Sheet/Material Safety Data Sheet (SDS/MSDS) is available for toner/ink (99/45/EC & 2001/58/EC) P11.4 V Paper containing recycled fibres and meeting requirements of ENV12281 can be used in the product. P12 P12.1 P12.2 P12.3 P13 P13.1 Ergonomics The computer system meets the ergonomic requirements of EN 29241-3, -7, -8 for CRT displays and EN-ISO 13406-2 for flat panel displays. The product keyboard meets the requirements of ISO 9995 and EN 29241-4. The computer input device meets the requirements of ISO 9241-9. 5.5.32.86.45
Packaging and documentation Product packaging: material type(s): Corrugated paper weight (kg): EPE PP-E PS-E P13.2 V Plastic packaging material is marked according to DIN 6120, ISO 11469 or ISO 1043, 1-4. P13.3 V Product plastic packaging is free from chlorine P13.4 V User and product documentation are free from chlorine bleached paper P14
Additional information "The IT Eco Declaration covers the product base model only. If optional items with moving parts are added, like extra hard disks or graphic cards with fans etc, these can change energy and acoustics values for which HP can take no responsibility."

Page 4 (4)

HP StorageWorks VLS Data Migration Solution using HP StorageWorks 6000 Virtual Library System and HP OpenView Storage Data Protector
Introduction..... 2 About object copy.... 2 Prerequisites.... 2 Limitations..... 2 About the Virtual Library System... 3 Solution details.... 4 Device configuration.... 5 Autoconfiguring VLS libraries and devices... 6 Configuring drive settings..... 7 Configuring multi-path device path listings... 8 Object copy configuration.... 10 Creating an object copy specification.... 10 Filtering available objects to be copied... 11 Selecting where the Cell Manager writes the object copy.. 12 Restoring from object copy..... 14 Summary..... 15 For more information.... 16

Introduction

Disk-based backup has been a part of data protection solutions for years, but has never had the portability or the ease of functionality of traditional tape-based backup. With the advent of virtual tape devices such as the HP StorageWorks VLS6000-series, the backup and restore speeds that customers need and the ability to integrate seamlessly into existing backup application configurations are attainable. More recently, data protection solutions have escalated the need to migrate data offsite to comply with disaster-recovery requirements. Also, new regulations concerning long-term data retention pose challenges for those looking to take advantage of virtual tape devices in their environments. These needs can be met by the HP StorageWorks Virtual Library System (VLS) Data Migration Solution using HP OpenView Storage Data Protector, HP StorageWorks 6000 Virtual Library System and HP StorageWorks Tape Libraries. The object copy functionality in Data Protector allows primary backup jobs written to the VLS to be migrated to physical tape. The solution is to create a data protection cycle that incorporates the existing backup window, adds the speed of the VLS as a primary shortterm restore cache, and introduces a migration period outside the backup window during which data is moved from the VLS to physical tape for longer-term retention.

About object copy

With the object copy function, introduced with Data Protector 5.5, customers can copy one or several selected object versions (backup jobs) to a specific media set. During the object copy session, Data Protector reads the backed up data from the source media, transfers the data, and writes it to the target media. In this solution, the object copy reads data from a backup on the VLS and writes it to physical tape. Object copy sessions can be started interactively or set to run automatically with a schedule similar to a regular backup job. Object copies can be appended to media containing existing object copies to maximize the use of a physical tape. The following prerequisites and limitations are required when using object copy sessions with Data Protector.

Prerequisites

The Data Protector Media Agent must be installed on every system that will participate in an object copy session. At least two backup devices must be configured in the Data Protector cell.

Limitations

It is not possible to copy objects backed up using either the Zero-Downtime Backup function to disk or the NDMP backup functionality. Multiple copies of one object version cannot be created in one object copy session. The destination devices must have the same or a larger block size than the source device.
Important: In the case of this solution, all block sizes, segment sizes, and disk agent buffers for the backup devices were configured with the same settings. Complications can result with different settings (explained later in this document).
For more information on the object copy functionality in Data Protector, see the HP OpenView Storage Data Protector V5.5 administrators guide.
About the Virtual Library System
The HP StorageWorks VLS6000 Virtual Library System seamlessly integrates into existing backup configurations and provides accelerated backup and restore performance in complex SAN environments. A unique configuration within the backup application is not required because of the ability of the VLS to emulate existing tape devices and libraries. VLS presents individual virtual libraries and drives to Data Protector Media Agent servers, enabling simultaneous backup of many systems. Not only does this help reduce backup window times, it eliminates the need for data interleaving that might be necessary to improve performance. Simultaneous backups, along with quicker restores from data residing on the disk, help provide dramatically improved restore performance.

Figure 1. HP StorageWorks VLS6100, VLS6500, VLS6800 Virtual Library Systems
The table below lists the HP StorageWorks VLS6000-series models and the maximum capacities.
Models VLS6105 VLS6109 VLS6510 VLS6518 VLS6840 VLS6870 Maximum capacities 5 terabytes 8.8 terabytes 10 terabytes 17.6 terabytes 40 terabytes 70.4 terabytes
VLS can emulate the HP ESL E-Series and MSL tape libraries as well as 1/8 autoloaders. The VLS 6000 emulates the HP Ultrium 230 (LTO1), HP Ultrium 460 (LTO2), HP Ultrium 960 (LTO3), DLT 7000, DLT 8000, and SDLT 320. For more information on Virtual Library Systems, access the VLS website at: http://h18006.www1.hp.com/products/storageworks/6000vls/index.html.

Solution details

The VLS Data Migration solution was designed around a configuration in which a VLS would be inserted. For example, the backup environment might contain a Data Protector Cell Manager server and multiple production servers with the Data Protector Media Agent installed. All these servers are sharing and writing to a tape library over the SAN (see Figure 2). In a typical VLS deployment, these Media Agent servers are not writing to tape at a sufficient speed. Because of this, tape drives are being occupied for long periods of time, causing other backup jobs to wait, which lengthens the backup window. With the VLS integrated, multiple virtual libraries and drives can be created, allowing many more or all of these slower servers to back up to the VLS simultaneously. Since more simultaneous writes reduce or even eliminate the wait for backup jobs, the backup window is reduced. Although the backups complete within the window, the data must be: Sent offsite to comply with company disaster-recovery policies Maintained and available for restore for an extended period of time, which might exceed the capacity of the virtual library
Figure 2. Example solution environment
The VLS acts as a staging area where backup jobs are initially written, and after a designated period of time, data is migrated to physical tape. The increased backup performance can be maintained without compromising disaster-recovery or regulatory compliance requirements. Backup jobs can be maintained on the VLS for a few days, allowing for quicker restores when most restore requests are made. Object copies of the VLS backup jobs can be made during this time, and once the retention window for the VLS-collected data expires, the virtual cartridges can be recycled, freeing up space for new backup jobs. Meanwhile, the object copies, now written to physical tape, can be moved offsite. In addition, copies of the object copies can be created, allowing for one physical copy to remain onsite while the other is sent offsite. The VLS Data Migration Solution creates a data protection/migration cycle during a 24-hour period in which backups are written to the VLS during off-peak production hours and object copy jobs are run during peak production periods (see Figure 3).

The advantage of Data Protector's Object Copy functionality is that an alternate Media Agent server, the Cell Manager in this case, can handle the entire transfer from VLS to physical tape without involving the original Media Agent server. This eliminates additional overhead on the production server.
10pm 9pm 8pm 7pm 6pm 5pm 4pm 3pm 2pm

12am 1am

2am 3am 4am 5am 6am 7am

Backup to Virtual Tape

Object Copy to Tape

1pm 12pm 1 1am 10am

8am 9am
Figure 3. 24-hour backup/object copy cycle

Device configuration

The device autoconfiguration wizard used for configuring tape libraries in Data Protector greatly simplifies the configuration process, especially in an object copy solution. With separate VLSpresented virtual libraries for each Media Agent server, as well as the physical library used by all Data Protector servers in the cell, manual configuration would be extensive and possibly confusing. Employing the wizard and taking advantage of Data Protectors MultiPath device sharing capabilities reduces configuration time for this solution to a matter of minutes. The autoconfiguration wizard determines the device names, lock names (used to prevent shared devices from being accessed simultaneously), media type, media policy, and the device file or SCSI address of each device in the library, and configures the drives and slots. After running the wizard, manual changes can be made to customize the devices as necessary in a particular configuration. The lock names are the key to the MultiPath functionality that allows automatic device sharing within Data Protector. Without MultiPath, devices to be shared by multiple hosts had to be manually configured with the same lock name to avoid simultaneous access. When MultiPath is chosen within the autoconfiguration wizard, the lock name configuration is handled automatically. The order in which MultiPath device paths are configured will be the preferred order of use for a particular job. In other words, if server As path to a shared device is listed before server Bs path in the properties of the device in Data Protector, server As path will be the first one tried. This may not always be preferable, especially when trying to ensure that all data is backed up to tape over the SAN for best performance. Preferred paths can be defined for backup jobs within Data Protector, which will override the device path listing in the device properties. Setting the preferred path for backup jobs makes sure that each Media Agent server will write to tape using its own device path over the SAN. However, preferred paths cannot be set for the source device on object copy jobs or restores of object copy data. Since a main goal of this configuration is to ensure that backup jobs, object copy jobs, and restores of object copy data all are transferred over the SAN, additional adjustments will need to be made to the device configuration.

In the scenario used to test this solution, one Data Protector 5.5 Cell Manager and four production servers with Data Protector Media Agents installed have been zoned on the SAN to see the VLS and the physical library. On the VLS6840, one library and one drive per library was configured for each Media Agent server. The VLS6840 has four available Fibre Channel ports to present virtual devices to the SAN. In order to simplify things, each library was presented out its own Fibre Channel port on the VLS unit. This allowed selective LUN presentation by zoning only the appropriate FC port to each Media Agent server. The Cell Manager HBA had all four FC ports zoned to it.
Note: The VLS can selectively present LUNs. If more virtual libraries than FC ports are required, this feature can be used to preserve the environment being described. For more information on LUN presentation with the VLS, consult the HP StorageWorks VLS6000 administration guide.
In addition, all servers had the physical library zoned to their respective HBAs. As a result, each Media Agent server saw two librariesits VLS virtual library with one drive, and the MSL6060 with four drives. The Cell Manager saw five librarieseach VLS virtual library and the MSL6060. After the devices have been presented and the appropriate steps taken to create device files for the respective operating systems, the libraries must be configured within Data Protector.
Autoconfiguring VLS libraries and devices
In the following example, the MSL6060 physical library has already been configured as a multi-path device, shared by all servers. Three of the four VLS virtual libraries have been configured, one at a time, and now the fourth one needs to be set up.
1. Right-click Devices in the left panel to start the Autoconfiguration Wizard. 2. In the Client Systems window, select the Cell Manager and the appropriate Media Agent server 3. Click Next to continue (see Figure 4).
Figure 4. Device Autoconfiguration Wizard Client systems
4. Select the VLS virtual library that both servers share.
5. Click Next (see Figure 5). 6. On the next screen, select the box next to Automatically discover changed SCSI address. This

allows Data Protector to handle LUN address changes that might occur as a result to changes on the SAN. 7. Click Finish to create the library.
Figure 5. Device Autoconfiguration Wizard Devices
Configuring drive settings
HP recommends changing the name of the VLS library and its virtual drive(s) to reflect the Media Agent server (see Figure 6 and Figure 7). Configure the drive settings under the Settings tab to be the same as all the other drives in all other libraries. By ensuring that all the drives have the same block size, data segment, and data buffers settings, compatibility issues between source drives and destination drives in object copy sessions can be avoided.
Figure 6. Renaming the virtual library
Figure 7. Renaming the virtual drive
Configuring multi-path device path listings
After creating the library and configuring the drive settings, the multi-path device path listing for each drive must be configured so that the Cell Manager path is the first path listed. As stated earlier, preferred paths can be set for backup jobs but not for source devices in object copy jobs. Recall that in this solution, preferred paths are to be selected for each VLS virtual drive to ensure that the Media Agent server path sends the backup data over the SAN. By altering the device path listing to ensure that the Cell Manager path comes first, this will allow the Cell Manager to handle the object copy data transfer (also over the SAN), since Data Protector uses the listing order by default. This satisfies another main goal of the solution to remove excess overhead from production servers. To alter the device path listing:
1. Expand the entry for the virtual library and right-click on the drive entry to access Properties. 2. Click the Drive tab and, in the Configured paths window, select the drive path for the Cell

Manager (see Figure 8).

Figure 8. Selecting Cell Manager device path -- properties
3. On the right side of the window, click the up arrow until the Cell Manager path is at the top of the

list (see Figure 9).

Figure 9. Adjusting device path listing -- properties

4. Click Apply.

Object copy configuration
The object copy portion of the cycle is typically set up to occur outside of the normal backup window, to avoid interference with the backups themselves and to take advantage of idle Cell Manager and library time. In the test scenario, the backups occurred overnight, so the idle period happens during the business day. The Media Agent servers are busy during the business day, acting as production servers. Therefore, the overhead associated with object copy sessions needs to be handled solely by the alternate Media Agent server, in this case, the Cell Manager. The test scenario uses the following process.

Creating an object copy specification
To create an object copy specification:

1. 2. 3. 4. 5.

Access the Copy section in the drop-down menu of Data Protector Manager. In the left panel, click Object copy and Automated. Right-click Scheduled to select the Add wizard. In the right panel, give the specification a unique name (see Figure 10). Click Next.
Figure 10. Creating the backup solution
6. In the Backup Specifications window, select Selected backup specifications (see Figure 11). 7. In the selection window, select the backup specification for the appropriate Media Agent server. 8. Click Next.
Figure 11. Creating the backup specification (continued)
Filtering available objects to be copied
Set up the filter carefully to only include the backup job run the night before. Data Protector will perform an automatic copy of all the available copies designated by the filter, which may end up being the object copy created yesterday. Therefore, HP recommends limiting the Relative time and Duration (hours) settings to the time period between the start of the previous nights backup job and the start time of the current object copy job. Click Next (see Figure 12).
Figure 12. Setting the relative time specifications
1. In the Library Filter window, ensure that the library containing the backup job is selected (see 2. Select Selected libraries.

Figure 13).

3. Select the box next to the appropriate VLS virtual library. 4. Click Next.
Figure 13. Selecting the virtual library
5. On the Source Devices window that appears, ensure that the desired device is included in the 6. Click Next.

available list.

Selecting where the Cell Manager writes the object copy
To select where the Cell Manager will write the object copy:
1. In the Destination Devices window, select the physical library (see Figure 14). 2. Select a particular drive in the library and configure it to use the previously defined object copy 3. Select the box next to Use preferred multi-path host and select the Cell Manager. 4. Click OK. 5. Click Next.

media pool.

Note: There are two ways of configuring the destination drives. The entire library could be chosen, rather than an individual drive. This would allow Data Protector to select whichever drive path was available at the time. However, this means that every drive instance must be configured for the media pool and preferred multi-path host for each object copy specification. Conversely, when choosing a specific drive for each object copy specification, make sure that the same drive is not selected for use at the same time. The latter method was chosen to expedite testing.

Figure 14. Selecting where the Cell Manager will write the object copy
6. In the Options window, clear the Same as source box (see Figure 15). 7. Select Permanent in the Protection drop-down menu to make sure the object copy is protected
from recycling in the Internal Database.
Note: Do not check the Recycle data and catalog protection after successful copy box. Since the original backup needs to remain available on the VLS for the designated time period, this box cannot be checked.
8. Click Next to proceed to the scheduling window, where the object copy sessions can be
scheduled to run during the desired copy window. Multiple jobs from different servers can run concurrently, but only one object copy can run per server at a time. 9. After completing the schedule, proceed to the Summary window to review all the choices for the specification. 10. Click Finish to save the specification.
Figure 15. Selecting the protection level of the target object
Restoring from object copy
After the data has been migrated to physical tape, it must still be available for restore to the original server. The device path rules for Data Protector state that during a restore session, the first choice for device paths are paths that are on the client to which the data is restored, if all objects are restored to the same target client. So, object copy data can be restored over the SAN directly to the Media Agent server without any additional configuration. Restoring from object copies in Data Protector is very similar to standard restore jobs:
1. Select Restore from the Data Protector Manager drop-down menu on the taskbar (see Figure 16). 2. To select specific data from the copy, open the Filesystem folder, select the appropriate server,
and the data to be restored.
Figure 16. Selecting the data to restore
3. Under the Copies tab, highlight the selected version (see Figure 17). 4. Click Properties. From here, the source copy can be changed to the object copy version on
physical tape. 5. Select Select source copy manually and select the copy version from the drop-down menu. 6. Click OK. The field under Auto select copy will change to No, reflecting the manual selection. 7. Click Restore. Data Protector will begin restoring the data.

Figure 17. Selecting the source copy manually

Summary

The HP StorageWorks VLS Data Migration Solution provides a systematic way of protecting data long term, while taking advantage of the performance and time-saving features of the VLS6000-series libraries. By constructing a cyclical configuration that maximizes the device usage and improves the existing backup window, customers can comply with corporate and governmental disaster-recovery and data-retention requirements. By configuring Data Protector in this manner, backups, copies, and restores can all take advantage of the SAN fabric bandwidth for improved overall performance.

For more information

www.hp.com/go/ebs www.hp.com/go/dataprotector www.hp.com/go/tape
2006 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Itanium is a trademark or registered trademark of Intel Corporation in the U.S. and other countries and is used under license. 439401-001, November 2006