Ultimate Backup Tool V2.0 Download
Ronaldo Maffei
The heart of the tool is a PowerShell script I created named invoke-XenBackup. The script does require the XenServer PowerShell module installed. The GUI Tool will do this automatically. To do this manually download the PowerShell module here under the development section. And extract it to your PowerShell Module folder.
Hello ,,,I am really new at this, do not even know how to write a script on any language, but I am really thankful I found this website. I have tried the backup tool on my server, I see the zip logs on the folder I want to send them to but I do not know where that actual snapshot went to . I do not see it under snapshots at the VM selected. Please excuse my ignorance. What am I not seeing or what am I doing wrong.
Cool that you found the tool! The tool will copy the snapshot to the export path you selected after that it will delete the snapshot. You can send the logs to Chris....@dtncomputers.nl. That way I can help some more.
Hi Davidson, thank you for your patience, Version 2 is out today and should solve your problems. I also added the ability to backup to network drives directly! But the user running the task must have writing writes to the share. I hope this works for you!
Is there a possibility to select the disk I want to backup? because I have vms with a lot of data but on disks separate from the operating system, if I select every VM this will generate large files and longer backup time.
it is also of great help the software thanks!
When am trying to export to network drive its failing, there is enough space in network drive also am taking back of other applications to this network drive those are fine, but its failing from the tool. Below are from logs please help.
I used your tool last week to export my VMs so I could recreate my vms after the reinstall of my server.
I noticed when I imported the vm it was not available, but a template of the imported vm existed. Later I also saw the comment of Tonny Andersson from 14 April 2018 at 20:53:
When importing a backed up VM it is restored as a template, what in most cases is not wanted. This can be avoided by setting the following parameters, at line 133, before exporting the snapshot .
Are there any settings I can re-import? Everything is still sitting in OneDrive. And in *%APPDATA%\Local* I see I have a backup 20190116063617.sqlite which I assume is from this new isntall. I also see a 85,600KB ICBYVMIOZA.sqlite file which I guess is relevant.
Downgrading / reverting to a lower version talks about sqlite backups made before database version upgrade (which you get with 2.0.4.5), how to downgrade by identifying and restoring the backup databases (which also raises consistency issues with the destination, if backups have been run, unknown to the restored database).
Basically, the 85 MB file is probably the job database, and if backup 20190116063617.sqlite is a few hundred KB, it might be your former Duplicati-server.sqlite which you could try using as that (after renaming current), if you decide to try to downgrade, start Duplicati Server or Tray Icon, and note (or maybe even export) your job.
What happens if this building is flooded? If the three computers end up underwater? (Something VERY likely in this property) How would I go around retrieving data if all I have in my hands are the backup files on the OneDrive server and my password?
Recovering this specific backup
I think in this case it sounds like the config may have been lost a while back. There are just not enough different files on the server to have run multiple times like it should have. Especially when I compare it to the other successfully working backups.
The two above steps - either just getting a FULL recovery from backup data without config files. OR the ability to migrate a config between backup locations. That is a big plus which I have briefly misunderstood.
i.e. if I am pulling 35GB of data out of a backup store of 60GB then I assume the overheads of doing a restore bit by bit over the network from the cloud is slower than just pulling it all back to local and restoring locally.
Winamp Backup Tool v3.x, superseeded the old v1.x and 2.x versions and makes nearly anything better:
- more professional looking interface, less bloated than v1.x/2.x
- most of the souce code was rewritten
- vastly improved error handling (especially when using removable drives like USB sticks for backups etc)
- complete new, HTML5 log file system
- a new 'backup file info page', which shows the content of your used backup file in restoration mode
- a new 'manage backup and log files page', which shows the amount of backup/log files allows you to delete backup and log files.
- a new finish page, which integrates much better with the design of the rest of the tool
- vastly improved detection of running Winamp instances
- individual previous modes for backup and restoration mode
- 7-zip compression support for backup files
- vastly improved handling of multiple Winamp installs
- ability to select a custom Winamp install path for backup and restoration mode
Winamp Info Tool v5.0.2 was released.
This is a minor update which fixes a nasty bug, which prevents the tool to create a compressed report, it also adds icons to "Preferences and "About" buttons
and make the Index on top of HTML reports more flexible.
Take a look at the Winamp Info Tool Changelog to see all changes.
Winamp Info Tool v4.5.3 and Winamp Backup Tool v1.1 were released.
These are minor updates. Both tools now share the same update file and provide updated language files.
Take a look at the Winamp Info Tool Changelog and the Winamp Backup Tool Changelog to see all changes.
The Backup Tool does not archive the SSL / TLS Binding Certificate used for the IIS World Wide Web Publishing Service (W3SVC). To archive the SSL Certificate, see the Microsoft support document Export a Server Certificate (IIS 7) for instructions about how to manually perform the backup.
Before performing an operation, it's a best practice to decrypt the web.config files manually. If using 2.4.9 or later, you can let the tool automatically decrypt the web.config files, but manual decryption through the SecureAuth administrative interface is faster.
During this phase, the Backup Tool checks various aspects of the SecureAuth environment to help ensure a successful backup is made. If the tool encounters an error, a message with instructions appears onscreen.
Restore and Migrate are almost the same operation, so you can follow the same steps for each. The difference is that Restore restores everything from backup, whereas Migrate restores from backup without restoring SecureAuth0 and the standard Themes.
Read these instructions carefully and follow them after exiting the backup tool. Note that some screens will display; these are based on backup type and environment. Therefore, not all of the screens below will appear.
The Reset File Permissions and Shares Tool is a utility shipped with all SecureAuth Identity Platform Appliances. Its purpose is to validate correct settings for privileges on all files and folder in the D:\SecureAuth directory. It also validates correct file shares configured for the SecureAuth Filesync Service. For help using this tool, see the SecureAuth support document Using the Reset File Permissions and Shares Tool.
During the Restore process, your Windows Firewall settings are reinstated from backup. To ensure contact with the SecureAuth Identity Platform Appliance is not lost when the settings are reinstated, all Firewall profiles were turned off. If your SecureAuth Identity Platform Appliance normally uses the Windows Firewall with Advanced Security, review the restored configuration and re-enable your firewall at the earliest possible opportunity. See the Microsoft support document Windows Firewall with Advanced Security Properties Page.
[BUG] During unattended operations, the tool would stop at the description screen and prevent a fully automated process. The prompt will no longer appear during unattended operations and default verbiage will show in the description.
[FEATURE] Starting with the 2.2.0 version of the SABackup Tool, .NET 4.5.0 or greater is required. The tool will now check for the presence of .NET 4.5 and, if not present, notify the user and exit the script.
[BUG] In previous versions of the SABackup Tool, if the appliance that was backed up had the IIS URL Rewrite module installed, and that backup was later restored to an appliance on which the rewrite module was not installed, errors would occur. This could be the realm(s) on which a .NET error appeared; in some cases the IIS worker processes would fail to start, thus rendering IIS inoperable. The SABackup tool will now record whether or not the URL Rewrite module is installed and expected. Should the appliance on which the restore operation was performed not have the module installed, SABackup will install it to prevent run time issues.
[BUG] The SABackup Tool has a minimum OS requirement of Windows Server 2008. If the tool is run on legacy versions of SecureAuth Identity Platform 5.x with Windows Server 2003, various errors occur. The tool will now check on run to ensure it is not running on a 2003 Server appliance.
[BUG] In previous versions, a full backup would restore the IIS Config settings if the OS versions matched. In some scenarios this was causing SecureAuth0 to become inoperable. The script will now backup but not restore the IIS configs and create all realms through the built-in IIS tools.
[BUG] The SecureAuth Backup Tool needs to be installed at D:\SecureAuth\MFCApp_BIN; however, some users were installing it in another location. When run from a non-standard location, the behavior of the tool was erratic. The tool will now validate its runtime location at startup. If the tool is not installed in the correct location, it will display an error and exit.
760c119bf3