Welcome to the world of Principia - the successor to the Android hit physics game Apparatus, played by over 3 million players.Solve puzzles using the laws of. Download Trial Version Buy Download. OneSafe JPEG Repair is reliable u tility to repair damaged or corrupt image files having JPEG or JPG file extension. The software repairs image files saved on hard disk of computer, memory card, or any other storage media. This tool scans the storage media thoroughly and repairs even the.
OverviewStorageCraft ShadowXafe is an all-in-one system that allows you to protect and restore your vCenter/VMware or Hyper-V systems from a single interface. It has the following features and functionality:. Support for both Hyper-V and VMware environments. OneSystem - OneSystem is the central interface for ShadowXafe. See for additional information about ShadowXafe and OneSystem.
The Protection Environment - The Protection Environment includes the hosts, clusters, virtual and physical machines that you want to protect. Storage - The Storage is where your backups are located (Storage name, site, and path). You can select or define these storage types: NFS, iSCSI, SMB, or StorageCraft Cloud. Policies - Policies define the snapshot frequency, storage destination, Retention settings, and replication targets.About The ShadowXafe User GuideThis User Guide contains instructions for using ShadowXafe.
Note: It may take a few minutes to display the IP address for the new OneSystem VM.In Hyper-V. Download and run the MSI.
Accept the License and select your customized install options. Follow the directions for. After the deployment is complete, the director or service node VM starts running. The VM will now be accessible in the Hyper-V manager and the IP may be available via the networking tab.Note: It may take a few minutes to display the IP address for the new OneSystem VM. Note: You can add and manage multiple vCenter environments within a single ShadowXafe system. A vCenter environment consists of one or more physical hosts, which run the VMs. If a protection appliance backend service is running on the same host as the VM being backed up, the protection appliance will use an efficient method to capture the backup data (consult VMware's documentation on 'hot-add').
Backing up VMs without a protection appliance backend service on the same host is possible, but slower (consult VMware's 'NBD' transport documentation). Deploy additional Service Nodes to each host to ensure effective use of hot-add. Setting Up (Deploying) OneSystem. Mount or extract the StorageCraft Deployment Tool.iso file. Run the StorageCraft Deployment Tool. Supported Operating Systems and Requirements Note: ShadowXafe supports only 64-bit Agent operating systems. Starting ShadowXafe and First Time User RegistrationGetting the IP Address for OneSystemFind the IP address for OneSystem under the Summary tab in vCenter.The chapter describes this in more detail if you need additional help.Connecting to OneSystem and First Time Registration.
Open a browser on another machine that is on the same network as OneSystem. Enter the IP address (or host name) of OneSystem into your browser URL field and press the Enter key on your keyboard. This displays a message that says 'Your connection is not private'. Note: You can filter machines to Select one, Select many, or Select all. Click Assign Policy to apply the policy to the selected machine(s). Click Save to start the backup.Adding another PolicyClick Add Policy if you need more policies.
The appliance lets you create multiple policies that allow you to protect your data as needed.Starting the Backup ProcessBackups Start Immediately when you assign a policy. When you click Save, the backups for the selected machine start. See the in the Release Notes for additional information.RecoverySee the and chapters for additional details.05 - Monitor and Manage. Important: If you replicate to Cloud Services, the Service Level is automatically set to Cloud Premium. This applies to all ShadowXafe images replicated to StorageCraft Cloud Services. You should also always verify your Cloud Services Retention settings before replicating to the cloud because the Cloud Services Retention settings take precedence (override) the ShadowXafe replication settings. ShadowXafe policy retention settings apply in all cases, except when you replicate to StorageCraft Cloud Services.Configuration. Add protection environmentTo add a protection environment:.
Click the Add protection environment button. This displays the Add machine source window. Enter the machine name.
Enter an Alias if you want (optional). Enter the Host name. Select the port number (443 is default).
Enter the User name. Enter the Password.
Check the Secure box (if applicable). Click Save.Add StorageTo add storage:.
Click the Storage link at the top of the Configuration page. This displays the following screen. See the article.PermissionsThe permissions page displays the users. To add a user:. Click the Permissions link on the configuration page. Process Overview.Add StorageCraft Cloud StorageTypically you want to add your other storage (node types: NFS, iSCSI, SMB) before adding the StorageCraft Cloud node type.
Go to the ShadowXafe Configuration page and select the Storage tab. Click Add Storage. This opens the Add Storage page. Open the Node type dropdown and click StorageCraft Cloud.
Enter the Name for your cloud storage (user definable). Enter the Cloud Username. Enter the Cloud Password.
Enter the Image Password. Confirm the Image Password. Click Save.ImportantIf you replicate to Cloud Services, the Service Level is automatically set to Cloud Premium. This applies to all ShadowXafe images replicated to StorageCraft Cloud Services. You should also always verify your Cloud Services Retention settings before replicating to the cloud because the Cloud Services Retention settings take precedence (override) the ShadowXafe replication settings. ShadowXafe policy retention settings apply in all cases, except when you replicate to StorageCraft Cloud Services.Replication and Seeding Settings (New Policy)Replicating means that you are transferring your selected recovery points (for all machines covered by the policy) to StorageCraft Cloud Services through the internet. Seeding means that instead of replicating immediately to the cloud, it will populate a seed drive (if attached to the Service leader). Move your cursor over the seed-drive line to display the eject button.
Click the eject button. Package and ship the seed drive to StorageCraft in the provided shipping container. StorageCraft will add your recovery points directly to your Cloud Services account.If Populating the Seed Drive Doesn't FinishIf a seed drive transfer appears to be stalled, (i.e. The “Transferring” message continues to be displayed for an unreasonably long time), follow these steps to restart the seed drive population.
Go to the Machine Details page for the machine in question. Click Edit for the StorageCraft Cloud seed type. This page is only for upgrading from one minor revision to another minor revision within a single major version. If you need assistance upgrading from more than one or two revisions behind, for example from version 2.1.2 to 2.1.10, please contact support. In this example, using version number 2.1.10, the number 2 is the major version, and 1.10 are the minor revisions.Upgrade orderStorageCraft recommends upgrading system components in the following order so that everything is ready to communicate when OneSystem restarts. Service Nodes.
Service Leader. OneSystem. Agents (if deployed in your environment)Adding Service Leaders and other Nodes into the OneSystem CockpitAs a prerequisite to checking for updates you should add the Service leaders and other nodes to the cockpit so you can manage and update them all from within the Cockpit. This will save you from needing to SSH into each individual system to manage them.Required Port NumberThe Cockpit requires the ability to SSH into the machine from OneSystem/Director (Port 22).Step 1 - Choose the correct Upgrade channel.Important: Do this before checking for updates.Step 2 - In the Configuration tab click Service Nodes.Note: Capture or note the IP addresses for each of your ShadowXafe Service Nodes. The IP addresses will be needed in steps 5.1 and 5.2 below.Step 3 - Click Launch Cockpit.Step 4 – Check the “ Reuse my password for privileged tasks” box, then click Log in.The 'Reuse my password for privileged tasks' checkbox is located below the User name and Password entry fields.Step 5 - If machines were previously added to the cockpit you can manage them now, or select them for updates.Step 5.1 - If machines were not previously added to the cockpit, click + on the right side of the screen to add them now.Step 5.2 - Specify which service node, or service leader to add.
Use the IP address, FQDN, or the External Address and port then click Add.Note: You may need to enter the same unique passwords created during deployment. You may also need to accept certificate fingerprints.Step 6 - Use the dropdown list to select which service leader, director or node you want to upgrade.Step 7 - After selecting which director, service leader or node to update, click Software Updates.You'll see the progress indicator spinning during the search. This may take a while.Step 8 - when the list of updates is displayed click Install All Updates to run the updates.Note: ShadowXafe packages are identified with “xafe-“ in the name. Some updates may be for CentOS (i.e. Not part of ShadowXafe).Note: You can have multiple updates for multiple service nodes running at the same time.Step 9 - Reboot all Appliances in the same order as you updated them.
Restart the director last.Step 10 - Verify that all service nodes come online in the configuration.Use the versions listed in the Service Nodes tab to complete this step.06 - Recovery and VirtualBoot. ShadowXafe Recovery Recovery on Hyper-V and VMwareThe instructions and information on this page describe the recovery process for VMware. However, the recovery process is the same for both Hyper-V and VMware. VAIO (described later in the instructions) is specific to VMware and is not used by Hyper-V. Hyper-V has its own filters (equivalent to VAIO) which provide the same VirtualBoot operations.Note: For VMware, in order to install the StorageCraft VAIO filter driver for VirtualBoot, the host must be configured to be VMwareAccepted. If the host is not configured properly the VirtualBoot plugin cannot install.Process Overview. Click the Recovery tab in the navigation bar. Select the Source Machine.
Select the Recovery Point. Click Select the Target. Select the Target Type and fill in the fields. Click Start recovery.Target Types. Restore to new VM. Restore to VirtualBoot target.
Restore to Recovery AgentRestore to new VM. Click Select Target to display the Target Machine screen. ShadowXafe VirtualBoot is similar to the VirtualBoot process in SPX (unless you select the ShadowXafe Migrate data to vSphere option). Checking the migration box creates a permanent VM. Restore to Recovery AgentThe Recovery Agent ISO uses bootable media to start the target machine and get it into a state where ShadowXafe can restore to that machine. The ISO was designed for physical machines but can also be used on a virtual machine.On the Target MachinePrepare the Target Machine to Connect with OneSystem.
Boot the new target machine from the ISO. When the 'Start the StorageCraft Recovery Agent' menu appears, click Start the StorageCraft Recovery Agent.
When the dialog window prompts you to register the target machine, select the Host name and enter the IP address of the OneSystem VM into the registration field.The target machine boots and acquires an IP address. It then starts advertising its IP address to ShadowXafe indicating that the target machine is ready for a restore.In OneSystemAfter completing the steps on the target machine, follow these steps to start the recovery. Click the Recovery tab in the left-side navigation bar. Select the Source Machine. Select the Recovery Point. Select the Target. Additional Resources.Contacting StorageCraftCall StorageCraft at 801.545.4700.Frequently Asked Questions What is ShadowXafe?ShadowXafe is the hardware independent (software-only) version of the data protection appliance that protects your Virtual Machine environments and machines and lets you restore from a single interface.
It does not require OneBlox as the storage device. You can use the hardware specified in the Requirements section of this user guide.Why Upgrade from SPX to ShadowXafe?ShadowXafe is much easier to deploy and supports host-based backups. You can protect all types of operating systems, centralized management view, and it scales to larger installations. ShadowXafe includes everything you need for data and system protection such as taking backups, accessing backups and files, monitoring and managing multiple sites, and more.
In essence you are managing everything through 'one pane of glass'.ShadowXafe has a more efficient backup format that allows better deduplication (whether on OneBlox or other deduplicating storage systems). Instead of focusing on raw files, storage in ShadowXafe is a service. This allows much smarter and more efficient random access, and better integration with the underlying storage system whatever it may be. It allows more efficient data flow because the storage service can dynamically answer queries. For example, ShadowXafe 'consolidates on the fly' and streams the data offsite.The agent-based backup feature of ShadowXafe is much smaller (smaller footprint on disk, much reduced CPU usage, less RAM). ShadowXafe also has streamlined licensing to ensure your data continues to be backed up. It also has more efficient file/folder restore which means you don't need to install a kernel-level mount driver to access files/folders.Which Versions of Windows does the ShadowXafe Windows-Agent Support? Note: ShadowXafe supports only 64-bit Agent operating systems.
The Windows Agent MSI blocks installation on 32-bit operating systems. Server 2019.
Server 2016. Server 2012 R2. Server 2012. Server 2008 R2.
Windows 10 Desktop. Windows 7 (64-bit) DesktopDoes ShadowXafe do volume based or disk based backups?ShadowXafe always takes backups of the entire disk, for both host-based and agent-based backups, which makes recovery more reliable and convenient. However, just like our previous backup products, agent-based backups use our award winning volume snapshot driver.
This ensures that agent-based backups are the highest possible quality.Does the Host-based backup integrate with VSS?Host based backups do not integrate with VSS. Under certain conditions, if you have VMware Tools installed on the target machine, VMWare will attempt to quiesce through the VMware Tools. Otherwise, it's a crash consistent backup. StorageCraft automatically installs VMware Tools when deploying OneSystem, but you need to install VMware Tools yourself on the Target.What is the ShadowXafe Support Bundle?The Support Bundle is the collection of log files created by ShadowXafe to help you understand in detail what is happening in your environment. The bundle can also help you troubleshoot and resolve any issues you may encounter.
See.Where are the Log Files?There are two ways of finding the log files. Click the Support Bundle link in the user interface to download a zip of the log files. Use the Cockpit view to view the log files.The image below shows the Support Bundle link. Note: The log files for ShadowXafe are not the same format as the log files for ShadowProtect or SPX.See for additional information.Can I change the Policy after starting the backup process?If I've created my Protection Environment, selected my Storage, and applied my policy (backups are being taken), can I stop the process and change the policy (for example change my backup frequency from every 4 hours to once every hour) and then continue backups without any adverse effects?Yes, doing this will just give you more recovery points and take up more storage space.
You can also go the other direction and reduce the backup frequency which would give you fewer recovery points and take up less disc space. Alternately you could also create another policy for the specific values you want.What is the VAIO Filter and How is it used in ShadowXafe?The VAIO filter is the set of vSphere APIs for IO filtering.The VAIO filter is used for ShadowXafe VirtualBoot. It allows you to almost instantaneously start a VM from a backup recovery point. While the VM is still running (after VirtualBooting it), the filter allows the VM to access additional information as needed from the backup recovery point. The additional data is used by the VM as needed, and written to the VM disks. This process is known as backfilling.What happens if I reinstall the same version of the VAIO driver (filter)?If you install the same version of the VAIO filter that is already installed, the process first uninstalls the filter and then attempts to reinstall it.In some cases vCenter can remove VAIO from its database in such a way that the API falsely reports that the filter was removed or uninstalled when it really is still present on some of the ESXi hosts.
Similar results can also happen when directly trying to remove the VAIO filter.If this happens here are some things you can try:. Use command line tools to find and remove it. Enter + exit Maintenance Mode. Reboot vCenter or particular ESXi hosts. Shut down VMs, and so on.Generally vCenter only gives us a very generic error - for example, 'The operation is not allowed in the current state'.Additional Questions and Links to Answers.
Will ShadowXafe backup both VMs and physical computers? See, or. Where can I install/deploy ShadowXafe (which platforms)?
And. How does ShadowXafe protect my machines? See, and, etc. How do I use ShadowXafe to backup virtual and physical machines? See, etc.
How do I use ShadowXafe to restore a backup? See,.
How can I use ShadowXafe to restore a backup from a physical machine to a virtual machine or from a virtual machine to physical?. How do I use the recovery ISO on a physical machine?
See,. How do I Run Backend Services on each ShadowXafe datastore for better backup performance? See,. What is the difference between 'agent-based' and 'host-based' backups? Agent based installs an agent on each individual machine. Host-based uses interaction with the host to backup data on the VMs. What versions of Windows does the agent-based backup support?
See. Does the host-based backup integrate with VSS?
See. Does ShadowXafe restore from volume based, disk based, or file based backups? See. Why did changed-block tracking fail? See,. Can I use ShadowXafe on multiple vCenter environments?
See. How many times do I need to install ShadowXafe OneSystem? See. Do I 'Run Backup Services' in ShadowXafe at the datastore level, vCenter level, the cluster level, or the host level? The OVF is deployed per ESXi host.08 - Concepts and Terminology. This Concepts and Terminology article will help you understand and use StorageCraft ShadowXafe more effectively.Backup Services and Recovery AgentsThe StorageCraft data protection appliance uses services, and in some cases agents (on individual Windows machines). The appliance allows you to:.
Protect and restore cluster and host based systems. Protect individual machines (virtual machines or physical) as needed.Examples of Services and Agents as Used in ShadowXafeRecovery agent = Bootable ISOBackup agent = Windows Installer package (MSI)Service node = Virtual Appliance (OVF) and OneBlox, also sometimes referred to as backend nodes.OneSystem = Virtual Appliance (OVF). Note: The Windows backup agent does not use the Backup service.
This only applies to virtual machines. Restore Service – handles the process of restoring machines. Storage Service – manages and performs the tasks to store the backups. Scheduling Service – is responsible for controlling which jobs run and when (on what interval) they run. The scheduling service is responsible for telling the other services/workers what needs to be done and when.Backup Agent (Windows)This semi-autonomous agent runs directly on the Windows machine being protected. The agent has direct access to physical resources and interacts with the operating system, etc.Backend Agent (see Service Node)The service node (sometimes called the backend agent) handles copying data to the storage destination.CBT – Changed Block TrackingVMware tracks the changes made to storage blocks on the VMware datastore for host based backups.
Configuration OptionsConfiguration options include:. Environments. Storage. Service Nodes. Sites. Integrations. SMTP.
Users. Groups. OneXafe ClustersDashboardThe Dashboard is the part of the OneSystem user interface that shows a high-level view of the system status. It includes system health, SLA compliance for protected machines, and storage trends that help you know when you are likely to run out of space so you can add more if necessary.Data Storage Node. VMware's datastore refers to where VMware virtual machine 'disks' (or.vmdk files) are stored. The datastore refers to the location where ShadowXafe stores its backup images.
StorageCraft also refers to this as a storage destination or storage target.Deploying ShadowXafeUse the Deployment Tools to install (deploy) all necessary elements to backup and restore your data. This includes:. The OneSystem user interface. Service nodesYou can deploy OneSystem and Service Node together (on the same host machine), or you can install OneSystem on one host, and the Service Nodes on multiple other hosts in your cluster.Destination (Storage) or Target StorageThe destination or target storage is where the appliance stores your backup data. The appliance persistently stores recovery points in the storage destination. A single storage destination is the smallest storage element or unit you can address in a policy.
Also see.Differential BackupThe ShadowXafe appliance creates a differential backup if Changed Block Tracking (CBT) fails.The appliance creates a differential backup if it was unable to track the specific areas of disk that have changed since the previous backup. This can happen for host-based backup if VMware Changed Block Tracking (CBT) fails. The differential backup compares a current snapshot of the machine to a previous recovery point to determine what has changed, and backs up only those changes. The resulting recovery point is small, like an incremental backup, but takes potentially longer to create than the original full backup.Note: This definition is different than the one used by some other companies in the industry. They refer to a differential as a backup of the changes (differences) since the last Full backup.
ImageThe part of a recovery point representing the data from an individual disk on the protected machine. The image is sparse because deduplication is used to optimize used space. Incremental BackupAn incremental is a backup that includes only the changes on a machine since the previous backup.
Ignored machineWhen adding a protection environment, ShadowXafe discovers all the machines in the environment. Ignoring a machine indicates that the machine should not be backed up, and should not be included in the unprotected machines count, even if a policy has not been applied.MachineA machine is a uniquely identifiable virtual machine or physical computer in the environment that can be protected by the appliance. OneSystemOneSystem is the central control interface (the management virtual machine) for the appliance. It schedules work for the distributed service nodes (backend nodes/agents). It provides authentication and coordination between:. Storage Agents (backend agents). The vCenter server.
And the user interface (console).OneSystem also includes a dashboard to monitor SLA compliance and alerts from across multiple sites. You can watch storage consumption trends and select Protection Environments (machines and hosts to protect).
You can also select storage destinations and define, edit and assign backup policies, adjust retention, and restore backups, to OneBlox clusters or shares.PolicyThe policy combines the name, storage destination, RPO, retention settings and replication for each machine to be protected.You can create as many policies as needed. For example, you can have one policy that runs a backup once per hour and another policy that runs a backup once per every 15 minutes. One policy per site can be designated as the default, which will automatically be assigned to newly discovered machines.Important: Each source machine can have only one policy applied at a time.ShadowXafe allows you to create a protection environment, add storage and define or select a policy. The protection flow consists of the end-to-end process and elements required to backup and restore your data. This includes backing up your data, managing your data, having access to your collection of backed up images (incrementals), receiving system reports about the status of your images, and being able to restore the data you need in an easy process so it is available when you need it.Protection Appliance (ShadowXafe)The protection appliance is a dedicated backup and recovery (all-in-one) system. It includes OneSystem and various that facilitate the work of creating and managing your backups.
Protection environmentThe protection environment includes the machine source, name, host information, port, username, password and an option to select whether the connection is secure or not. See in the user guide for step-wise instructions.Recovery PointA recovery point is a collection of the information about a machine's state (i.e. The disk data and metadata) at the instant in time when a backup snapshot was taken. The appliance can fully restore a machine to the state it was in when the recovery point was created. The appliance can also use a recovery point to do a partial restore, for example, retrieving individual files or folders and their contents. Recovery point objective (RPO)A recovery point objective (RPO) is the targeted 'maximum amount of tolerable data loss'. RPO is a trade-off between the actual data loss and cost to store every change continuously. RPO helps you decide how often to run a backup.
It also identifies the granularity for available recovery points over time. For example, you may want an RPO of 1 hour for the current day, but for a month ago, an RPO of 1 day is acceptable. In other words Losing older data may be more acceptable than losing newer data.Recovery time objective (RTO)The recovery time objective (RTO) is the targeted 'maximum amount of tolerable downtime'. RTO is a trade-off between down-time and the cost of the infrastructure that supports faster recovery.
Recovery methods that use backed up data 'in-place' provide shorter Recovery Time Objectives than if you need to copy backed up data. RetentionRetention settings define how long your recovery points will be saved or stored. You can create new or change existing retention settings in the policy definitions.Important: You can only use one retention selection per policy. If you want to define additional sets of retention parameters, you need to create other policies for each new retention definition.Service NodeA service node is any machine registered that supports the appliance and handles copying data to the storage destination. Service nodes do not include your machines that you are trying to protect. See for additional information.SiteA site is a grouping of machines, service nodes and storage nodes that let the administrator control how data flows within the system. This makes efficient recovery point data transfers possible by sending backups and restores between machines and storage on the same local network.
Each site must have at least one service node deployed. The first service node deployed is known as the site leader.Site LeaderThe 'site leader' is the main/first service node on a site.
Additional service nodes can be added for scalability.SLAThe SLA status shows whether the backups and retention, etc. comply with the defined and assigned protection policies. An SLA is simply an indicator that the system is doing what you configured it to do. Source MachineThe source machine is the virtual machine that is being backed up. A recovery point for a specific source machine, when restored will create a new machine identical to the original source machine.StorageStorage in ShadowXafe can use NFS, SMB shares, local storage, or iSCSI storage. Note that the storage target should be separate from the VM where OneSystem is installed. As a best practice, the storage should not be on the same machine as OneSystem.Storage can:.
Contain recovery points. Plays a role in your policy. Be a backup destination. Be a replication source.
Be a replication target.vCenter addressThe vCenter address is required when adding protection. The vCenter address can be added in the form of an IP address, the Host name, or the Fully Qualified Domain Name. See in the First Backup chapter for step-wise instructions.VMware Transport ModesSee the VMware article about.09 - ShadowXafe Troubleshooting.
ShadowXafe RequirementsSee the in the User Guide.StorageCraft ShadowXafe v2 R4 (February 3, 2020) Enhancements. Improved Storage Service and agent performance. Added knobs (variables in the common.env file) to fine tune the environmental conditions. See ' for details.
Added self-healing disk backups if corruption is detected in the chain for that disk. Increased the drive size of the OneSystem virtual machine. You can now exclude selected volumes on agent machines from backups to reduce required storage space.
See ' for details. Improved readability for Storage Destination names displayed on the Capacity Planning screen. Improved startup messages and logging for better notification of potential startup errors.Fixed Issues. Fixed a variety of gRPC issues. Fixed replication timeouts. Fixed retry configuration.
Fixed an issue that prevented changed SMTP configurations email from being sent. Removed Retention from the Machine details page. The list of IO filters will be shown under Storage Providers in the offline state. Remove the iofilter entry from the list. Resync it, which enables the same iofilter.
Retry the VirtualBoot.StorageCraft ShadowXafe 1.6.0 (September 20, 2018) Enhancements. Added functionality that allows BitLocker to be backed up with the Windows Agent. 4212. Updated the Deployment Tool to allow updating the VAIO filter. 5182. Improved the functionality of log rotations. 5123.
Made changes to allow VirtualBoot on ESXi 6.7 with vCenter 6.7. 5091. Added the functionality to display the Cloud replication destination in the Protection page policy tool tips. 5055. Adjusted boundaries on RPO recovery points for retention policy. The limits are: hourly (1-9999), daily (1-13650), weekly (1-5200), monthly (1-1200).
5080. Improved the functionality and stability of clickable buttons when using the Edge browser. 5040. Improved the accuracy of Capacity Planning Projection. 5043. Improved Capacity Planning (collected) dashboard reporting accuracy and consistency.
5038. Improved SLA accuracy and messaging for items that need attention. 5024. Improved the automatic refresh of the SLA Detail Table.
4714. Improved accuracy of transfer rate reporting for Windows Agent backups. 4886.
Improved the refresh functionality for Projection Date updates screen. 4729Fixed Issues. Fixed an issue caused by recovery points that failed to mount.
This prevented the service leader from starting or registering. 5249. Fixed an issue that occasionally prevented a VirtualBoot agent machine from booting. 5184. Fixed an agent display error: 'Key Not Found' that could happen if you created an initial backup and then added a new volume. 5069.
Revised the functionality when deleting Non Default sites. Removing sites no longer removes backend VMs. Backup VMs now need to be removed manually. 5053. Fixed an issue with a double-byte character in the name of a virtual machine that was preventing Instant Restore Booting. 5039.
Fixed incorrectly reported and misleading error message 'Unable to communication with machine.' The error message was being displayed, but the backups were still working. 5030.
Fixed an unknown error that was reported if a disk filled during restore transfer. 4997. Fixed an issue where disks attached to service nodes when a backup failed, stayed attached and the disks needed to be manually removed. 4965. Fixed an issue that was causing an 'unexpected error occurred' message to be displayed when storage a node was unmounted in the ShadowXafe user interface. 4964.
Fixed an unknown error message that was occasionally displayed when backup jobs failed. 4936. Fixed an issue that was preventing machines without backups from being displayed in in the Assigned Policies table if a policy was assigned. 4609.
Fixed an issue where the message “email successfully sent” was not displayed when a new user was created. 4520. Fixed a display issue that was causing the protection environment to disappear from the ShadowXafe user interface when upgrading. 4412. Fixed an issue that caused problems with the IO filter’s SSL when editing Storage Policy Backup Management in vCenter.
How to Uninstall oneSafe 1.5.2 Application/Software on Your MacUnlike the software developed for Windows system, most of the applications installed in Mac OS X generally can be removed with relative ease.oneSafe 1.5.2 is a third party application that provides additional functionality to OS X system and enjoys a popularity among Mac users. However,instead of installing it by dragging its icon to the Application folder, uninstalling oneSafe 1.5.2 may need you to do more than a simple drag-and-drop to the Trash.When installed, oneSafe 1.5.2 creates files in several locations. Generally, its additional files, such as preference files and application support files,still remains on the hard drive after you delete oneSafe 1.5.2 from the Application folder, in case that the next time you decide to reinstall it,the settings of this program still be kept. But if you are trying to uninstall oneSafe 1.5.2 in full and free up your disk space,removing all its components is highly necessary. Continue reading this article to learn about the proper methods for uninstalling oneSafe 1.5.2.
Manually uninstall oneSafe 1.5.2 step by step:Most applications in Mac OS X are bundles that contain all, or at least most, of the files needed to run the application, that is to say,they are self-contained. Thus, different from the program uninstall method of using the control panel in Windows,Mac users can easily drag any unwanted application to the Trash and then the removal process is started.
Despite that,you should also be aware that removing an unbundled application by moving it into the Trash leave behind some of its components on your Mac.To fully get rid of oneSafe 1.5.2 from your Mac, you can manually follow these steps: 1. Terminate oneSafe 1.5.2 process(es) via Activity MonitorBefore uninstalling oneSafe 1.5.2, you’d better quit this application and end all its processes.
If oneSafe 1.5.2 is frozen, you can press Cmd +Opt +Esc, select oneSafe 1.5.2 in the pop-up windows and click Force Quit to quit this program (this shortcut for force quit works for theapplication that appears but not for its hidden processes).Open Activity Monitor in the Utilities folder in Launchpad, and select All Processes on the drop-down menu at the top of the window. Select the process(es) associated with oneSafe 1.5.2 in the list, click Quit Process icon in the left corner of the window, and click Quit in the pop-up dialog box (if that doesn’t work, then try Force Quit). Delete oneSafe 1.5.2 application using the TrashFirst of all, make sure to log into your Mac with an administrator account, or you will be asked for a password when you try to delete something.Open the Applications folder in the Finder (if it doesn’t appear in the sidebar, go to the Menu Bar, open the “Go” menu, and select Applications in the list), search for oneSafe 1.5.2 application by typing its name in the search field, and then drag it to the Trash (in the dock) to begin the uninstall process.
Alternatively you can also click on the oneSafe 1.5.2 icon/folder and move it to the Trash by pressing Cmd + Del or choosing the File and Move to Trash commands.For the applications that are installed from the App Store, you can simply go to the Launchpad, search for the application, click and hold its icon with your mouse button (or hold down the Option key), then the icon will wiggle and show the “X” in its left upper corner. Click the “X” and click Delete in the confirmation dialog. Remove all components related to oneSafe 1.5.2 in FinderThough oneSafe 1.5.2 has been deleted to the Trash, its lingering files, logs, caches and other miscellaneous contents may stay on the hard disk. For complete removal of oneSafe 1.5.2, you can manually detect and clean out all components associated with this application. You can search for the relevant names using Spotlight. Those preference files of oneSafe 1.5.2 can be found in the Preferences folder within your user’s library folder (/Library/Preferences) or the system-wide Library located at the root of the system volume (/Library/Preferences/), while the support files are located in '/Library/Application Support/' or '/Library/Application Support/'.Open the Finder, go to the Menu Bar, open the “Go” menu, select the entry: Go to Folder.
And then enter the path of the Application Support folder:/LibrarySearch for any files or folders with the program’s name or developer’s name in the /Library/Preferences/, /Library/Application Support/ and /Library/Caches/ folders. Right click on those items and click Move to Trash to delete them.Meanwhile, search for the following locations to delete associated items:. /Library/Preferences/. /Library/Application Support/. /Library/Caches/Besides, there may be some kernel extensions or hidden files that are not obvious to find. In that case, you can do a Google search about the components for oneSafe 1.5.2. Usually kernel extensions are located in in /System/Library/Extensions and end with the extension.kext, while hidden files are mostly located in your home folder.
You can use Terminal (inside Applications/Utilities) to list the contents of the directory in question and delete the offending item. Empty the Trash to fully remove oneSafe 1.5.2If you are determined to delete oneSafe 1.5.2 permanently, the last thing you need to do is emptying the Trash.
To completely empty your trash can, you can right click on the Trash in the dock and choose Empty Trash, or simply choose Empty Trash under the Finder menu (Notice: you can not undo this act, so make sure that you haven’t mistakenly deleted anything before doing this act. If you change your mind, before emptying the Trash, you can right click on the items in the Trash and choose Put Back in the list). In case you cannot empty the Trash, reboot your Mac. Tips for the app with default uninstall utility:You may not notice that, there are a few of Mac applications that come with dedicated uninstallation programs.
Though the method mentioned above can solve the most app uninstall problems, you can still go for its installation disk or the application folder or package to check if the app has its own uninstaller first. If so, just run such an app and follow the prompts to uninstall properly. After that, search for related files to make sure if the app and its additional files are fully deleted from your Mac.
Automatically uninstall oneSafe 1.5.2 with MacRemover (recommended):No doubt that uninstalling programs in Mac system has been much simpler than in Windows system. But it still may seem a little tedious and time-consuming for those OS X beginners to manually remove oneSafe 1.5.2 and totally clean out all its remnants. Why not try an easier and faster way to thoroughly remove it?If you intend to save your time and energy in uninstalling oneSafe 1.5.2, or you encounter some specific problems in deleting it to the Trash, or even you are not sure which files or folders belong to oneSafe 1.5.2, you can turn to a professional third-party uninstaller to resolve troubles. Here MacRemover is recommended for you to accomplish oneSafe 1.5.2 uninstall within three simple steps. MacRemover is a lite but powerful uninstaller utility that helps you thoroughly remove unwanted, corrupted or incompatible apps from your Mac. Now let’s see how it works to complete oneSafe 1.5.2 removal task. Download MacRemover and install it by dragging its icon to the application folder.
Launch MacRemover in the dock or Launchpad, select oneSafe 1.5.2 appearing on the interface, and click Run Analysis button to proceed. Review oneSafe 1.5.2 files or folders, click Complete Uninstall button and then click Yes in the pup-up dialog box to confirm oneSafe 1.5.2 removal.The whole uninstall process may takes even less than one minute to finish, and then all items associated with oneSafe 1.5.2 has been successfully removed from your Mac! Benefits of using MacRemover:MacRemover has a friendly and simply interface and even the first-time users can easily operate any unwanted program uninstallation. With its unique Smart Analytic System, MacRemover is capable of quickly locating every associated components of oneSafe 1.5.2 and safely deleting them within a few clicks. Thoroughly uninstalling oneSafe 1.5.2 from your mac with MacRemover becomes incredibly straightforward and speedy, right?
You don’t need to check the Library or manually remove its additional files. Actually, all you need to do is a select-and-delete move. As MacRemover comes in handy to all those who want to get rid of any unwanted programs without any hassle, you’re welcome to download it and enjoy the excellent user experience right now!This article provides you two methods (both manually and automatically) to properly and quickly uninstall oneSafe 1.5.2, and either of them works for most of the apps on your Mac.
If you confront any difficulty in uninstalling any unwanted application/software, don’t hesitate to apply this automatic tool and resolve your troubles.