Comments

  • MSP360 Explorer for MacOS. Connection Failed. Check your credentials.
    Do you select a bucket? If so is the bucket all lower case? Just grabbing at straws. If that doesn't help, I'll ask a solution architect to jump on the thread.
  • MSP360 Explorer for MacOS. Connection Failed. Check your credentials.
    Have you verified your access and secret key in the AWS Web Console?
  • restore version (is it possible to choose from the available backup dates?)
    I think in that case, if you really did not know when the issue occurred, then you would be much better off simply restoring different versions of a candidate file to see which restored version did not have the issue. Then, using that file restore and the dates on the file, use the date range options to restore everything else. I do not think you'd ever go through a master list of files and versions cherry-picking individual files simply to see which ones were ok as there would be too many and it would take too long to individually select files.
  • How to restore from Google Drive when now not supported
    I'd recommend opening a new forum post as I'm not the one who's best for that question. On the new post, please show and type the exact error.
  • restore version (is it possible to choose from the available backup dates?)
    It's hard for me to think of a reason you would not restore the latest version within the date range supplied for all files, using that scenario. Maybe I'm just not thinking of one, so please elaborate on the business case if you have more information to share. Even if there were a few outliers, they could be easily restored using a secondary restore plan that selects only those file versions. The rest of the files, and presumably there would be a lot, would be restored with the main restore plan using the date ranges specified above.

    I worry what's happening is we're trying to invent a use case to fit the request - when it's easier to understand a business case and then decide on the best way to implement a feature to solve that problem. But again, I'm happy to keep this discussion going until we're hopefully in agreement one way or the other. While I agree that there could be a feature that simply lists all files and versions in a flat list that let customers cherry-pick files for restore, I'd need to understand better how that would be useful for you by understanding what business case would make that feature necessary.

    Look forward to your reply.

    David
  • How to restore from Google Drive when now not supported
    Sorry. The article needs updating with that missing (yet important :-) detail. Look for a line called"
    <ShowAllAccounts>false</ShowAllAccounts>

    and change the false to true.
  • restore version (is it possible to choose from the available backup dates?)
    If you have files that were corrupted for some reason and they were then backed up, then you can easily restore the older versions simply by using one of these options during restore:
    * Point-In-Time Restore - to restore files up to a specific date / time
    * Modification Period - Restores files modified within the specified date ranges
    * Backup Period - Restores files backed up within the specified date range
  • restore version (is it possible to choose from the available backup dates?)
    In that example, why wouldn't you simply restore the latest version of that deleted folder? Doing so would restore the folder in its entirety.
  • Error - Purge: File not present
    More than likely you have made an explicit selection for a file to be backed up in the backup wizard and that file is no longer being found on disk; hence the error. The theory being that since you made an explicit selection, you probably want to know if that file cannot be found (as opposed to simply selecting a folder with dynamically changing contents). The Purge operation may indicate the file is set to be purged, possibly because it's past the defined retention period, but the file cannot be found on disk any longer.

    You should be able to see the file in question in the History for that backup plan or by looking at the backup plan and checking it against the path in the message to see if a file has an explicit selection. If this does not help resolve the issue, please let us know.
  • restore version (is it possible to choose from the available backup dates?)
    Are you asking for the ability to see all files and versions of files that have mod dates and / or backup dates within a specified range in the app before restoring? If so, can you explain a little about how you'd utilize that feature within the product?
  • File based or image based
    Use file backup as it will allow you to tune the retention at the file level while backing up only the folders needed. Image backup is for backing up entire operating systems for the purpose of disaster recovery. While you can restore individual files from an image-based backup, you'll find the file-based option more flexible for your needs.
  • Best backup version
    Either MSP360 Backup for Windows Server or Ultimate. Depends on the amount of storage you are going to need. If you plan to use more than 1 TB or storage with your storage provider, then you need Ultimate. Otherwise, you can use Server Edition.
  • Scheduled Backup (block level) duplicate files when modified instead of just adding blocks
    As I mentioned previously, any application that is designed to change part of a file instead of an entire rewrite with compression (Office Docs, JPEGs, PDFs, etc.) would be a better candidate. Outlook PST files come to mind as do databases that you might back up when the database is offline. Also, the smaller the file, the more likely that any changes to it would change a high percentage of the overall file size and result in the file being backed up in full.

    There is no harm in leaving the block-level option enabled and scheduled the required recurring backup to make sure any block-level files backed up are backed up in full on some schedule. But, if you don't see your data in need of block-level, then disable it. Backups going forward (after the initial full backup of all files) will always only back up those files that are new / changed.
  • Outlook backup, not archive (ost not pst)
    PST is not only archive, although it can be used for archives. PST files are also used for live Outlook databases when using Outlook with POP3 servers - as opposed to enterprise Exchange or IMAP servers. PST files contain the email as opposed to OST files where they are simply cached from the server. You might also use a PST (as you mentioned) to archive server data to a local file to avoid mailbox size limits or to keep important emails past your company's delete policy.

    The best way to back up what's in your OST is to copy to a PST using the Export Wizard or a simple copy operation with an attached PST file.

    Since OST files are just cached copies of items that are saved on your mail server, they cannot really be used as backup. Move / Copy what's important to a PST file and back that up instead.
  • restore version (is it possible to choose from the available backup dates?)
    Yes, you can select "Manually" on the Restore Point tab in the Restore Wizard and then select the version of each file you want to restore (folders are not objects and do not have date / time stamps).
  • Scheduled Backup (block level) duplicate files when modified instead of just adding blocks
    Those Microsoft office file formats are also ZIP files and get recompressed each time you save. So you may not see block level backups effective with them.

    Just as an aside, you can rename any Office file with a . ZIP extension and open it up to see what's really in it.

    Block-level backups are not going to be as beneficial with files that are recompressed and rewritten each time they are saved. Instead, they are better able to take advantage of files that are changed only in part by the underlying application, like a Microsoft Outlook PST file.
  • Scheduled Backup (block level) duplicate files when modified instead of just adding blocks
    From what I can see, the software detected that all parts of the file were changed and proceeded with a full backup. ODS files are ZIP files composed of multiple XML files. Because of the compression used with that file format, it's possible small changes can result in most of the file changing each time it's saved.
  • Scheduled Backup (block level) duplicate files when modified instead of just adding blocks
    The software performed two full file backups according to image #3. There was no block-level backup completed for that file. Did you explicitly schedule block-level backups in the backup wizard? On the Scheduling tab in the wizard, there are two scheduling options: Incremental and Block-Level. Without getting too detailed, the block-level needs to be configured for those types of backups. The Incremental, less frequently, as it backs up complete files.Can you post a screenshot of that page in the wizard?

    If the Schedule tab looks different, you may be running an older version of the software.

David Gugick

Start FollowingSend a Message