Comments

  • ESXi Server error
    Did you check the event log on the virtual machine to see more about the error? I would check any event log entries for details and then have a look at this KB article for a possible solution: https://kb.msp360.com/standalone-backup/esxi-&-hyper-v/vm-quiescing-error
  • Difference between "schedule" and "full schedule"
    if you delete versions older than a time period, all the versions are removed when they age out, with the exception of the last version if you check the keep last version option. The number of versions you keep for each file is up to you and as long as they haven't aged out you'll have that many versions, assuming there have been that many changes and that many backups. If you decide you want to keep three versions, after the fourth version is backed up, the first version is removed. Also keep in mind that if you're doing block level backups you need to be aware that versions are going to be tied to the full backup of the file . So if you change your file every day and back it up every day and are running full backups once a month, you'll have 30 versions of that file that must be kept at a minimum before they can be removed because of the need to keep that full in order to restore the block-level file backups.
  • Generating a local backup of an AWS volume or snapshot
    The edition of the backup you need is where you're going to be running it from, so Linux in this case, since presumably you can install the agent on the Linux EC2 instance and run the backups directly to S3 storage. It doesn't matter where you're copying the backups or what tool you're using to facilitate that data migration as there is no backup product involved in that process. You may want to scour the internet for an Amazon S3 file sync utility That can synchronize local disk with your S3 storage to avoid copying objects locally more than once.

    Also keep in mind that you might be fine just keeping your data in S3. If you don't really need it locally you can save yourself the hassle of that process and the costs involved. Well we generally advocate for 321 backups, with a local backup and one offside in the cloud, that's generally for on-prem desktops and servers as opposed to servers that are already in the cloud. It certainly is more protection having a local copy, but there are costs involved in that process.

    Let me also add, and I apologize for not mentioning this earlier, that you don't have to back up to S3. You could create an account with a company that offers lower cost storage like Wasabi or backblaze B2 and back up there for 5 to $6 per terabyte per month. The backups will likely run more slowly because the data needs to move out of the AWS environment and region into a different cloud storage vendor, but if the costs work better for you it may be a good option. Plus with some services like Wasabi there are no data egress fees, so should you decide to move the data locally from Wasabi You could do that at no charge.
  • Generating a local backup of an AWS volume or snapshot
    if you only need a single license then that is what you need. You'll have to review the different editions to see which one satisfies your backup requirements. We do not have a cloud. The product backs up to your own storage. So you'd be backing up to an S3 bucket that you'll create for the target of any backups. And there will be storage charges according to how much data you're keeping. You can check the AWS calculator to understand storage fees as well as any data egress fees should you decide to copy the data out to your local environment. And you can always use less expensive S3 storage classes like S3 infrequent access or one zone infrequent access if that works for you. However, I would stay away from the S3 glacier storage classes as getting data out can be quite expensive and time consuming.
  • Generating a local backup of an AWS volume or snapshot
    Just to clarify, you are running EC2 instances and want to back up the data on those volumes? If so, you have a few choices:

    • You can use our Windows or Linux backup product (either our subscription Managed Backup or the stand-alone, perpetually licensed CloudBerry backup products) and install the agent on the EC2 instance and create file/folder backups as needed - preferably, they'd go to Amazon S3 storage since there's likely no easy way to hit your local network from EC2. You can copy those backups locally if needed, but there are data egress fees that will add cost to that process. You can also leverage lower cost S3 tiers like S3 Infrequent Access and S3 One Zone-IA to lower storage costs. There are retention requirements on S3 IA, so read about them before using.
    • You can use the same products to create image based backups of the EC2 volumes for Windows
    • You could use our Managed Backup product to help create snapshots of your EC2 instances - but those are stored by AWS in S3 and I am unaware of a way to get them out

    I think the first option is likely the easiest. You'll just have to decide if copying locally is needed. You can copy files from S3 locally using our S3 Explorer product, but you'll likely need the paid version for best performance with data sets that size.
  • Difference between "schedule" and "full schedule"
    If you're not using block-level backups to back up changes within files rather than the entire file every time it is changed, then there's only one backup type to schedule since the product backs up all changed files in their entirety every backup. If you're using block-level, then you want the product to back up changes within files (helpful for large files that change little day-to-day). In that case, you need to schedule a recurring full (e.g., once a week or once a month) so those files are backed up in their entirety. That's needed to manage retention. If you can imagine a large file that is backed up using block-level backups forever - we would be unable to delete old versions since every backup contains only part of the entire file.
  • Files NOT in source being backed up
    The team would like to see the logs for this particular machine. Can you submit them from the feedback option in the user interface?
  • Feature Request: SAML Authentication to Management Console
    no movement yet on this request. I'll check with the team again.
  • Files NOT in source being backed up
    Can you verify your version while I check with Support?
  • Beware of ExFAT formatting on WD Black USB Gaming Drives
    Thanks Steve. At that size the file system uses 2 MB clusters. That could partly be the reason for the slower performance. What's more unusual is that the external hard drive was formatted with that file system, which is more traditionally used for removable media like SD cards and removable USB sticks.
  • BitLocker Best Practice Question
    A few points.

    • You should not use the Keep BitLocker option on system volumes if you're backing them up using image backup. VSS cannot be used with BitLocker and that can lead to system volume corruption.
    • If you back up a non-system volume using the Keep BitLocker option, then you end up backing up the entire volume - including unused space. That can greatly extend backup time and increase storage requirements (imagine a 4 TB volume with 200 GB of used space and 3.8 TB of unused space). That also means you cannot exclude folders for backup on the volume using that option as everything needs to be backed up
    • As you've noted, you cannot perform file-level restores from volumes using the Keep BitLocker option

    You can (and should) use our AES-256 encryption during backup to protect the backups.

    Unless you have a specific need to keep the BitLocker encryption, I would not keep it for backup.
  • Source partition was not found warning message
    possibly during the server upgrade the ID on the volume changed. I would go through the backup wizard again and make sure the proper partitions are selected and then run the plan according to schedule to see if the message clears. It's possible one of your partitions is not getting backed up
  • Backup Service stopping
    No. Maintenance is not required and would never cause backups to stop running. As far as security software I'm asking what are you running on that computer? Windows Defender, Norton Antivirus, something else?
  • Backup Service stopping
    What security software are you running? I'm wondering if it's the cause of the issue. Can you also verify which version you're running? Also, please verify which account you're running the service under.
  • Protecting backup to B2
    There’s an immutability feature coming (likely in the 7.2 version) that will lock the data for the duration specified in the GFS retention settings. So, you’ll need to use the new backup format in order to leverage immutability.

    If you were using our Managed Backup, there are ways to disable the agent and lock it down with a master password. One thing you probably can do is run a backup to B2, object lock the data, change buckets and start backing up to an entirely different bucket to ensure the older backup is safe. You could also back up to an external HD and take it off site.
  • Remote Desktop doesn't work!
    What security software are you running?
  • Windows 10 Pro Desktop marked as a server.
    Please open a case so Support can review and provide the details to the engineering team for a fix. Thanks.
  • Remote Desktop doesn't work!
    Can you verify you're using the same version, and the latest version of the product, on all computers involved?

David Gugick

Start FollowingSend a Message