If you want to continue using the RDX Cleaner in Arcserve UDP V6, download the new RDXCleaner and RDXForceCleaner from the following URLs:Īrcserve UDP Agent (Linux) ConsiderationsĪrcserve UDP Agent (Linux) supports only those kernels that are officially published by Linux distributors. RDXCleaner and RDXForceCleaner are not automatically upgraded from Arcserve UDP V5.To migrate the database and upgrade from Arcserve UDP 5.0 supported versions where the backend database is SQL Server 2005, see How to Migrate the Backend Database and Upgrade from Arcserve UDP 5.0 with SQL 2005 to Arcserve UDP 6.0 in Solutions Guide v6.0. Arcserve UDP Version 6.0 does not support SQL Server 2005 as the backend database.If you want to perform BMR from an older version of RPS and deduplication data store, you have to use the older version of the BMR ISO. If you upgrade to a newer version or update of Arcserve UDP, you must re-create the BMR ISO using the proper Windows AIK or ADK level to include support for latest features and bug fixes.To avoid simultaneous running of more than one instance of the AEGR utility, you can manually uninstall the standalone version and then upgrade to Arcserve UDP Version 6.0. Arcserve UDP does not support simultaneous running of more than one instance of the AEGR utility. For the agent machine, install any version except Version 5.0 of the standalone AEGR utility. If the Arcserve UDP Version 6.0 setup detects Arcserve UDP Exchange Granular Restore (AEGR) utility standalone Version 5.0 installed, the setup will remove the existing version and install the current version of the AEGR utility during the upgrade.We recommend to reinstall the BLI driver after the OS is upgraded to Windows 10. All the Incremental Backup gets converted to Full or Verify Backup. When you upgrade the OS, the registry BLI upper filter of volume class gets deleted and the BLI driver cannot monitor the volumes. After you upgrade a node from Windows 7, Windows 8, or Windows 8.1 to Windows 10, perform a Verify Backup.For more details on how to define the keys, see Define a Limit to the Quantity of Concurrent Backups in the Solutions Guide. If the concurrent job count is required, provide new values for the new keys (VMwareMaxJobNum and HyperVMaxJobNum) in Arcserve UDP Version 6.0. If you configured VMMaxJobNum in Arcserve UDP Version 5.0 and you upgrade to Arcserve UDP Version 6.0, the VMMaxJobNum configuration will be lost after the upgrade. In Arcserve UDP Version 6.0, the registry key is separated to two keys (VMwareMaxJobNum and HyperVMaxJobNum) to control concurrent backup jobs for Hyper-V VM and VMware VM respectively.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |