Transcription

hp OpenViewOmniback IItechnicalwhitepaperUsing hp OpenView Omniback IIGUI Via Slow Remote Connections

Using Omniback II GUI via slow remote connectionsTechnical WhitepaperTable of Contents1.Introduction . 32.Omniback II GUI changes from 3.x to 4.x. 43.Using Omniback II GUI via Dial up connection. 53.1.Using native Omniback II GUI and command line . 53.2.Using emulation programs based on X window. 63.3.Using emulation programs based on a two tiered PC X server architecture . 73.3.1.Exceed onDemand . 83.3.2.VNC. 93.4.4.Monitoring session . 10Performance Tests . 114.1.Test environment . 114.1.1.System configuration . 114.1.2.Network configuration . 114.1.3.Configuration of the X Windows software. 124.1.4.Configuration of Omniback II / Data Protector. 124.2.Test results. 134.2.1.5.-1-Explanations of the tasks. 15Conclusion . 16

Technical WhitepaperUsing Omniback II GUI via slow remote connectionsTable of FiguresFigure 2-1 Building blocks of the Omniback II GUI . 4Figure 3-1 sharing windows using a X server on a windows system . 7Figure 3-2 Exceed onDemand Configuration setup . 8Figure 3-3 VNC configuration setup . 9-2–

Using Omniback II GUI via slow remote connectionsTechnical Whitepaper1. IntroductionWith Omniback II version A 04.00 a new GUI was introduced. Using this GUI via slow remoteconnection with conjunction of X windows software may result in worse performancecompared to version A 03.50. The main goal of this document is to address this issue.This Whitepaper describes different approaches on how to use the Omniback II GUI via aslow dial up connection. In case the native GUI, available on HP-UX, Sun Solaris, WindowsNT, Windows 2000 and Windows XP can’t be used, the so called X emulation programs areused on Windows platforms to enable a connection to the Unix system where Omniback II isrunning.There are two different kind of emulation software. One type consists only of client software,which implements an X server (X is a generic name for the X Window System display server).On Unix machines there is no additional software necessary since the X server, running onthe Windows system, communicates via the X protocol directly with the X application on theUnix machine. The second type of emulation program requires software on both. On the Unixmachine a X server is running, which communicates with the X application, and on theWindows system a special client software enables the connection to the X server on the Unixmachine. The communication is based on a proprietary standard.When an Omniback II GUI is started, based on such emulation programs in conjunction with aslow remote network connection, there are performance differences between these two kindsof emulation software. This whitepaper describes the concepts of these two different kinds ofemulation software and explains what formulates the distinctions.Additionally, it explains how to use the native GUI, including the command line, whichachieves the lowest data flow over the network and therefore the best performance.This whitepaper is based on Omniback II A.04.10 and Data Protector A.05.00.-3-

Technical WhitepaperUsing Omniback II GUI via slow remote connections2. Omniback II GUI changes from 3.x to 4.xWith Omniback II A.03.xx, two different GUI were available; one for HP-UX as a Motif GUIand the other for Windows platforms. Although, nearly identical functionality was available inboth GUIs, the handling and look & feel were totally different.With version A.04.00, Omniback II introduced a new GUI on HP-UX, which is consistent to theone on Windows platform. This new GUI has the same look & feel, menu structure anddialogs as the Windows GUI. The great advantage is that users have the same user interfaceregardless of what platform they use.To get this cross platform consistent GUI, the GUI running on Windows was ported to HP-UX.This was done using the tool Wind/U of Bristol Technology. Wind/U mainly consists oflibraries that implement the Microsoft Win32 API, including features such as MFC (MicrosoftFoundation Class), ActiveX, and COM on major UNIX platforms. This allows that code, whichwas written for Windows environments, can be compiled and executed on major UNIXplatforms.Please note that Wind/U is not a virtual machine, which simulates a PC. Wind/U allows tocompile Windows Code and produces native Unix binary code, which then can be executedon the corresponding Unix machine.Figure 2-1 Building blocks of the Omniback II GUIApplicationSource CodeActiveX & MFCWin32Windows95/98/2000WindowsNTWind/U (Wind32)SUNHPIBMSGIOther-4–

