- Newest
- Most votes
- Most comments
Hi Joost,
Thank you for reaching out with your question about using Glacier after migrating to your DS923+. I'll be happy to guide you through this process and ensure you feel confident moving forward. 😊
Clarifying the Issue
The key challenge here is that after upgrading from the DS413 to the DS923+, the Glacier backup tasks (configured on the DS413) were not migrated. You’re wondering how to recreate the tasks on the DS923+ and whether the system will link to the existing Glacier vaults or create new ones based on server name changes. Additionally, you’re looking to confirm whether it’s safe to remove the DS413-related Glacier vaults.
This scenario is common when transitioning between Synology devices, as Glacier tasks are not automatically carried over due to changes in device-specific configurations. AWS storage costs and the integrity of your archived data are important considerations here.
Key Terms
- S3 Glacier Vaults: Storage locations in Amazon S3 Glacier for archiving data.
- Synology Glacier App: The application used by Synology NAS devices to interact with Glacier.
- Access Credentials: The Access Key ID and Secret Key needed to authenticate with AWS.
- Server Name: The identifier for the NAS system, which might influence how Glacier identifies tasks or vaults.
- Vault Lock Policy: An optional Glacier feature that enforces data retention rules for vaults.
The Solution (Our Recipe)
Steps at a Glance:
- Gather AWS credentials from your DS413 configuration.
- Configure new Glacier tasks on the DS923+.
- Verify if the new tasks use existing Glacier vaults or create new ones.
- Review vault policies and update if necessary.
- Remove unused Glacier vaults safely after verification.
Step-by-Step Guide:
- Gather AWS credentials from your DS413 configuration.
- Log in to the DS413 and open the Glacier App.
- Navigate to Settings or Task Configuration.
- Note down the Access Key ID, Secret Key, and the specific Glacier region you were using. These details will ensure continuity when configuring tasks on the DS923+.
- Export a report of your existing tasks, if supported, for easy reference.
- Configure new Glacier tasks on the DS923+.
- Install the Glacier App on the DS923+ via Package Center.
- Open the app and select Add New Task.
- Enter the credentials from Step 1 and select the same Glacier region.
- Ensure the backup paths and task settings align with those on the DS413.
- Verify if the new tasks use existing Glacier vaults or create new ones.
- Run a small test backup from the DS923+.
- Log in to the AWS Management Console and navigate to Amazon S3 Glacier.
- Check if data from the test backup is added to the existing vaults or if new vaults are created. Use the Vault Details section to compare names, regions, and timestamps.
- Review vault policies and update if necessary.
- If using Glacier Vault Lock, confirm that the policies on your old vaults still meet your current needs. Vault Lock policies are immutable, so new vaults may require updated configurations.
- Navigate to AWS Management Console > Glacier > Vault Policies to review and adjust as needed.
- Remove unused Glacier vaults safely after verification.
- After confirming that all necessary data is in the new vaults, delete old DS413-related vaults.
- Use the AWS CLI or Management Console to ensure that no retrieval requests are pending before deletion.
- Consider downloading a final inventory report of the old vaults for your records.
Closing Thoughts
Transitioning Glacier tasks between NAS devices requires meticulous attention to details like credentials, vault regions, and task configurations. By carefully recreating tasks and verifying vault usage, you can ensure data integrity and avoid unnecessary costs. Don't forget to review your AWS billing dashboard periodically to manage Glacier storage and retrieval expenses effectively. Let me know if you encounter any challenges, Joost—I’m here to help! 😊
Best wishes on your migration journey, and happy archiving! 🚀
Cheers, Aaron 😊
answered 2 years ago
Relevant content
asked 2 years ago
asked 2 years ago
- AWS OFFICIALUpdated 6 years ago
