Administering Avaya Aura System Manager 11-7-2023
Administering Avaya Aura System Manager 11-7-2023
Administering Avaya Aura System Manager 11-7-2023
Manager
November 7, 2023
Administering Avaya Aura® System Manager
Notices
© 2023 Avaya LLC. All Rights Reserved.
You may, at your own risk, assemble a MyDocs collection solely for your own internal business purposes,
which constitutes a modification to the original published version of the publications. Avaya shall not be
responsible for any modifications, additions, or deletions to the original published version of publications. You
agree to defend, indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all
claims, lawsuits, demands and judgments arising out of, or in connection with, your modifications, additions or
deletions to the publications.
A single topic or a collection of topics may come from multiple Avaya publications. All of the content in your
collection is subject to the legal notices and disclaimers in the publications from which you assembled the
collection. For information on licenses and license types, trademarks, and regulatory statements, see the
original publications from which you copied the topics in your collection.
Except where expressly stated by Avaya otherwise, no use should be made of materials provided by Avaya on
this site. All content on this site and the publications provided by Avaya including the selection, arrangement
and design of the content is owned by Avaya and/or its licensors and is protected by copyright and other
intellectual property laws including the sui generis rights relating to the protection of databases. Avaya owns all
right, title and interest to any modifications, additions or deletions to the content in the Avaya publications.
Note:
System Manager does not support deployments or upgrades on System Platform. Therefore, for System
Manager upgrades by using data migration utility, create a backup of System Manager configuration files and
the System Manager database only from the System Manager web console.
During the backup operation, System Manager validates the backup file that you upload, and displays an error
if the file type does not match.
You can perform either a backup or a restore operation at a specified time. The restore operation fails if a
backup operation is in progress. When a restore operation is in progress, the system skips all backup jobs that
you scheduled.
You can only restore the data on System Manager that has the same software version and IP address (both
OOBM and public), FQDN, and Hardening level as that of System Manager on which you created the backup.
System Manager verifies the signature of the backup files and warns if you restore a corrupted or tampered
backup file on System Manager.
To perform the backup and restore operations, you must map the user to the role with the following
permissions:
OnDemand add
For information about creating a custom role, see “Adding a custom role”.
Note:
While restoring backup on System Manager with different Out of Band Management network details, the
restore operation fails at validation phase.
• System Manager backup operation supports a maximum of 4GB file size of the /emdata/svars/
directory. This is approximately 41% of /emdata occupancy, as displayed in the Disk Space Utilization
widget on the System Manager web console Home screen.
• If you have 250K users and 4GB of svars file size, the backup file size is 5GB.
To process the backup in the /swlibrary directory, you must have three times of backup file size space.
• The root partition must have at least 1GB of free space.
Solution
Procedure
1. Clean up space in /swlibrary.
Note:
Do not delete the wildfly_java_tmp directory.
2. Move the backup archives located at /swlibrary/backup/ to the remote machine.
3. Delete unused SDM artifacts, such as OVAs and patches that are not required.
To delete SDM artifacts from the System Manager web console, click Services > Solution Deployment
Manager > Software Library Management > Manage Files > Select and Delete files.
4. Delete any files, such as OVAs for patch binaries copied manually.