Using Omniback II GUI via slow remote connectionsTechnical Whitepaper3. Using Omniback II GUI via Dial up connectionWhen working with Omniback II, it is recommended to install an Omniback II GUI locally onthe system. In case of a slow dial up connection or in case that only an ASCII connection canbe established, it is recommend to use the command line interface. The best networkperformance can be achieved with a locally installed GUI/CLI.If the so-called X emulation programs are used then the setup must also be adjusted to suitOmniback II requirements to achieve an acceptable performance via slow remoteconnections, for example a 56kbs modem connection.The startup time of the Omniback II 4.x GUI can be very slow, dependent of the used Xwindows program. It can last up to 1 hour, for detailed numbers see chapter 4. With DataProtector 5.0 the startup time over slow remote connections is decreased dramatically, so allX windows emulation program achieves acceptable results (up to 4 minutes). To get similarperformance values also for Omniback II 4.1 the patch SSPUX410 054 must be installed.3.1.Using native Omniback II GUI and command lineOmniback II offers a GUI for HP-UX, Sun Solaris and Windows platforms (NT, 2000, XP). Itcan be installed locally or also remotely by the Installation Server. The Ommiback II GUIdoesn’t require additional licenses. Please refer to the Omniback II installation manuals.In addition to the graphical user interface, Omniback II also offers a command line interface.Especially, for very slow remote connections it is recommended to use the command lineinterface, since it reduces the network traffic to a minimum.All functionality is available via the command line interface. For a complete description pleaserefer to the Omniback II documentation. Please see below for an overview of commands tostart, monitor and stop a backup sessions.start a backupfilesystemomnib -datalist backup specification name [additional options]oracle 8omnib -oracle8 list backup specification name [additional options]sapomnib –sap list backup specification name [additional options]start a restorefilesystem-5-omnir -filesystem system name : mountpoint ' label ' -session

Technical WhitepaperUsing Omniback II GUI via slow remote connections session id -tree file specification [additional options]sapomnir -sap system name : Set ID -session session id -tree filespecification [additional options]monitor/view sessionsonly active sessionsomnistatall sessionsomnidb -sessdetailed information of aomnidb –sess session id -detaildedicated sessionmessage information of aomnidb –sess session id -reportdedicated sessionabort a backupabort active session3.2.omniabort –session session id Using emulation programs based on X windowIf the local Omniback II GUI can’t be used and if there is a need to have an Omniback II GUIstill available, then so called X-windows programs can be used to share windows of an Xapplication from a Unix to a Windows system. Tools like Reflection X and Exceed providesuch functionality.Figure 3-1 illustrates the concept: such software, also called PC X server, manages visualdisplay on a Windows system, which comes from a X client application program. The X serverconveys user input information, such as the click of the mouse or a keystroke, to theappropriate client application. Client applications communicate their display requests to the Xserver. The X server and client application can reside on the same computer or on differentcomputers connected by a network.-6–

Using Omniback II GUI via slow remote connectionsTechnical WhitepaperFigure 3-1 sharing windows using a X server on a windows systemWindwowsSystemUnix CellManagerH9000XapplicationX protocolWAN(slowbandwithconnection)X serverAs showed in Figure 3-1 the X server running on Windows system communicates to the Xapplication (Omniback II GUI) via the X protocol. As described in chapter 2, the Omniback IIGUI running on Unix is not a real native Motif GUI, since Windows NT/2000 code togetherwith Wind/U is used to create native HP-UX code. Wind/U is based on Microsoft technologyand doesn’t follow the X protocol standard. This limitation has an impact on the network load:although it works the resulting network load is high and therefore, such a setup can’t berecommended for a slow remote connection. The main reason for this high network load isthat Wind/U components are basically implemented as extended MOTIF controls.Other emulation programs that don’t use the X protocol to send data via a slow remoteconnection, like Excced onDemand or VNC don’t have this limitation. They achieve a goodand acceptable performance via slow network connections. The next chapter will describethose configurations in detail.3.3.Using emulation programs based on a two tiered PC X serverarchitectureThis chapter describes another approach of sharing a Unix GUI on a PC. The biggestdifference is that the communication over the slow remote connection is not done via the Xprotocol. Due to proprietary, highly optimized protocols those program achieve acceptableperformance result when sharing the Omniback II GUI via slow remote connections. The twoprograms Exceed onDemand and VNC are described below.-7-

