Backup & Recovery for eMAM systems deployed on AWS

Health Check-up, Backup/Recovery & Patches/Upgrades for eMAM systems deployed on AWS Cloud

Health Check-up

In eMAM, you can monitor the statutes at various levels to ensure your system is functioning properly.

Live Dashboard

The Dashboard widget in the eMAM Director interface, gives you real time status of all the jobs submitted for processing. Based on the errors displayed, you can take corrective measures and resubmit the jobs for processing. Once the file vanishes from the Dashboard that process is complete. The Dashboard widget indicates the status of completed, pending or error items for different workflows:

1. Ingest: displays status of jobs submitted for ingest to the eMAM system.

2. Delivery: displays status of jobs submitted for delivery.

        

3. Archive: displays status of jobs submitted for archive.

    

4. Cloud: displays status of jobs relating to cloud upload or purge - Cloud Purge Error, Cloud Upload Error, Cloud Purge, Cloud Upload, Cloud Purging, Cloud Uploading.

    

5. Purge: displays status of jobs submitted for purge.

   


6. Workflow: displays real time status of all the workflows that are executed in the eMAM system.
   

Server Management

The Server Management tab in the Super Admin console displays all servers and server components along with its expiry dates. The Super Admins can check the license status of each server and its components and ensure licenses are renewed before it expires.

CloudWatch logs 

CloudWatch Logs automatically receives log events from several AWS services. The eMAM system CloudFormation template creates a CloudWatch log group into which the log files are copied from the EC2 instance. The CloudWatch log group contains log streams, which include the ID of the instance with the log file name. This allows you to identify to which EC2 instance the log file pertains.

1. Open the CloudWatch console at https://console.aws.amazon.com/cloudwatch/
    

2. In the navigation pane, choose Log groups.
    
3. For Log Groups, choose the log group to view the streams.
4. In the list of log groups, choose the name of the log group that you want to view.
5. In the list of log streams, choose the name of the log stream that you want to view.

Elemental MediaConvert monitoring

You can track the status, phase, and percent completion of your jobs. On the console, you can see your job status and the overall percent completion of your jobs. 


For more granular information, such as percent completion of the probing, transcoding, and uploading phase use Amazon CloudWatch Events. Access the Jobs page by opening the AWS Elemental MediaConvert console and choosing Jobs in the navigation pane.
For information about status and phase, see How AWS Elemental MediaConvert jobs progress.
MediaConvert returns error codes when transcoding jobs run into problems. You can use CloudWatch Events to track the error codes that the service returns. For more details on the error codes, see AWS Elemental MediaConvert error codes.


Backup & Restore

Backup and restore is one of the approaches for mitigating against data loss or corruption. Amazon S3 is an ideal destination for backup data that might be needed quickly to perform a restore.  eMAM system can be rebuilt from Database Backup so please ensure DB is backed up regularly.  Follow the recommendations from Microsoft for the Back Up and Restore of SQL Server Databases.

To recover your data, you must first have your data periodically backed up and pushed to secure storage locations from your eMAM system to AWS. eMAM recommends taking EC2 & DB snapshots separately. A snapshot takes a copy of the EBS volume and places it in Amazon S3, where it is stored redundantly in multiple Availability Zones. 

Click here for more details on Amazon EC2 backup and recovery with snapshots and AMIs, 

Click here for more details on Restoring from an Amazon EBS snapshot or an AMI.

Key steps for backup and restore: 

    1. Data is backed up into AWS using automated scripts.

    2. Ensure that you have an appropriate retention policy for this data. 

    3. Ensure that appropriate security measures are in place for this data, including encryption and access policies. 

    4. Regularly test the recovery of this data and the restoration of your system. 

Disaster recovery steps for eMAM systems on AWS cloud are:

1.      Build the EC2 instance from the EC2 & DB snapshot/AMI.

2.      Restore the DB from the backup.

Patches & Upgrades

eMAM uses CI/CD deployment pipeline for eMAM Lambda functions patches and upgrades.


eMAM patches are released in Zip files and available in the eMAM FTP repository. Customers who need upgrade can reach out to eMAM Support or to our Systems Integrator channel for a major system upgraded.

Click Here to see all the eMAM versions released till date.


eMAM Support:
Reach out to eMAM support, if you need to restore your system.

Portal/Chat: https://www.emamcloud.com/support/


    • Related Articles

    • eMAM Cloud Platform - Production (eCP-Production)

      eCP-Production Deployment About this Guide This guide is intended for IT infrastructure architects, administrators, and IT professionals who are planning to deploy eMAM system (PAAS) on AWS Cloud. Overview eMAM Cloud Platform - Production ...

    • eMAM Workgroup 5.3

      eMAM Workgroup Server Specs Doc

    • eMAM Publish Server Spec Guide

      Refer the attachment for eMAM Publish Server Spec Guide

    • eMAM Vault Server Spec Guide

      Refer the attachment for eMAM Vault Server Spec Guide

    • Bug Fixes eMAM 5.4

      Bug Fixes in eMAM 5.4 BUG ID DESCRIPTION 5.3.1_18NOV2021 11889 Storage DNA API change to handle "404 not found" in the response. 11899 Schedule metadata is not getting updated for PATCH api/v1/assets/{AssetId}/AssetMetadata 11708 PFR is not working ...