DFS hosting server migration
- Login to destination server and go to G:\Applications\CERN\AdminTools\DFS\Migrations
- run
rbcpy.cmd \\source_server\share_name dest_disk:\dest_dir_case_sens logfile.txt
- repeat previous action
- check log with notepad logfile.txt to see if new files were copied and look for errors
- if needed, fix access denied errors with
\Applications\CERN\AdminTools\DFS\Migrations\Tools\SubInacl.exe
tool. First revoke builtin\admistrator and then grant, e.g.: SubInacl.exe /subdirectories f:\Departments\Safety\Groups\RP\Instrumentation_Logistics\Back_Up\Backup_DPerrin_31-8-2006\C51\* /revoke=builtin\administrators
- check number of connected users, their idle time, open files, open mode and types of files and eventually wait and go to step 2
- share the folder using naming convention (e.g. D-IT-G-IS$) and set sharing permission to full control for everyone (we rely on filesystem ACL)
- open DFS console: run
dfsgui.msc
, add New Target, uncheck "Add this target to the replication set", specify path to the shared folder
- in DFS console, remove old target
- unshare the folder on the source server
- edit the page and detail of the move (source, dest, time)
--
JurajSucik - 07 Mar 2007
DFS old hosting server migration
- For each folder on a given machine
- make sure new copy is shared
- Stop the share on the old machine - from this moment people cannot access files)
- Make a final copy (it will take a while)
- Make sure that you know local administrator password on the old machine
- Disjoin the domain with the old machine and reboot it
- Logon with local administrator account and change its name to something like oldname-old
- Go to Nick and ask to
- Rename old machine to oldname-old in the LanDB
- Add a CNAME alias to new machine which should be called like oldname
- Wait until DNS changes propagate
- Check if the DFS folders are accessible
- As a final clean-up - can be done later
- Update appropriate web page with the information on when and where folder was moved
- Change DFS links to use new machine name instead of oldname, which is now in fact an alias
- remove old records from wins
- apply http://support.microsoft.com/kb/281308 on new server (to support aliases for SMB)
- put new server to the set in the webreq
SRV5_DIV, SRV1_HOME, SRV2_HOME were migrated on 3/14/2007 1800-2000.
SRV4_HOME was migrated on 3/21/2007 0700-0830.
--
JurajSucik - 14 Mar 2007