Appliance Related

• Arcserve UDP version number is not updated in the Console after replacing the Appliance image.
• Symptom
• After replacing the Appliance image through the Set Appliance Image Utility tool, the Original Arcserve UDP version is not updated automatically in the Factory Reset page of Arcserve UDP Console.
• Solution
• As a workaround, you need to reload the page and verify again.
• Appliance RPS node is not updated in the UDP Console after upgrade from UDP v6 or UDP v5.
• Symptom
• If you do not update the Appliance RPS node,
  • All the jobs performed on the Appliance RPS node after upgrade do not consume the Appliance license and search for non-Appliance license.
  • Appliance RPS node does not show the Appliance model information in the UDP Console.
• Solution
• You need to manually update all the Appliance RPS nodes after the upgrade.
• Appliance wizard login fails through browser.
• Symptom

If you restart the Arcserve Appliance system after modifying the hostname and try to log into Appliance wizard using browser, the login fails and displays security certificate error.

Solution

As a workaround, select the Continue to this website (not recommended) option in the browser for successful login.

• Appliance wizard login fails through browser.
• Symptom
• If you restart the Arcserve Appliance system after modifying the hostname and try to log into Appliance wizard using browser, the login fails and displays proxy error.
• Solution
• Relaunch the browser after sometime.
• User configuration information is lost while using Consolemigration.exe to migrate arcserveWSO2 database to the new UDP console.
• Symptom
• When you use ConsoleMigration.exe in Arcserve UDP v7.0 to migrate UDP console database, only the arcserveUDP database gets completely migrated to the new UDP console. However, the roles and corresponding permissions of users stored in the arcserveWSO2 database is lost during migration to the new UDP console.
• Solution
• Follow these steps:
1. 1. Apply patch T00001685 to Arcserve UDP v7.0.
2. 2. Re-run ConsoleMigration.exe to migrate the UDP console database:
1. To backup UDP database for old Arcserve UDP console, run ConsoleMigration.exe -BackupDB.
2. To recover database to new Arcserve UDP console, run ConsoleMigration.exe -RecoverDB.
3.  
• Despite complete execution of Customer_Boot.ps1, the Sophos Endpoint Installer does not register the Arcserve Appliance with Sophos Central.
• Symptom
• Even with complete execution of Customer_Boot.ps1 script, which includes correct parameters such as mcstoken and management server string, the Sophos Endpoint Installer doesn't register the Appliance server with Sophos Central. The customer is unable see the Appliance server hostname displayed on the Sophos Central Admin portal.
• Solution
• Follow these steps:
1. Remove the registration.txt file from the folder location:
   C:\ProgramData\Sophos\Management Communications System\Endpoint\Config
2. To re-register with Sophos Central, run the Customer_Boot.ps1 again.
• After using SetImage.exe to replace factory reset image, when you choose not to preserve data and revert Arcserve Appliance to default factory settings, the SSD disk does not get formatted properly. Hence, the default deduplication data storage does not get created when you use the Appliance Configuration wizard to configure the Arcserve UDP plan.
  This issue occurs only on the 9000 series Appliance with RAID-1 SSD configuration.
• Symptom
• After reverting the 9000 series Appliance to factory default settings, when you use the Appliance Configuration Wizard to configure the Arcserve UDP plan, the following error message generates:
• The data store hash destination “Y:\” is invalid.
• Solution
• To create default deduplication data store on Appliance Configuration Wizard, follow these steps:
1. Open Disk Management.
2. Initialize SSD, then format and assign the following:
• Drive letter: Y
• Volume label: UDPHash
3. Create a hidden file named as $$$arcserve.y.
4. To create default deduplication data store, go back to the Appliance Configuration wizard.
• When creating an Instant VM to a local Hyper-V server, the job fails if the Arcserve Appliance 9000 Series built-in Sophos is not activated.
• Symptom
• When you create an instant VM to local Hyper-V server, the job fails and the following errors display in the UDP activity log:
• Failed to read disk data from the backup destination.

• Instant VM job has detected the network communication or data read failure.
• Solution 1
• Activate Sophos. For more information, see Activating Sophos on the Arcserve Appliance 9000 Series.
• Solution 2
• Follow these steps:
1. Open Services.
2. Stop service Sophos System Protection Service.
3. Change the startup type of service for Sophos System Protection Service to Manual.
4. Note: After you activate Sophos on Appliance, manually start this service and change the startup type back to Automatic.