File Library and File Jukebox relocation in DP
Table of Contents Summary .......................................................................................................................................3 Introduction ....................................................................................................................................4 Scope ........................................................................................................................................4 Project Description ......................................
Summary The current versions of Data Protector, DP 5.5, 6.0 and 6.1, allow backup and restore in ESX VMware environments. An issue hereby is, that VMware does not support SAN attached tape libraries on the ESX Server system. Only smaller SCSI tape libraries can be directly attached to the ESX server. Therefore VMware backups to tape media in an Enterprise Backup Solution (EBS) usually go through the LAN.
Introduction Scope Figure 1 The recommended DP 6.1 ESX VMware ZDB integration With DP 6.1, ESX VMware Zero Downtime Backup (ZDB) is the recommended approach. As stated in the summary, technical consultants occasionally encounter severe obstacles when implementing the Advanced Backup to disk with a following copy to tape in VMware environments. For cases when the Data Protector ESX VMware ZDB Integration is not the appropriate choice, this document explains a possible alternate approach.
For the sake of completeness, we also mention the traditional import-methodology for the File Jukebox. To maintain a structured overview, detailed DP session output is to be found in Appendix B. Remark The reader of this document needs a profound knowledge of the product Data Protector. This is in particular true for the execution of the handed commands.
Initial Setup We defined in lab conditions a simple setup which is sufficient to proof our points. DP clients The first client system is named kiekeboe.company.com. Disk Agent and Media Agent components are installed on it. The Cell Manager, named lminnaert.company.com, will serve as the second node in our setup. Figure 3. Cell Manager lminnaert and DA/MA client kiekeboe Media Pool Next we defined a dedicated Media Pool TransJB to contain the media of our transportable File Jukebox.
Figure 4. Media Pool of transportable File Jukebox 'TransJB' Mount Points On host kiekeboe.company.com we created two mountpoints C:\FL and C:\JB under which the respective LUNs for the File Library and the Jukebox are to be mounted.
File Library We defined a File Library TransFL on host kiekeboe with two writers with its repository on the mentioned LUN. Figure 5. The File Depot Directory for File Library 'TransFL' File Jukebox as said before we’ll demonstrate the same action for a file jukebox to.
Figure 6. The Media Slots for File Jukebox 'TransJB' Detailed logical device info In this lab setup we posses now over the following libraries: C:\Program Files\OmniBack\bin>omnidownload -list_libraries Library name Host Library type ============================================================ Test1 lminnaert.company.com Jukebox Test2 lminnaert.company.com Jukebox TransFL kiekeboe.company.com File Library TransJB kiekeboe.company.
C:\Program Files\OmniBack\bin>omnidownload -library TransJB NAME "TransJB" DESCRIPTION "" HOST kiekeboe.company.com POLICY Jukebox TYPE File REPOSITORY "c:\JB\file01" "c:\JB\file02" "c:\JB\file03" "c:\JB\file04" "c:\JB\file05" "c:\JB\file06" "c:\JB\file07" "c:\JB\file08" "c:\JB\file09" "c:\JB\file10" MGMTCONSOLEURL "" And the drive details of the ones we will be using are: C:\Program Files\OmniBack\bin>omnidownload -list_devices -detail ….. …..
Datalists To run a backup-to-disk, we defined two datalists. One towards each of our two defined devices. Figure 7. Backup Specifications for 'TransFL' and 'TransJB' The details of Kiekeboe_2TransFL and Kiekeboe_2TransJB are to be found in the Appendix A. Both datalists were successfully executed and resulted in sessions 2008/07/19-1 and 2008/07/19-2. The session reports can be inspected in Appendix B.
Logical Device modifications By executing the last step in the previous chapter, we have taken a backup of our host kiekeboe to a local attached device. Imagine now we’d like to have this data onto tape media, but our host can’t reach a tape device. To perform a copy-to-tape anyway without having to pass the data via the LAN to another DP client who does see the tape drives, we will relocate our LUN’s with backup data upon and “notify” DP of these changes.
If identical mount-points can’t be maintained, the situation becomes pretty difficult. In another chapter we’ll indicate what can be done in such cases. Copy to Tape In our lab setup we had no physical tape drive at our disposal, hence we copied towards a null-device called BlackHole Copy-to-BlackHole Interactively we copied sessions 2008/07/19-1 and 2008/07/19-2. Both copy sessions 2008/07/25-8 and 2008/07/25-9 completed successfully though with a mount request which was simply confirmed.
Methodology Based on Traditional Import In the previous chapter the used relocation method was based on modifying the logical device definitions within the Media Management DB of course in combination with a real physical relocation of the respective LUN’s. This was shown for the File Library and the File Jukebox as well. For those who don’t like to download logical device definitions to change them, followed by an upload in the media management DB, there is the “traditional import“ method too.
Extra Jukebox definition On our Cell Manager itself we defined an extra File jukebox called ImportJB for the purpose to import the media labeled TransJB_2 (in slot C:\JB\file02) from jukebox TransJB on host kiekeboe into jukebox ImportJB on host lminnaert for a further object copy to tape in the next step. Figure 9. Jukebox 'ImportJB' on host lminnaert with one slot c:\4import\file It can be observed that here we do not have to maintain the same repository path.
Import of medium In the GUI we right clicked upon c:\4import\file to start a medium import. This import failed since the medium is already known in the Media Management DB. See the next figure. But the blue question mark in the previous figure changed to a green tape! And this was our only goal. Figure 10. Import media labeled 'TransJB_2' in slot c:\4import\file If we look to the details of the medium in the pool this is confirmed: Figure 11.
Copy-to-tape Now the data is relocated and this is known to DP, thus we can go ahead with our copy-to-tape. In our lab environment a copy-to-null-device. An interactive copy of the session 2008/08/11-1 was then executed in which we changed the original device TransJB_D1 to 4importD1. Figure 12. Object Copy from File Media to Tape The output of omnidb –ses 2008/08/12-2 –report is to be found in Appendix B.
Preparation new cycle Now that our data is saveguarded on a secure medium, we need to relocate the storage space so that the Media Agent on host kiekeboe can once again communicate with the slots in the jukebox TransJB. We do this by importing the media in TransJB. Figure 13. Import the media c:\JB\file02 in TransJB We got an unsuccessful completion, but the goal to get rid of the blue question mark for the given medium was reached.
With Repository Relocation In the first examples we relocated a file jukebox and a file library from a client to our CM and back using the same mointpoint names. Now we’ll see what’s to be done for an identical action when we change the mointpoints too. Note that this methodology is really cumbersome and error prone. On top of that it is a procedure which can not be executed “on-line”. Therefore we will only briefly indicate what needs to be done.
Instead of c:\ImpFL, apparently the original slot in c:\FL is looked up in the Media Management DB which is of course not reachable on our CM. (The mediumID is visible in the GUI when defining the copy session). For those who’d like to continue anyway, they have to see they can get exclusive access right to the IDB of DP. Meaning no other action or GUI’s can be open. This to execute: C:\Program Files\OmniBack\bin>omnidbutil -writedb -mmdb c:\temp\newMMDB 25/07/2008 15:57:39 Exporting libraries ...
Appendix A Datalists Kiekeboe_2TransFL DATALIST "Kiekeboe_2TransFL" DYNAMIC 1 5 DEFAULTS { FILESYSTEM { } RAWDISK { } } DEVICE "TransFL_Writer0" { } WINFS "C:" kiekeboe.company.com:"/C" { -trees "/AUTOEXEC.BAT" } Kiekeboe_2TransJB DATALIST "Kiekeboe_2TransJB" DYNAMIC 1 5 DEFAULTS { FILESYSTEM { } RAWDISK { } } DEVICE "TransJB_D1" { } WINFS "C:" kiekeboe.company.com:"/C" { -trees "/AUTOEXEC.
Appendix B Session Reports Session 2008/07/19-1 Backup Kiekeboe_2TransFL C:\Program Files\OmniBack\bin>omnidb -ses 2008/07/19-1 -report [Normal] From: BMA@lminnaert.company.com "TransFL_Writer0" Time: 19/07/2008 0:06:08 STARTING Media Agent "TransFL_Writer0" [Normal] From: BMA@lminnaert.company.com "TransFL_Writer0" Time: 19/07/2008 0:06:09 Loading medium from slot c:\FL\0301a8c05488113d150b105000b.fd to device TransFL_Writer0 [Normal] From: BMA@lminnaert.company.
Session 2008/07/19-2 Backup Kiekeboe_2TransJB C:\Program Files\OmniBack\bin>omnidb -ses 2008/07/19-2 -report [Normal] From: BMA@lminnaert.company.com "TransJB_D1" Time: 19/07/2008 0:06:36 STARTING Media Agent "TransJB_D1" [Normal] From: BMA@lminnaert.company.com "TransJB_D1" Time: 19/07/2008 0:06:37 Loading medium from slot c:\JB\file02 to device TransJB_D1 [Normal] From: VBDA@lminnaert.company.com "C:" Time: 19/07/2008 0:06:42 STARTING Disk Agent for lminnaert.company.com:/C "C:".
Session 2008/07/25-9 Object Copy from Kiekeboe_2TransFL [Normal] From: BMA@lminnaert.company.com "BlackHole" Time: 25/07/2008 16:45:00 STARTING Media Agent "BlackHole" [Normal] From: BMA@lminnaert.company.com "BlackHole" Time: 25/07/2008 16:45:01 nul Initializing new medium: "Default File_12" [Normal] From: RMA@lminnaert.company.com "TransFL_Writer0" Time: 25/07/2008 16:45:01 STARTING Media Agent "TransFL_Writer0" [Warning] From: CSM@lminnaert.company.
Session 2008/07/25-8 Object Copy from Kiekeboe_2TransJB [Warning] From: CSM@lminnaert.company.com "Interactive" Time: 25/07/2008 16:41:06[64:18] Some of the devices are occupied. Session is waiting for all the devices to get free. [Normal] From: BMA@lminnaert.company.com "BlackHole" Time: 25/07/2008 16:42:35 STARTING Media Agent "BlackHole" [Normal] From: BMA@lminnaert.company.com "BlackHole" Time: 25/07/2008 16:42:36 nul Initializing new medium: "Default File_11" [Normal] From: RMA@lminnaert.company.
Session 2008/08/11-1 Backup to file medium labeled TransJB_2 in slot c:\JB\file02 on device TransJB_D1 [Normal] From: BMA@lminnaert.company.com "TransJB_D1" Time: 11/08/2008 22:16:08 STARTING Media Agent "TransJB_D1" [Normal] From: BMA@lminnaert.company.com "TransJB_D1" Time: 11/08/2008 22:16:09 Loading medium from slot c:\JB\file02 to device TransJB_D1 [Normal] From: VBDA@lminnaert.company.com "C:" Time: 11/08/2008 22:16:14 STARTING Disk Agent for lminnaert.company.com:/C "C:".
Session 2008/08/12-2 Object copy from file medium written in session 2008/08/11-1 which is now located in c:\4import\file on device 4importD1 [Normal] From: BMA@lminnaert.company.com "BlackHole" Time: 12/08/2008 9:56:45 STARTING Media Agent "BlackHole" [Normal] From: BMA@lminnaert.company.com "BlackHole" Time: 12/08/2008 9:56:46 nul Initializing new medium: "Default File_13" [Normal] From: RMA@lminnaert.company.
For more information www.hp.com/go/dataprotector © Copyright 2008 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. Linux is a U.S.