Technical WhitepaperUsing Omniback II GUI via slow remote connections3.3.1. Exceed onDemandThis program consists of an X Server and an Exceed onDemand client. The X server isrunning on the Unix system. This has the advantage that the communication with the Xapplication (Omniback II GUI) is done within the LAN. The communication between the Xserver and the Exceed onDemand client is done via the slow dial up connection . Thefollowing figure shows the configuration setup.Figure 3-2 Exceed onDemand Configuration setupH9000Unix SystemHH90009000LANH9000X applicationsystemsX ApplicationExceed onDemand Server(X Server)Thin X ProtocolWAN(slowbandwithconnection)Exceed onDemandClientExceed onDemandClientExceed onDemandClientThe key differentiator is that both the X application and the X server could run on the samesystem. The X server (Excceed onDemand server) can also be used for other Unix systemsconnected to the LAN. This results into the fact that the exchange of information via the Xprotocol is done either locally or within the LAN. Please see the Exceed onDmenaddocumentation for more information. The communication across the slow remote connectionsis done via the Thin X protocol, which is highly optimized for slow remote-connections.-8–

Using Omniback II GUI via slow remote connectionsTechnical WhitepaperMore information can be found @ http://www.hummingbird.com/solutions/.3.3.2. VNCVNC stands for Virtual Network Computing. It is, in essence, a remote display system whichallows you to view a computing 'desktop' environment not only on the machine where it isrunning, but from anywhere on the Internet and from a wide variety of machine architectures.The VNC protocol is a simple protocol for remote access to graphical user interfaces. Itoperates over any reliable transport such as TCP/IP. It is truly a “thin-client” protocol: it hasbeen designed to make very few requirements of the viewer. The Figure 3-3 shows how VNCis setup and works. VNC Server software must be installed on the Unix system while VNCviewer is necessary on the client side.Figure 3-3 VNC configuration setupX applicationsystemsH9000H9000H9000LANHWindows System9000WAN(slowbandwithconnection)X ApplicationVNC Server (Xvnc)VNC protocolVNCviewerThe VNC Server software Xvnc is based on a standard X server. Applications can displaythemselves on it as if it were a normal X display, but they will actually appear on anyconnected VNC viewers rather on a physical screen. Therefore Xvnc is two servers in one: Tothe applications it acts like an X server, and like a VNC server to the remote VNC users. Byconvention, the VNC server display number will be identical to the X server display number,which implies e.g., host1:2 will refer to display 2 on machine host1 in both the X world and theVNC world.-9-

Technical WhitepaperUsing Omniback II GUI via slow remote connectionsVNC is free and can be downloaded, used and redistributed under the terms of the GNUPublic License. Both binaries and source code are available from the following tml.3.4.Monitoring sessionIf the current sessions are monitored and the GUI is running over a slow remote connection itis recommended to change the default refresh rate from 5 seconds to a higher value. Thisreduces the network traffic. The value can be changed under File- Preferences - Monitor Refresh interval. This value affects only the screen where the current sessions are shown.If the detailed information (backup objects, backup device, message) is shown in the GUI andthe GUI is connected to the Cell Manager via a slow remote connection, then such a setupcan influence the backup performance. In case the detailed information is shown in the GUI adirect socket connection is established with the Cell Manager. A process running on the CellManager (backup session manager) is responsible to update all connected GUIs with thelatest information, which was sent from the backup system (media agent). In case it takesvery long to transmit all new data to the GUI, then this can influence the backup performancein total. Therefore it is recommended to see the detail information of a session only if it isneeded and to change to context within the GUI when the detailed session information is notrequired.- 10 –

Using Omniback II GUI via slow remote connectionsTechnical Whitepaper4. Performance TestsThis chapter presents performance test results of the Omniback II / Data Protector GUI that isshared via slow remote connections with X window programs. Four different tools were part ofthese tests: Reflection X, Exceed, Exceed onDemand and VNC.4.1.Test environment- VNC Server- Exceed onDemandserver- Omniback II 4.1- Data Protector 5.0 (beta)H- VNC viewer- Exceed on Demand- Exceed- Reflection X9000WAN(slowbandwithconnection)Unix SystemWindows System4.1.1. System configurationUnix SystemHP-UX 11.00; 256Mbyte RAMWindows SystemWindows NT 4.0; Service Pack 5; 192 Mbyte RAM4.1.2. Network configurationTwo different software was used for the connection via the telephone line. First with PAL anetwork connection was established. Second the Extranet software was used to connect tothe Intranet via the firewall. The following table describes the used software in detail:PALPhone Assist Lookup v4.1ExtranetExtranet Access client V02 62 47Security: ESP Triple DES, SHACompression: LZS Compression- 11 -

