- Jun 30, 2004
- 16,154
- 1,757
- 126
I've got RAPID working while I troubleshoot a WHS server backup difficulty with the subject client system.
Regardless the backup strategy, I'm wondering what happens when you restore an image backup from the Sammy SSD to an HDD.
There are two Magician services or processes which run under RAPID -- very tiny use of RAM. Magician itself takes some 17MB of RAM, and RAPID works whether or not the Magician program is running at startup or any other time.
I would expect that the services or processes would merely stop -- possibly with an error reported in event logs, since the device or SSD might not be there if replaced by an HDD.
I recall that there were definitely some adjustments to make once the initial HDD had been cloned to the SSD. So now I'm wondering what happens in reverse.
Regardless the backup strategy, I'm wondering what happens when you restore an image backup from the Sammy SSD to an HDD.
There are two Magician services or processes which run under RAPID -- very tiny use of RAM. Magician itself takes some 17MB of RAM, and RAPID works whether or not the Magician program is running at startup or any other time.
I would expect that the services or processes would merely stop -- possibly with an error reported in event logs, since the device or SSD might not be there if replaced by an HDD.
I recall that there were definitely some adjustments to make once the initial HDD had been cloned to the SSD. So now I'm wondering what happens in reverse.
Facebook
Twitter