| Arcserve |
6.0 Installation
6.1 Prerequisite Tasks
6.2 Installation Instructions
Welcome to the Arcserve UDP Version 5.0 Update 2 Release Notes. This Release Notes contains important information about this update.
The following enhancements or features have been added to Arcserve UDP for this update:
Allows you to migrate backup data on a share folder or data store from Arcserve D2D r16.5 or Arcserve UDP Version 5.0 to a data store of the selected RPS server.
Note: For Arcserve UDP Version 5.0 sessions, both migration from "share folder to data store" and "data store to data store" are supported. For Arcserve D2D r16.5 sessions, only "share folder to data store" is supported.
Note: This update does not support BMR to a smaller disk if the sessions are migrated from Arcserve D2D r16.5, Arcserve UDP Version 5.0, or Arcserve UDP Version 5.0 Update 1. It only supports BMR to smaller disk when the sessions are backed up from Arcserve UDP Version 5.0 Update 2.
Allows you to import virtual machines that reside in a Windows cluster environment and protect them.
Note: Only Windows 2012 and Windows 2012 R2 cluster are supported in this update.
Sends email alerts if a new virtual machine is found in Hypervisor. You can configure the hypervisor manually in Node Discovery Configuration.
Allows you to use No Charge Edition for Workstation Operation System when backing up to a non-RPS data store.
Allows you to restore mailboxes, folders in a mailbox, and mail objects from the host-based backup sessions without installing Arcserve UDP Agent (Windows) inside the guest VM.
Note: This applies to VMware only.
Allows you to protect (backup and restore) the Pervasive SQL database.
Note: This task is not available from Arcserve UDP Agent (Windows). To perform this task, follow the manual steps provided in the Arcserve UDP Agent (Windows) User Guide.
Allows you to protect (backup and restore) the Oracle database.
Note: This task is not available from Arcserve UDP Agent (Windows). To perform this task, follow the manual steps provided in the Arcserve UDP Agent (Windows) User Guide.
Allows you to delete node data (all recovery points) from RPS server data store view. The deletion operation will be tracked as jobs and activity log messages will track which nodes are deleted. You can manually delete the recovery point of the data store in the Browse Recovery Points panel.
Provides APIs for third-party developers to access core features of Arcserve UDP, including node management, RPS and data store management, plan management, job monitor and job histories, querying activity logs, deploying the agent and adding licenses.
In Arcserve UDP Version 5.0, you can specify the order of the transport mode for VMware VM backup in the registry key on the proxy server. Now you can do the same on the Console when creating a host-based agentless backup plan.
Allows you to specify which days of the week do not need a daily backup when configuring the daily backup plan.
Allows you to add new nodes when creating a plan. If you add existing nodes here, the nodes will be updated.
Even after you download and install Arcserve UDP Version 5.0 Update 2 manually, you can remote deploy the agent and RPS with the same level update.
Calculates the used and remaining capacity in License Manager for Arcserve UDP Managed Capacity License.
Allows you to cancel the scheduled deployment task manually for both the Agent and RPS.
Allows you to create a host-based agentless backup plan using the Copy Recovery Point task.
You can specify the No Compression – VHD compression option in both the on-demand copy recovery point job and scheduled copy recovery point job, so that the copied disk file can be mounted directly on a Windows operating system.
Provides a command-line utility to check the data integrity at the recovery point level and data store level for a deduplicated data store. The command-line utility also supports regenerating the hash database in case the original hash database is broken.
When performing a VM recovery, for each of the disks, you can now specify a disk type which is different with the original VM, so that you can convert the disk type during VM recovery. This works for both VMware VM (disk types are thin provision, thick provision lazy zeroed and thick provision eager zeroed) and Hyper-V VM (disk types are dynamic expanding and fixed size).
When adding/updating Linux nodes, you can input Non-Root credentials for those Linux nodes.
The purpose of this feature is to keep data consistent in the backup of cluster shared disks. When cluster failover happens since the last successful backup, in the next incremental backup on the node which hosts the cluster shared disk, it will perform a full backup for the cluster shared volumes. For the other non-clustered shared volumes, it will still perform an incremental backup.
Note: BMR does not support restore cluster shared disks. So before performing a BMR for the cluster node, you need to disconnect the shared disk first.
Customize new asynchronous read mechanism for backing up Arcserve UDP deduplication recovery point to tape: all time-consuming operations (for example reading data, transferring data, decompressing data, etc) for getting source recovery point data will be processed in parallel. Introduce new caching and sorting mechanism to avoid reading duplicated data blocks and decrease disk seek frequency. The job throughput of backing up an Arcserve UDP deduplication recovery point to tape will be greatly improved.
When you create or modify a plan to select a node as a backup source or backup proxy, Arcserve UDP checks whether the agent is installed on the node and if it is the latest version when saving the plan, Arcserve UDP then displays a verification dialog that lists all the nodes that either have an outdated version of the agent or does not have the agent installed to define install/reboot schedule.
Arcserve Backup r16.5 SP1+ RO75131 is supported with Arcserve UDP Version 5.0 Update 2. With this release, performance improvement for tape backups of Arcserve UDP nodes is included. For more information on Arcserve Backup integration, see the Arcserve Backup r16.5 SP1 Updates Release Summary.
This update fixes the following issues, which could have occurred:
Fixes the host-based backup recover VM issue. This problem only happens when Recover VM is performed using the session created out of integration with Arcserve Backup raw session restore.
Note: This applies to password protected sessions on the Arcserve UDP side.
Fixes the database recovery model changes from full to simple and from simple to full during the backup time. The fix prevents potential data loss.
Fixes the Arcserve UDP Agent (Windows) report for two error log messages in the activity.log when you run a backup.
For a VM node that specified a hypervisor, the VSB job needs an additional license after the backup job is successful.
For a VM node imported from vCenter, the backup job consumes a license for vCenter node, and not the actual ESXi node.
For a VM node which is hosted on a VMware workstation, Arcserve UDP is unable to identify the VM as a virtual machine.
For a VM that specified hypervisor to the hypervisor which has more than one sockets. Backup job always consume one license count even the hypervisor has more than one sockets.
Fixes a problem where a backup of an agent node is failing with a license error in some cases where the agent and console are on the same machine, but the agent cannot communicate with the console using a local host name.
Fixes a scheduled job not launched at 23:59 when the end time is set to 23:59. This is caused by the schedule end time being set to 00:00 in this case. Change the scheduled job end time to 23:59:59 instead of 00:00.
Provides support for a non-root user to restore to any folder.
Fixes a problem where the host-based backup proxy is unable to browse the recovery point and you receive the following message:
"Error: Failed to browse recovery point: The remote procedure call failed."
Fixes an exception in thread "main".
Fixes the problem of “The Hotadd disks are not automatically removed from the proxy VM after the backup job completes”.
Fixes a problem where the recover VM fails with invalid parameter.
Fixes the problem of “Failure of locating the disk data when creating a VHD in Windows 2008 Hyper-V host while using the VHD in Windows 2008 R2 or higher Hyper-V host”.
Fixes the problem where the Arcserve UDP Agent Service terminates unexpectedly after a merge job.
Includes the correct driver from local drivers while creating a BMR ISO.
Fixes the problem that after running a backup, the recovery points are deleted.
Fixes the problem “A Arcserve UDP Agent (Windows) full backup will be performed after a Arcserve UDP Agent (Windows) incremental backup completes and the Arcserve UDP web service is restarted".
Fixes the error “Arcserve UDP Agent (Windows) restore fails with error code 32 when the restore location already has the same file there”.
Fixes a crash problem “Arcserve UDP Agent (Windows) Copy session job crashes”.
Provides support for the Linux system with thousands of logical volumes but several mounted for Arcserve UDP Agent (Linux). The volumes information is collected first and then a query of the volume can be performed quickly if needed.
Provides support for fake raid backup, for example /dev/mapper/nnn for Arcserve UDP Agent (Linux).
Fixes a problem where a VM machine is unable to boot after VSB converts to ESX. The following error is issued:
Security Accounts Manager initialization failed because of the following error: Directory Service cannot start, Error Status: 0xc00002e1
After Virtual Standby convert, the VM cannot startup and will receive a blue screen with error code 0x7B when a driver is needed for the SCSI disk on the source machine.
Fixes a problem of a crash in AFBackend.dll.
Backup failed on NAS with error code 0x05..
Fixes a problem where the merge will fail with error code 6..
Fixes a security vulnerability problem.
Fixes the problem that when clicking the data store link on the “Recovery Point Servers” console, to checking the node list protected by the data store, the console pops up an error message that the data store management service is down. But in fact, the service is running. Meanwhile, the node list cannot be displayed.
Fixes the problem where the backup job crashes at AFBackupDll.dll.
Fixes the problem where the host based VM backup job fails with the following errors in the Host-Based VM Backup-<date>-<time>-...log file:
"CD2DOffhostESXMachine::CreateSnapshot::pf_V2PNF_TakeSnapshot() failed. diskcnt=x, rc=1, msg = Cannot create a quiesced snapshot because the snapshot operation exceeded the time limit for holding off I/O in the frozen virtual machine."
Fixes the problem where an Arcserve UDP agentless backup creates temporary folders on the C drive on the guest OS, but fails to delete them after the backup is completed.
Fixes the problem that no VMs were discovered when importing the VMs from a French Edition Hyper-V host, on which the VM caption “Virtual Mchine” of wmi object Msvm_ComputerSystem is localized in French. In the fix, the GUID and data folder of the virtual machine are used to validate the virtual system for importing the VM instead of using the caption which might be localized.
Fixes the problem that an Arcserve UDP backup job will crash when it is collecting BMR information.
Fixes the problem that the UEFI VM cannot boot after VSB. The following error occurs: “Boot failed. EFI SCSI Device".
This problem is encountered when copying data by bitmap for a UEFI volume. Now it is fixed by copying the whole volume for every backup.
Fixes the problem that the scheduled Arcserve Backup Data Synchronization did not run.
Fix resolves the deployment issue of Arcserve D2D from Central Protection manager to a remote node with very large disk space.
Fixes a security vulnerability problem.
Fixes the problem where the full backup job completed successfully even if some of the writers are skipped from the backup due to bad status.
Fixes a crash during an incremental backup.
Fixes a crash during an incremental backup.
Fixes the problem during a BMR, where the machine could receive a BSOD during start up. This would happen if the target machine has a larger disk than the source machine. Opening the dump file with Windbg shows bugcheck code DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1).
Fixes the problem where the full backup job completed successfully even if some of the writers are skipped from the backup due to bad status.
Fixes a problem where you are unable to browse recovery points.
Fixes a problem where a backup fails with error code 64.
Fixes the read/write file error (error code 87 and 2) during the backup job.
Fixes a security vulnerability problem.
Fixes a problem where the data store is in an inconsistent state.
Fixes the problem that when a customer uses Volume GUID as the backup destination, an incremental backup will be converted to a full backup.
Fixes the problem where the Arcserve UDP host-based backup creates temporary folders on the c drive on the guest OS, but fails to delete them after the backup is completed.
Fixes the problem where the backup job crashes at AFBackupDll.dll. It is caused by an out of index error if it cannot collect writer data from inside guest OS.
Fixes the problem where creating the Granular Restore catalog in Exchange 2013 fails.
Fixes a problem where no mailbox was shown in the restore email, even though the Exchange catalog was created successfully.
Fixes the problem where Exchange Granular Restore mail restores successfully however an error message is logged in the activity log.
Fixes the problem where Exchange mail restore login failed on the Granular Restore validation screen.
Fixes a problem when restoring the whole mailbox, the restore job crashes.
Fixes a problem with Exchange Granular Restore on the Agent, where the option for Exchange catalog generation is grayed out.
Fixes a problem where incorrect information is displayed in the restore window.
Fixes the problem where an Exchange Granular Restore catalog job was successful, but nothing was created.
Fixes a problem with reporting sync process.
Fixes a problem so that a Run Now job does not need a makeup job. This problem occurs if any type of backup is scheduled to repeat every 1 day or longer period, and the next job is scheduled on the day after the next day or later.
Fixes a problem where the users access UNC path status is incorrect, and may cause the VSB job to fail.
Fixes a problem that fails to inject the VMXNET3 driver in BMR.
Fixes a problem that when creating more than two primary partitions in BMR Advanced mode, it fails.
Fixes a configuration issue that when backing up two virtual machines using Arcserve UDP, the backups are successful, but randomly the VM consolidation message comes up for different VMs.
Fixes a problem when there are several concurrent agent-less backup jobs launched for Hyper-V virtual machines, the backup job may be converted from an incremental backup to a full backup.
Fixes a problem where an Arcserve UDP BMR will fail after a Host-Based VM Backup and there is no BootVolume/VolumeName system information in the adrconfig file.
Fixes a problem when restoring the mail objects whose account has a different account name and display name, the restore job may fail.
Fixes a problem when the File System Catalog job for an agent-less session is completed, it still displays in the dashboard for In-Progress jobs.
Fixes a problem when the Exchange Granular Restore job runs, it occupies a lot of memory.
Fixes a problem when the Arcserve UDP Agent user does not have access to a file, then it cannot be listed in the restore UI.
Fixes a problem in the email alert generated by an agent-less host-based backup job, which adds a row for the backup size.
Fixes a license error, that when you back up a VMware guest with Arcserve UDP, the VSB of this VM guest fails with the following error:
"Virtual Standby job failed because of license failure. Contact your account representative to obtain a new license."
Fixes a problem where the VHD/VHDX files of a standby VM snapshot, which are created by a full backup session, are not merged after the snapshot is deleted during conversion. That will cause the disk space to keep growing.
Fixes a problem that some system files are not listed in the restore UI.
Fixes a problem where check for updates cannot connect to the Arcserve server in a certain firewall policy.
Fixes a problem that when the Exchange granular restore job runs, it may crash.
The SSL protocol 3.0, as used in OpenSSL through 1.0.1i and other products, uses nondeterministic CBC padding, which makes it easier for man-in-the-middle attackers to obtain clear text data via a padding-oracle attack, such as the "POODLE" issue. This fix will refuse the connection from the client using SSL 3.0 and consequently attackers cannot hijack the connection and obtain the clear text data.
You will need to run the utility “ChangeToHttps.bat” to disable SSL3.0 if the following conditions exist:
Arcserve UDP Version 5.0 Update 1 is available.
Fixes a problem when performing a BMR in advanced mode, where you cannot create three or more partitions on a MBR disk.
Fixes a problem that failed to integrate the drivers for vmxnet3 when creating a BMR image.
Fixes a problem that if the source disk size is changed in an incremental backup, the incremental backup will forcibly do one full backup for the specific disk. It encounters a problem when merging the incremental recovery point later (because it still regards the full disk as an incremental disk).
An issue exists for VDDK that backed up data might be corrupted in the case that a virtual disk is increased from a size less than 128 GB to a size larger than 128 GB. The fix is to follow the workaround suggested by the VMware KB article.
When using HotAdd mode to back up a VM, the disk file of the VM is mounted into the proxy machine. But in the case where the backup job aborts abnormally (for example, job crash or job is killed), that disk will keep being mounted. This fix is to clean the hotadded disk from the proxy VM when the next backup job starts.
Fixes a problem with an incorrect network series. You can see the replication timeout.
Fixes a problem that cannot discover the VMs in the VMware ESXi cluster when a cluster member's ESXi host is in a disconnected status.
Fixes a problem with Advanced schedule triggering a job. At the end of DST time, after restarting the service, the agent may trigger multiple makeup jobs.
For all issues fixed in this release, see the Arcserve UDP Version 5.0 Release Notes.
The following issues could exist in this update:
Symptom
VMware has a bug when quiescing a VM so that its snapshot contains corrupted data. The backup reads data from the snapshot so that the data backed up also becomes corrupted. For more information about this issue, see the following VMware KB article: Application quiescing with Windows 2008 R2 SP1 and Windows 2012 with vSphere Data Protection, VMware Data Recovery, and third-party backup software (2146402).
Note: This problem can occur with all VMware ESXi versions and on a VM with guest OS Windows 2008 R2 SP1 and Windows 2012. The data corruption problem cannot be detected by the software because VMware does not return an error in this case. This may lead to the situation that you are not aware of the problem until you try to restore some data.
Solution
For more information about how to detect any data corruption and the corresponding solution/workaround, see the Arcserve KB article.
Symptom
If you have performed the following:
Then, the downloaded Arcserve UDP Version 5.0 Update 2 cannot be deployed properly through the Console. This may cause an indefinite loop of Agent remote deployment.
Solution
For more information about the work around, see the Arcserve KB article.
Symptom
This problem can happen when you are using a FQDN name to add the host to the Console. When the Agent node is rebooted, it will notify the Console to remove the pending reboot status, but using the short hostname. The FQDN name and the short hostname mismatch causes this mechanism to fail, so the pending reboot warning is still there. Also if a machine is added using a FQDN name and the machine does not have any Arcserve UDP products previously installed, and now you trigger a remote deployment, after the remote deployment is completed and before pending reboot status is removed, the backup may fail.
Note: This may impact Arcserve UDP Version 5.0 Update 2 users who are using FQDN name and deploy Arcserve UDP Version 5.0 Update 2 to these FQDN named Agent nodes.
Solution
On the Console UI Nodes View, right-click the node and run Install/Upgrade Agent again. This will solve both the pending reboot warning problem and the backup failure after deploying Arcserve UDP Version 5.0 Update 2 to a fresh machine problem.
Symptom
When the source machine is a Windows 8.1 or Windows 2012 R2 system and you perform a BMR on a machine with a 4 KB disk, it may fail to boot the machine after BMR with error message: system_thread_excption_not_handled (WppRecorder.sys).
Solution
Boot to the recovery console (you should automatically get there after a few Blue Screen crashes).
c:\windows\system32\compact.exe /U c:\windows\system32\drivers\*.sys
fsutil behavior set DisableCompression 1
Symptom
A migration job does not show in the Nodes list view on the resources tab.
Solution
Access the RPS view or dashboard tab to check the job monitor.
Symptom
Cannot browse volumes in the Arcserve UDP Recovery Point View.
Solution
Use a UNC path directly instead of mapping to a network drive.
The Windows version of proxy [<Proxy Name>] is an earlier version than virtual machine [<Virtual Machine Name>]. As a result, the subsequent Exchange catalog job may fail, and you will need to install the related Windows update package to resolve the problem."
Symptom
The Exchange catalog job will use the Exchange binaries from the virtual machine. If the Windows version of the proxy machine is an earlier version than the virtual machine, the Exchange binaries do not work well, and as a result, the catalog job will fail.
Solution
Install the following Windows update package to resolve the problem:
Symptom
Failover happens for the clustered VM before taking a snapshot when backing up a VM. This causes the Hyper-V host recorded in the backup session to be inconsistent with the VM configuration.
Solution
You can manually connect the network adapter to a virtual switch on its Hyper-V host or use the Restore to an alternative location option to recover the VM with which you can set the restore configuration for the VM.
Symptom
Suppose you migrate a Linux Backup Server to the Arcserve UDP Console. If you release the Linux Backup Server and then migrate it again, you will see a new plan is automatically created on the Console.
Example:
You have a Linux Backup Server1 that manages Linux_Node1. You have created a backup job named New Plan. You also have a Arcserve UDP Console that manages Linux_Node2 and Linux Backup Server2 and the plan is also named New Plan.
You migrate Linux Backup Server1 to Console using the d2dreg command. After the migration, the backup job name changes to New Plan_<Linux Backup Server1>. Deploy New Plan_<Linux Backup Server1>.
Now you add Linux_Node1 to New Plan and add Linux Backup Server1 as the server and deploy the plan. New Plan now protects Linux_Node1 and Linux_Node2 and the server is Linux Backup Server1.
Now you release Linux Backup Server1 from Console. Delete New Plan and New Plan_< Linux Backup Server1> from Console. When you migrate Linux Backup Server1 again to Console, two plans get migrated: New Plan and New Plan_<Linux Backup Server1>.
Solution
Delete the new plan. The new plan does not have any nodes, therefore, it does not affect any backup schedule.
Symptom
Although the backup job of one virtual machine has already finished, the virtual machine's status is still “Backup up” in the Hyper-V Manager. Therefore, if another backup job for this VM starts at this time, it will fail with error “The Hyper-V VSS writer has encountered an error when processing this virtual machine”. In addition, you cannot perform some operations, such as power on/off for the VM at that time in Hyper-V manager. And if the VM is Hyper-V cluster, you cannot perform live migration for it.
This problem happens during the following situations:
• There are several backup jobs starting at the same time or at times close to each other (within 1 minute).
• One or more backup jobs finished, but there is still at least one backup job which is still in progress.
Root of the problem:
To avoid bringing unnecessary workload to the Hyper-V host, instead of taking one VSS snapshot for each VM, Arcserve UDP tries to take one VSS snapshot for all VMs if their backup jobs start at the same time or at times close to each other. After the VSS snapshot is taken, all the VMs inside this VSS snapshot instance will be “locked” (in Backing up status). Because Arcserve UDP cannot release the snapshot until all backup jobs are finished, even if the backup job of a VM already completed, that VM is still “locked”. Due to the limitation of VSS snapshot that only one snapshot can be taken for one VM at one time, if another backup job of the same VM starts at this time, it will fail with the error “The Hyper-V VSS writer has encountered an error when processing this virtual machine”. In addition, some operations (such as power on/off) are disabled in Hyper-V Manager and, if the VM is in a Hyper-V cluster, live migration is also not allowed. This does not happen in Hyper-V 2008R2 because Hyper-V 2008R2 has different behavior on the VSS snapshot mechanism.
Solution
While the VM is “locked”, you can still use the guest OS as normal. Therefore, this has no impact on the usage/availability of the guest OS. However, if you have concerns and want to avoid this situation, it is suggested that you use different plans to protect VMs which have a different size. In other words, include the VM with a similar size in one plan so that those backup jobs take a similar amount of time and, at the same time, set different schedules for those plans.
Symptom
The UI may respond slowly when accessing Arcserve UDP Agent (Windows) from Internet Explorer 10 or 11, if you are using any of the specific versions of Internet Explorer 10.0.9200.17XXX and Internet Explorer 11.0.9600.17XXX.
If this issue occurs, all other subsequent requests will wait for response for 5 minutes.
This issue only happens when using any of the versions of Internet Explorer 10 and 11 mentioned. All other browsers do not have this issue.
Solution
Perform one of the following temporary solutions:
Perform the following permanent solution:
Symptom
The network parameter WAN_SendCommandFragDataMerged in the registry (located in HKEY_LOCAL_MACHINE\SOFTWARE\CA\ARCserve Unified Data Protection\Engine\Network) used the incorrect value (the value was 1 and should be 0) as the default in Arcserve UDP Version 5.0 Update 1. If upgrade to Update 2, this registry key will keep the old default value. It will cause some performance problems for the replication over WAN. The fresh installation of Update 2 will not be affected by this issue.
Solution
Manually change the value of the registry key WAN_SendCommandFragDataMerged from 1 to 0 in HKEY_LOCAL_MACHINE\SOFTWARE\CA\ARCserve Unified Data Protection\Engine\Network.
Symptom
The behavior of the operating system creates the offline state by default.
The SAN policy was introduced in Windows Server 2008 to protect shared disks that are accessed by multiple servers. The default SAN policy from the source VM is “Offline Shared” for all SAN disks except the boot disk. Setting the policy to Offline enables the SAN disks to be offline during startup. After recovery, a new disk for the VM is created. The disk file from the VM appears to be a SAN disk where the operating system identifies it as being offline. When the offline disk is set to be back online, the disk remains online even after rebooting the system.
Solution
As a workaround, specify the DISKPART.exe command: SAN POLICY=OnlineAll setting for the source VM before backup. Because the disks can be shared among other servers, data corruption can occur. You must use the correct SAN policy to protect the data.
DISKPART.EXE command line
Query SAN policy:
DISKPART > san
SAN Policy: Offline Shared
Change SAN policy:
DISKPART > san policy=OnlineAll
DISKPART successfully changes the SAN policy for the current operating system.
For all known issues in this release, see the Arcserve UDP Version 5.0 Release Notes.
The following limitations could exist in this update:
Note: This limitation exists only for VMware VMs, which has the option to set the OS type. For Hyper-V, this problem does not exist.
For all limitations in this release, see the Arcserve UDP Version 5.0 Release Notes.
The following sections provide information about installation prerequisites and installation instructions.
Consider the following prerequisite tasks before installing this update:
When installing the Arcserve UDP update or the Arcserve UDP Agent (Windows) update, it is important to maintain optimal performance between the Console, the Recovery Point Server (RPS), and the Agents. As a result, when the update is installed in an environment that contains both a Console and an Agent, you must always install the update on the Console first, and then on the RPS, and finally on the Agent. (For the Agent that is installed on the Console or the RPS, the update will be automatically installed on that Agent at the same time).
Note: If you have an environment with both Arcserve UDP and Arcserve Backup installed, and you want to install Arcserve UDP Version 5.0 Update 2, you need to also install the corresponding Arcserve Backup patch RO75131 at the same time.
Important! When updating to Arcserve UDP Version 5.0 Update 2, a system reboot may be required. For more information about the system reboot after upgrade, see the KB article.
You can use two methods to install the update; by using the update utility or manually:
Installing the Update Using the Update Utility
To install the update using the update utility from the Home Page, follow these steps:
Note: For the Full Installation, this step also automatically downloads the necessary packages for remote deployment to the RPS and the Agent. For the Agent only installation, this completes the update process.
Note: For more information about updating Arcserve UDP, see the Solutions Guide. For more information about updating Arcserve UDP Agent (Windows), see the Agent for Windows User Guide.
Installing the Update Manually
For an upgrade installation package for Windows servers and workstations that have a previous version of Arcserve UDP already installed, download and install the update manually using the following links to the installation files:
For a fresh installation package for Windows servers and workstations that do not have Arcserve UDP installed yet, download and install the update manually using the following links to the installation files:
For a Linux installation, download and install the update manually using the following links to the installation files:
The Arcserve Support team offers a rich set of resources for resolving your technical issues and provides easy access to important product information.
With Arcserve Support:
Copyright © 2015 Arcserve. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.