Technical WhitepaperUsing Omniback II GUI via slow remote connections4.1.3. Configuration of the X Windows softwareExceedX server tune-up performed (at the end of the installation)version 7.1.0.0ExceedClient: version 3.2onDemandServer: version 3.2 (without SSL)Patch 3.2.0.6 installed(used optimal settings according to the patch description)Reflection XVersion 6.2VNCClient version 3.3.34.1.4. Configuration of Omniback II / Data ProtectorOmniback II 4.1HP OpenView OmniBack II A.04.10installed patches:PHSS 25963 1.0 OV OB4.10 patch - CS packetPHSS 25965 1.0 OV OB4.10 patch - CORE packetPHSS 26220 1.0 OV OB4.10 patch - MA packetPHSS 26342 1.0 OV OB4.10 patch - CC packetPHSS 26344 1.0 OV OB4.10 patch - DA packetOmniback II 4.1 *HP OpenView OmniBack II A.04.10installed patches:PHSS 25963 1.0 OV OB4.10 patch - CS packetPHSS 25965 1.0 OV OB4.10 patch - CORE packetPHSS 26220 1.0 OV OB4.10 patch - MA packetPHSS 26342 1.0 OV OB4.10 patch - CC packetPHSS 26344 1.0 OV OB4.10 patch - DA packetSSPUX410 054Data Protector 5.0HP OpenView Storage Data Protector Beta version A.05.00(Internal build version 172)- 12 –

Using Omniback II GUI via slow remote connections4.2.Technical WhitepaperTest resultsThe numbers are given in “minutes: seconds”. The small numbers in brackets show the usedbandwidth in kbit/s.VNCStartup Time4.14.1 *5.0ExceedReflectiononDemandX1:07 (42,6)59:45 (46,6)37:02 (42,6)33:00 (46,6)1:03 (44,0)51:29 (46,6)42:43 (37,0)34:41 (46,6)58:12 (44,0)37:15 (44,0)0:40 (44,0)4:37 (44,0)5:20 (44,1)9:30 (41,3)0:55 (44,0)4:21 (44,0)4:36 (44,1)8:40 (41,3)0:28 (44,0)0:51 (44,0)4:33 (44,1)8:20 (4,41)0:50 (44,0)4:46 (44,1)8:00 (4,41)3:00 (46,6)3:08 (42,6)3:08 (46,6)1:58 (44,0)3:05 (42,6)5:02 (44,0)1:12 (44,0)ExceedlocalGUI0:050:050:053:40 (44,0)switch4.10:20 (42)context1:15(46,6)1:18 (42,6)2:01 (44,0)0:030:031:13 (44,0)1:20 (44,0)4.1 *5.00:10 (44,0)2:00 (46,0)1:19 (42,0)2:01 (44,0)0:15 (44,0)1:45 (46,0)1:20 (44,0)2:05 (41.3)0:16 (44,0)1:40 (46,0)0:15 (44,0)0:21 (44,0)2:00 (41.3)0:38 (42,6)0:56 (46,6)0:031:10 (44,0)start / stop4.10:42 (44,0)1:55 (44,0)3:20 (44,0)3:13 (44,0)0:15backup4.1 *0:49 (44,0)1:55 (44,0)3:56 (42,0)3:25 (41,3)0:150:55 (44,0)0:59 (44,0)4:02 (44,0)4:45 (41,3)0:28 (44,0)0:57 (44,0)5.00:35 (44,0)1:05 (44,0)4:11 (44,0)3:20 (44,0)0:154.10:25 (42,6)5:58 (44,0)3:51 (42,6)4:13 (44,0)0:040:04reconnect5:30 (41,3)4:58 (37,0)4.1 *0:40 (44,0)3:15 (44,0)2:44 (42,0)7:50 (41,3)0:30 (44,0)3:11 (44,0)2:26 (44,0)6:10 (41,3)0:25 (44,0)2:55 (44,0)2:55 (41,3)0:25 (44,0)5.00:24 (44,0)3:00 (41,3)0:35 (44,0)2:14 (42,6)2:26 (46,6)3:02 (44,0)- 13 -0:04

Technical Whitepaperchanging4.1Using Omniback II GUI via slow remote connections0:32 (42,6)preference0:59 (44,0)1:42 (42,6)0:55 (44,0)2:35 (37,0)2:12 (46,6)0:080:082:03 (44,0)4.1 *0:30 (44,0)2:10 (44,0)2:28 (42,0)8:05 (41,3)0:25 (44,0)0:52 (44,0)2:15 (44,0)2:25 (41,3)0:27 (44,0)1:00 (44,0)1:50 (44,0)2:35 (41,3)2:26 (42,6)2:04 (46,6)0:46 (44,0)5.00:27 (44,0)0:24 (44,0)0:21 (44,0)0:082:51 (46,6)NOTE: For some actions the numbers are deviating. M