IBM Licensed Programs: Systems Management Products 623
IBM Licensed Programs: Systems Management Products
– Positioning BRMS Application Client to ADSM
The AS/400 Application client to ADSM was introduced as a niche BRMS function to
help customers in an enterprise ADSM environment, who need to manage small,
remote systems where there is no skilled resource to handle the backups. The AS/400
Application Client to ADSM should not be used as the backup solution for
mainstream, central site AS/400 system. Native BRMS saves to traditional tape drives
continue to be the recommended IBM strategic solution for AS/400 backups.
Customers interested in using the AS/400 Application client to ADSM should be
aware of the following considerations related to performance, automation with ADSM
servers, and user data:
• Performance
The performance of the Application Client to ADSM is significantly less than what
can be achieved when saving directly to tape media. AS/400 save/restore
operations to tape are managed by hardware-controlled direct memory access
operations, which have been optimized for maximum performance. Application
Client save/restore operations use a software process that intercepts the normal
AS/400 save/restore data stream so that the data can be passed to the ADSM APIs
for transmittal to or from the ADSM server.
• Automation
ADSM servers do
not
currently support central scheduling of operations to
Application Clients (those that use the ADSM Application Programming Interface),
as well as several other functions available with ADSM Backup/Archive clients.
AS/400 Application Client operations can be scheduled only on the client using
AS/400 job schedulers. There is no automated logging of these scheduled events at
the ADSM server.
• User Data
Recovery of an AS/400 requires “system” objects (SAVSYS, IBM Libraries,
configuration data, security data, and so on) to be saved to an Alternate IPL device.
Therefore, only “user” data can be saved to ADSM servers. Also, BRMS recovery
information needs to be saved to tape so it is available to guide the recovery,
including connection to the ADSM server. By the time these “system” and “recovery”
objects are saved to tape, many customers may find there seems to be little
advantage to excluding the “user” objects when considering the complexity the
ADSM operations add to the overall AS/400 backup and recovery process.
• There are a several enhancements in V3R1 related to the control or management of
clients. Some of those enhancements are:
– The ability to support centralized logging of operations information allows client and
server events to be made available from a central point.
To Next Page
Loading...
Need help?
General