What is the MOST operationally efficient way for a SysOps administrator to meet these requirements?
Create an AWS Lambda function that runs on an hourly basis and checks how many tapes have available space. If the available tapes are below a certain threshold, provision more.
Install the Amazon CloudWatch agent on the on-premises system. Push the log files to a CloudWatch log group. Create an AWS Lambda function that creates more tapes when the “Not Enough Space” error appears. Create a metric filter and a metric alarm that launches the Lambda function.
Create an additional Tape Gateway with its own set of tapes. Configure Amazon Simple Notification Service (Amazon SNS) to send a notification to the backup engineer if the tapes that are associated with the primary Tape Gateway do not have available space.
Configure tape auto-create on the Tape Gateway. In the auto-create settings, configure a minimum number of tapes, an appropriate barcode prefix, and a tape pool.
Explanations:
Creating an AWS Lambda function that runs on an hourly basis to check tape availability is not the most efficient solution. This method adds unnecessary complexity and does not address the issue of managing available space on tapes dynamically as backups are running.
While the approach of using CloudWatch logs and Lambda functions could work, it involves too many steps and custom configurations. Additionally, creating more tapes only when the “Not Enough Space” error occurs doesn’t proactively manage space or prevent the error from happening in the first place.
Creating an additional Tape Gateway may provide more capacity, but it doesn’t solve the problem of ensuring enough space on the primary Tape Gateway, and the engineer will need to monitor notifications manually. This isn’t an operationally efficient approach.
Configuring tape auto-create ensures that new tapes are automatically provisioned when needed. This provides a seamless and operationally efficient way to ensure there is always enough tape capacity, minimizing the chances of backup failures due to insufficient space.
I organize that the answer is:
Configure tape auto-create on the Tape Gateway. In the auto-create settings, configure a minimum number of tapes, an appropriate barcode prefix, and a tape pool.