Determining better performance when the console is run locally or uses remote display back
Performance depends on the following:
The console may perform better if it is started on the console's application server host first, and then it is displayed back to the desktop host. However, little is known of a situation where that configuration produces better console performance. As previously mentioned, the configuration is not recommended due to problems unrelated to performance issues.
Consider the following scenarios to determine what would provide the best performance for your configuration.
Assume no deficiency in either the console host's resources or the application server host's resources. Assume that the amount of NetBackup configuration data being transferred to the console host far exceeds the X-Windows pixel display data. That is, the actual console screen being sent from the remote host.
Unfortunately, the only way to determine the viability of this situation is to try it. Network capabilities and the proximity of the two hosts influences each NetBackup configuration.
Assume that the available resources of the application server host far exceed that of the console host.
Assume that the console host has a very limited CPU and memory as compared to the NetBackup master server being administered. (The console host is the computer on which the console is started.) If the console is run on the master server and displayed back to the desktop host, performance may be enhanced.
If the desktop host is a Windows computer, X-terminal emulation or remote display tools such as Exceed and VNC are required.
These scenarios address the performance aspect of using the NetBackup console. There may be other reasons that require you to display back remotely to your desktop, however, it is not recommended. Review the release notes for additional issues of relevance to the NetBackup Administration Console and the Backup, Archive, and Restore client console.
Table: Files containing configuration entries shows the files that contain configuration entries.
Table: Files containing configuration entries