Best Practice For Hyperion Enterprise Backup and Virus Scanning.

Best Practice For Hyperion Enterprise Backup and Virus Scanning. [ID 1100507.1]
Modified 21-MAY-2010 Type HOWTO Status PUBLISHED
In this Document
Goal
Solution

Applies to:

Hyperion Enterprise - Version: 6.3.1.0.00 and later [Release: 6.3 and later ]
Information in this document applies to any platform.
Goal


Back-up guidelines for backing up an Oracle Hyperion Enterprise Application where Internal back-up is not used or in version where it is not available.

Virus Scanning best practice for Hyperion Enterprise Applications.


Solution


Best Practices for backing up an Hyperion Enterprise Application.

Terminology.

These notes use the term “Application Folder” (App Folder) to describe the Enterprise Database folder containing the Database files.

This is not the same as the “Software Folder” which contains the Executable code and associated DLL files etc

Note : the App Folder may be a sub folder of the Software Folder, please be aware of this. The location of both these folders are user definable at install/app creation time.

The default Software Folder being C:\Progam files\Hyperion solutions\Hyperion Enterprise.

Application Name (APPNAME) this is the “name “ of a particular Enterprise Database created by the user..

To identify your Software Folder, search for the file Hypent.exe, your should only have one copy, resident in your Software Folder.

The App Folder contains the following files amongst other.

APPNAME.EXA
APPNAME.INI
APPNAME.lok
APPNAME.use

It also has sub folders

\data
\reports
\inbox
\outbox

The App folder is again user definable but, the above sub folders are the default sub folder names.

The Application folder is defined by the APPPATH parameter in your Hypent.ini under each [APPNAME] section. You will find the hypent.ini in the citrix home folder or user profile folder.
Note the hypent.ini may contain several Application defined by the appropriate [APPNAME] sections.


BACKING UP

Always ensure there are no users logged on to any Enterprise or Reporting modeule when the back-up kicks off. Set a Back-Up Window (time) in which users know not to log on to the application while the back-up takes place.

Always back-up entire APP FOLDER never parts of APP FOLDER
.
RESTORING

Before restoring a back-up, ensure users are not logged in to any Enterprise or Reporting module..

When restoring you have the option to either overwrite the present app folder (suggest you clear it first). If you do overwrite the users will be able to connect to the restore with no changes needed.

If you restore to a new App Folder , the users will have to use the “Add Application” option at their logon screen to locate the restored folder and then add the restored application. When they do this, the reference to that particular application is overwritten with the new location within hypent.ini.

Note you can only have one instance of an APPNAME in your hypent.ini file at any one time.

When the users add an APPNAME that is already there, they get a message warning this will Overwrite the Application. It is only the link via the hypent.ini file that gets overwritten and not the Application itself.

Never restore partial applications. ALWAYS THE COMPLETE APP FOLDER.

If the software folder is damaged, run the install program again and select the REPAIR OPTION or run a complete re-install. If you restore a Software Folder form back-up you may run into file registration issues.

VIRUS SCANNING

The APP FOLDER should not be scanned live scanned for viruses.

Exclude the APP FOLDERS form live virus scanning.

Run a full scan over the APP FOLDERS daily when users are not active.

The danger is that the virus scanning software locks a file while scanning, and Enterprise cannot then lock the file itself.

Make sure users do not store office documents in the APP FOLDER as these can harbor viruses and need to be live scanned.
.
VERIONS 65 AND ABOVE

Enterprise version 6.5.x and 6,5,1.x include an internal back-up routine which does allow back-ups to be taken with active users.

This functionality was not available in earlier versions