Performing Backups and Restoring Objects
You can back up development objects on workstations and servers as frequently as necessary.
Consider these scenarios and solutions when developing your backup strategy:
A company does not allow the developers to back up directory data to the server because of space concerns.
Developers are required to check in their development objects at specific time intervals, such as every eight hours, to avoid rework. Unless you have unlimited disk space on a file server to enable developers to back up their entire path code directory, you must use the check-in process as your backup method. If you follow the recommended development process, developers will know that they can check in unfinished or malfunctioning applications to the DEV path code.
For workstation backups, end users should not have non-replicated data on their machines.
For development server backups: At a certain company, the IT department backs up both the development file server (normally the deployment server) and necessary databases (central objects, Object Librarian, and data dictionary).
When a developer needs to restore a particular object from backups, a database administrator restores the export to a path code called Restore. The developer checks out the object from Restore, ensures that the object functions as expected, and checks the object into the normal development path code.
For deployment server backups: In most cases, you do not need to back up the entire server nightly.
However, under certain conditions, you might need to back up these directories nightly:
The DEV path code, if you are modifying objects, building new packages, or updating the database that is delivered during a workstation installation.
MEDIA OBJ, if your media objects reside on the deployment server.
Data sources in Oracle or SQL Server, if your system data or any other important data is stored on the deployment server.
For enterprise server backups:
Back up the DBMS nightly.
You should use the backup tool that your database vendor provides.
Back up objects by backing up the entire directory.
Also back up the PROD and DEV path codes and the jde.ini file.
Path codes are updated when the Version Control administrator deploys an object that was modified by developers who are authorized to access the Server Package application, and by end users who create new batch versions that will be run on the server.