Forum tip: Always check when replies were posted. Technology evolves quickly, so some answers may not be up-to-date anymore.

  • Cloudberry PC and MAC Have Different AWS Directory Structures
    I'm checking with the team, but I am pretty sure backups are not compatible between platforms as they exist in their native backup formats. But I'm waiting on confirmation from the Support team. In addition, I also asked if PC backup files can be restored to a Mac as another possibility.

    But my guess regarding your question of leveraging a PC backup on a Mac as the basis for avoiding having to back them up again, is likely to result in the need to do just that: back them up again. Do not re-copy the backup files in the cloud from the Mac bucket to the PC bucket until you hear back from me as I'm not sure yet that would work.
  • Mac Unattended Access
    Are you asking for the ability to connect to a Mac system to remotely control it? Or are you referring to connecting to a PC from a Mac with Unattended Access?
  • Accessing AWS 3 Folders in a Container from Cloudberry MAC Backup
    You only select the Bucket. All backups are organized within the bucket based on computer prefix. Folders in the cloud are not like folders on your hard drive. Cloud objects are stored in a flat file structure - the folders are themselves just objects and AWS prefixes folder object name to the file names of those files that are stored within them to make "browsing" more like a traditional hierarchical file system.

    So, all you need to do is select the Bucket you want to use or create a new one, as needed. You can read more about S3 "folders" here: https://docs.aws.amazon.com/AmazonS3/latest/user-guide/using-folders.html
  • Unable to connect for remote access
    It's not clear without a more detailed analysis of what's going on with the remote PC. Some users had indicated in the past that having FastStart enabled caused the issues for them and disabling it fixed the issue. You can read more about how to disable FastStart here: https://www.windowscentral.com/how-disable-windows-10-fast-startup

    Other had corrected the issue by restarting the Remote Assistant Service on the remote system. But usually this was only a temporary fix.

    There was also a fix for a similar issue in 2.3.1 (and another in the 2.3 release), so make sure you are using the latest version.

    You may want to open a support case from the menu - Diagnostic option on the remote system where you are unable to connect.
  • ID and PIN accessibility
    It's currently planned for the next 2.4 release.
  • What is the Function of the "~segments" Directory Branch in the Cloud File Store?
    If you want to clean up old backups from a machine that you are still backing up, you should only do so from the Storage tab in the UI. If you delete directly from cloud storage, the local repository will be out of sync. I’m not sure, offhand, what that folder is for. I’ll have to ask Support. Are you planning to keep backing up this Linux machine using that backup plan?
  • Unable to Complete a VM Image Backup
    This is going to need a support case. Use the Feedback option in the UI and Support should be able to provide additional assistance with OpenStack.
  • Unable to Complete a VM Image Backup
    Are you saying there is at least one IMG file that is the cause? Can you post the exact error you are seeing (screenshot)? Is it possible that file is in use by another process?
  • Fast NTFS Scan Improvements?
    Agreed. It's currently scheduled for the 4.8 release of the console (we're on v4.6 right now). I'll add your comments to the open item and maybe we can get it sooner.
  • Maximum upload speed to AWS S3 over AWS Direct Connect?
    I guess these are the variables (or some of them, at least):
    1. Speed with which data can be read from the NFS volume by the Windows Server
    2. Network speed / adapter settings for the Windows Server VM to AWS Direct Connect
    3. Maximum ingest rates for Amazon S3
    4. MSP360 Backup processing

    Regarding these items:
    1. Test your read speed from the NFS volume by the Windows Server. You could try copying a file from a Command Prompt on the Server for a file on the NFS volume to the NUL: device - to eliminate write speeds on the VM. Just select a file that has not been read recently and in cache. Something like this should suffice:
    ECHO %time% & COPY /B "AFileOnNFSVolume.BAK" NUL: & ECHO %time%
    
    2. Check your VM to see how the Network Interfaces are configured. Are they capable of speeds greater than 1 Gbps?
    3. I've done some digging around the internets in the past and have never been able to find definitive docs from Amazon on maximum ingest rates for S3. I would say that 1 Gbps is extremely fast hitting a single bucket, but i think this is probably a good question for you to ask your technical rep at Amazon. It's possible that even though you have a 5 Gbps link to AWS, it's not possible to get that rated speed when writing to S3
    4. On the MSP360 side there are a few things that can affect throughput:
    • If you are using RMAN to compress the backup (recommended) then re-compressing with MSP360 is probably a waste of CPU cycles. Consider disabling compression, if enabled
    • If you are encrypting, that will use CPU cycles as well - but I'm not recommending you disable if the backup is not already encrypted using Oracle Secure Backup.
    • With 12 Virtual CPUs, I'd consider using 10 or 11 Threads at the most to avoid unnecessary thread switching on the CPUs. Set Chunk Size accordingly - maybe 100 MB - but higher could be a little better as it does reduce some latency
    • Make sure Block-Level backups are disabled (Advanced Scheduling Block-Level). Just have incremental selected. The RMAN backup files are not going to be updated, so no block-level analysis is needed during backup for those files.
    • Make sure Logging is set at LOW or DISABLED. We can use logs to help diagnose issues and they'll need to be at LOW (at the lowest), but for maximum speed, you could try disabling the logging (Options - Logging)

    That's all I can think of right now. Let us know what you find.
  • Fast NTFS Scan Improvements?
    From what I can see in the internal docs, there were at least 2 enhancements:
    1. Improved memory utilization when backing up 100,000's of files
    2. Speed improvements in looking for file changes on large volumes (an internal test on a test 10 TB volume showed scan speeds improving from an hour down to a few minutes) - YMMV
  • Cannot Run Any Administrator Process
    You're triggering UAC from an interactive session when you use Run as Administrator. UAC currently requires local confirmation and cannot be triggered from the remote system. We are working on a possible new feature to allow UAC in this scenario. In the interim, you could use Unattended Access to connect to the remote system and you'll have the access you need.
  • Remote screen image too large
    Scaled View icon in the toolbar. Looks like 4 arrows stretching out from the center. That should do what you need.
  • Managing backups of duplicate file names within sub-folders
    Block-level only works within files. It doesn't matter if your files have the same names as those used in other folders. They are treated as new files and need to be backed up in full. Since they are unlikely to ever change, they'll never be backed up again. If you start deleting older backups, they will eventually be removed from storage, depending on your retention settings. What's your desired retention as it relates to the Autodesk backup files? If it differs from other files you're backing up, you could create a separate backup plan for Autodesk.
  • Remote screen image too large
    Have you tried sizing the display using the option in the toolbar once connected?
  • Managing backups of duplicate file names within sub-folders
    If you have the parent folder selected for backup, then all sub-folders will be backed up dynamically each time the backup runs.
  • Frustration with USB Boot device
    Yes, a support case may be needed.
  • Not being asked for PIN or Password
    I'm thinking I misread your post. You are having to login to the remote machine using Windows Authentication, correct? If so, that's designed behavior in that Windows authenticates the unattended access.