Before starting the migration stop all activity on the appliance:
Deployments | Remote sites
Tag the RSA's and choose Cancel Sync from the Choose Action pull down menu
Library | Overview | Driver Feed
Select on Status and make sure no package shows the status Installing driver feed package.
Library | User States
Devices | Network Scans
Settings | Package Management
Tag the tasks and Select Cancel all Import and/or Cancel All Import Jobs
Settings | Package Management | Off-Board Package Transfer
Untag Enable Backup (and make sure none is running of course)
Settings | Appliance Maintenance
Also check that no Recaching, Deletion of Drivers or other activities listed on this page are taking place.
Progress | Automated Deployments / Manual Deployments
Settings | Appliance Maintenance | Reboot
Settings | Control Panel | Data Storage
Follow the procedure there as described in the manual
It very well might be that after performing above steps the migration succeeds this time.
If it fails however please collect the server logs directly after the migration was interupted and contact Support so they can analyze these:
Support | Download support logs
Known scenario:
The Storage_configure_sync_error log contains messages similair to these:
rsync: recv_generator: failed to stat "/kbox/datastore/external/tmp/1653026847/SQL 2008 R2 ENT x86 & x64\en_sql_server_2008_r2_enterprise_x86_x64_ia64_dvd_520517.iso": Input/output error (5)
rsync: recv_generator: failed to stat
...
"/kbox/datastore/external/tmp/585999374/SQL 2008 R2 Express with Management Tools\x86" failed: Input/output error (5)
rsync error: some files could not be transferred (code 23) at main.c(977) [sender=2.6.9]
In this scenario a L3 Agent can remove the contents mentioned in the log.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center