VMware backup-- "Current Version" vs Legacy
We started using the "Current Version" of VMware backup and found that the backups for the different VMs are not easily identified (we use AWS S3) using Cloudberry Explorer or the AWS bucket interface. The "legacy" version separated the backups in folders with the name of the VM; "current version" puts them under CBB_Archive using 20+ character hexadecimal names.
This makes the backups a lot more difficult to keep track of on the AWS side and forces the user to be completely dependent on the agent interface to check backups.
Wondering if others have found this as disadvantageous as we do. We are staying with the legacy backups for now.
PS-- would you consider creating a Category for Managed Backup - VMware. Seems too specific for the General category.
VMware backup current version in CBB_Archive
VMware backup current version hexadecimal folder name
Sign in or register to add a comment.
Add a Comment
Welcome to MSP360 Forum!
MSP360 Managed Products
Managed Backup - General
Managed Backup Windows
Managed Backup Mac
Managed Backup Linux
Managed Backup SQL Server
Managed Backup Exchange
Managed Backup Microsoft 365
Managed Backup G Workspace
Backup for Linux
Backup SQL Server
Connect Free/Pro (Remote Desktop)
*Current Version* - CloudBerry Backup for Windows 6.0 Release Notes
FAQ - Managed Backup - Customization
FAQ - Managed Backup - Licensing
Centralized Version of CloudBerry Managed Backup
Terms of Service
Useful Hints and Tips
Created with PlushForums
© 2023 MSP360 Forum