• Mitchell Berman
    0
    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.

    [img][/img]
    Attachments
    VMware backup current version in CBB_Archive (2K)
    VMware backup current version hexadecimal folder name (2K)
bold
italic
underline
strike
code
quote
ulist
image
url
mention
reveal
youtube
tweet
Add a Comment