Damian Jenkin · Aug 16, 2022

Whole Installation Partition Move, Potential Issues!?


  We have an IRIS installation on one drive "D"; the drive is a partition that is limited to 2TB in size; we want to move the entire D: contents to a larger partition-type not limited to 2TB.

The IRIS install is on D: as are all of the Databases the instance uses.

Are there any concerns or issues that should be considered or are not so obvious with doing this?

i.e. IRIS and all processes doing disk access to D: need be shutdown first (and a full-backup taken, all journals up to date for mirrors etc).

A new partition of E: created as say 3TB.

Robocopy (for example) the entirity of D: to E:, then relabel D: and O: (old), and E: becomes "D:", bring IRIS back up etc as usual.

...all is well?! all should be, just posing the question in case anyone has encountered anything odd or unexpected doing something similar... better to be safe than spending hours and hours rebuilding a server from a backup off a slow network-path... :P

Thanks in advance for any tips/tricks/catches/pointers.


  - Damian.

Product version: IRIS 2020.3
$ZV: 2020.3 (Build 304U)
0 156
Discussion (2)0
Log in or sign up to continue


I have done a similar thing in the past with Cache. As long as at the end of the process the IRIS will be at a new partition with the same letter, all the keys in registry that were created during the install, will still be valid.
The risk with the procedure you mentioned is minimal, and all should work  as expectged.

Thanks Yaron for your reply.

We've done the upgrade to a number of partitions now and all worked fine.

Only thing to make sure that was found was to reboot the server that's expecting the D:, after the rebuild, for ISCAgent / connections when still active.