Please comment on the portability aspects of moving a Pool from WHS 2011 to Windows Server 2012 Essentials and back. I'm posting this question here rather than in a support contact because the general information and guidance can also apply to what other users might want to do. Basically, for testing or trial purposes, what steps and precautions should be followed to move a full pool of pass-through disks from a VM with one OS to another VM with a different OS and back again without risking data loss on the pool? I think this would also apply to moving the pool intact between different computers or motherboards or upgrading then reverting OSs.
Scenario: As you know from my previous support tickets (640360 & 8209559), I've been having trouble with freezes of my WHS2011 VM (Hyper-V) when the DrivePool service is manually enabled (even running minimal msconfig settings and without the Scanner service). This occurred with the latest v 1.3 and also after I upgraded to the latest release of v 2. Usually the hang will occur at some point during the measuring stage; for some boots, though, the DrivePool service enters a steady state and presumably executes its management tasks okay. I know that I can operate this way indefinitely without data risk if I keep in mind what Alex told me that I've pasted into the end of this post for the benefit of all.
But after exhausting much of my hardware and software troubleshooting resources, I'd like to move the full single pool of 7 HDDs (16.7TB) to a VM with Windows Server 2012 Essentials to see if the problem disappears. If it still exists, the root of the problem will probably by the host hardware or software. However, I'm not prepared to commit to that server upgrade change from WHS2011 yet, so I want to be able to reattach the hard drives to the WHS2011 VM. Naturally, I don't want WS2012E to massage the Client Computer Backups folder on the pool and declare the backups corrupt. (The current native WS2012E Client Computer Backups folder is with its other default server folders on the system C: drive now, so I'm thinking that WS2012E won't automatically try to connect to the similar folder on the DrivePool pool. Still, . . . . . .) Here's what I think I need to do. Please correct me where wrong and let me know what pitfalls are in store:
Steps:
1. Install DrivePool 2 into WS2012E VM and shut down.
2. In Windows Explorer, rename (slightly) Client Computer Backups folder in the DrivePool drive's \ServerFolders in the WHS2011 VM (will cause a pre-defined server folder missing error and stop the Windows Server Client Computer Backup Service) and shut down. (?? - Not sure this is necessary as a safeguard to keep WS2012E from playing with it after the pool is moved.)
3. Remove the physical hard disks from the WHS2011 VM using Hyper-V Manager.
4. Add the physical hard disks to the WS2012E VM.
5. Start the WS2012E VM. DrivePool should find the full pool intact.
6. Run the WSS Troubleshooter Reset NTSF Permissions on the Pool and Restore DrivePool Shares. (?? - Not sure this is necessary unless the intent is to keep the pool on the new server, particularly if the plan is to return to the old server.)
To return the pool to the previous server:
1. Shut down both VMs.
2. Remove the physical hard disks from the WS2012E VM.
3. Add the physical hard disks to the WHS2011 VM.
4. Using Windows Explorer, reverse renaming of Client Computer Backups folder in Step 2 of first move above.
5. Run WSS Troubleshooter Reset NTSF Permissions on the Pool if it was done for Step 6 above.
Using DrivePool without the service: In reference to my statement above that the DrivePool service doesn't have to be run in order to use DrivePool (provided you have sufficient free space on all pool disks), I thought I'd include this clarification that Alex provided me in a support contact concerning data risk --
Q. "What are the risks for regular use (of DrivePool with the DrivePool.Service.exe service disabled) until the service is re-enabled?":
A. •Risks to data integrity:
◦If you have real-time duplication enabled: NONE. ◦Background (or nightly) duplication will not function.
•No pool management.
◦You will not be able to add / remove disks from the pool or perform any kind of pool management.
•Risks to running out of disk space:
◦There is a complicated mathematical model that we use to re-balance your pool to provide maximum available disk space for duplicated files. This will not function with the service disabled.
A simple example of this (but it can get much more complicated):
◾You add a 100 GB disk (#1) to the pool. ◾You fill that disk up to 90 GB. ◾Then you decide to add another 100 GB disk (#2) to the pool. ◾Your pool is now 200 GB in size with 90 GB used.
BUT, you can only copy 10 GB of new duplicated data onto it because disk #1 only has 10 GB free.
◦So if the service is not running, you risk running out of disk space.
In short, the service is not involved in reading or writing data to or from the pool. But maintenance and administrative tasks will not function.
Question
Mick Mickle
Christopher / Alex,
Please comment on the portability aspects of moving a Pool from WHS 2011 to Windows Server 2012 Essentials and back. I'm posting this question here rather than in a support contact because the general information and guidance can also apply to what other users might want to do. Basically, for testing or trial purposes, what steps and precautions should be followed to move a full pool of pass-through disks from a VM with one OS to another VM with a different OS and back again without risking data loss on the pool? I think this would also apply to moving the pool intact between different computers or motherboards or upgrading then reverting OSs.
Scenario: As you know from my previous support tickets (640360 & 8209559), I've been having trouble with freezes of my WHS2011 VM (Hyper-V) when the DrivePool service is manually enabled (even running minimal msconfig settings and without the Scanner service). This occurred with the latest v 1.3 and also after I upgraded to the latest release of v 2. Usually the hang will occur at some point during the measuring stage; for some boots, though, the DrivePool service enters a steady state and presumably executes its management tasks okay. I know that I can operate this way indefinitely without data risk if I keep in mind what Alex told me that I've pasted into the end of this post for the benefit of all.
But after exhausting much of my hardware and software troubleshooting resources, I'd like to move the full single pool of 7 HDDs (16.7TB) to a VM with Windows Server 2012 Essentials to see if the problem disappears. If it still exists, the root of the problem will probably by the host hardware or software. However, I'm not prepared to commit to that server upgrade change from WHS2011 yet, so I want to be able to reattach the hard drives to the WHS2011 VM. Naturally, I don't want WS2012E to massage the Client Computer Backups folder on the pool and declare the backups corrupt. (The current native WS2012E Client Computer Backups folder is with its other default server folders on the system C: drive now, so I'm thinking that WS2012E won't automatically try to connect to the similar folder on the DrivePool pool. Still, . . . . . .) Here's what I think I need to do. Please correct me where wrong and let me know what pitfalls are in store:
Steps:
1. Install DrivePool 2 into WS2012E VM and shut down.
2. In Windows Explorer, rename (slightly) Client Computer Backups folder in the DrivePool drive's \ServerFolders in the WHS2011 VM (will cause a pre-defined server folder missing error and stop the Windows Server Client Computer Backup Service) and shut down. (?? - Not sure this is necessary as a safeguard to keep WS2012E from playing with it after the pool is moved.)
3. Remove the physical hard disks from the WHS2011 VM using Hyper-V Manager.
4. Add the physical hard disks to the WS2012E VM.
5. Start the WS2012E VM. DrivePool should find the full pool intact.
6. Run the WSS Troubleshooter Reset NTSF Permissions on the Pool and Restore DrivePool Shares. (?? - Not sure this is necessary unless the intent is to keep the pool on the new server, particularly if the plan is to return to the old server.)
To return the pool to the previous server:
1. Shut down both VMs.
2. Remove the physical hard disks from the WS2012E VM.
3. Add the physical hard disks to the WHS2011 VM.
4. Using Windows Explorer, reverse renaming of Client Computer Backups folder in Step 2 of first move above.
5. Run WSS Troubleshooter Reset NTSF Permissions on the Pool if it was done for Step 6 above.
6. You should be back to where you started.
__________________________________________________________
Using DrivePool without the service: In reference to my statement above that the DrivePool service doesn't have to be run in order to use DrivePool (provided you have sufficient free space on all pool disks), I thought I'd include this clarification that Alex provided me in a support contact concerning data risk --
Q. "What are the risks for regular use (of DrivePool with the DrivePool.Service.exe service disabled) until the service is re-enabled?":
A. •Risks to data integrity:
◦If you have real-time duplication enabled: NONE.
◦Background (or nightly) duplication will not function.
•No pool management.
◦You will not be able to add / remove disks from the pool or perform any kind of pool management.
•Risks to running out of disk space:
◦There is a complicated mathematical model that we use to re-balance your pool to provide maximum available disk space for duplicated files. This will not function with the service disabled.
A simple example of this (but it can get much more complicated):
◾You add a 100 GB disk (#1) to the pool.
◾You fill that disk up to 90 GB.
◾Then you decide to add another 100 GB disk (#2) to the pool.
◾Your pool is now 200 GB in size with 90 GB used.
BUT, you can only copy 10 GB of new duplicated data onto it because disk #1 only has 10 GB free.
◦So if the service is not running, you risk running out of disk space.
In short, the service is not involved in reading or writing data to or from the pool. But maintenance and administrative tasks will not function.
Link to comment
Share on other sites
20 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.