On 24/01/15 17:56, Marc Muehlfeld wrote:> The second way, and the one I would go, is > - shutdown Samba on DC1 > - copy all databases and SysVol content to the new host, > into the folders, where your new OS expect them > - disconnect the old machine from the network > - start Samba on the new host > It's very important that the old host is never connected to the network > any more or you will mess up your AD! > > I don't know what Samba version Gentoo and Ubuntu are shipping. But I > suggest that the OS on the new host, doesn't have an older version.Hello Marc Thanks for your reply. Yes, that's what I thought... belt and braces copy all databases and sysvol content using the backup script and restore instructions on the wiki. Yes, I was going to literally turn OFF both the old 'real' DC1 and 'real' DC2 just in case the 'virtual' DC1 went fooey and interfered with DC2. I am also going to turn off all non-essential computers on the network so that Windows DC and login can be tested without any horrific consequences. What do the others think? Am I being paranoid or wise? :) Paul Littlefield PS: now I think about it, I amy as well 'virtualise' DC2 as well AS IS, then use that (with the same IP addresses, hostnames, etc. to test the new 'virtual' DC1 for replication, etc. Thoughts?
Am 24.01.2015 um 19:45 schrieb Paul Littlefield:> Yes, that's what I thought... belt and braces copy all databases and > sysvol content using the backup script and restore instructions on the > wiki.If you have shutdown Samba on the DC, you don't need the backup-script. This script just create hot-backups, so you don't have to shutdown a DC for backup. If Samba is already stopped, then it's save to backup/copy the files.> Yes, I was going to literally turn OFF both the old 'real' DC1 and > 'real' DC2 just in case the 'virtual' DC1 went fooey and interfered with > DC2.If you have brought the new DC1 together with DC2 and the replication has started, you can't go back to the old DC1, if something doesn't work. Then you will get an inconsistent AD.> I am also going to turn off all non-essential computers on the network > so that Windows DC and login can be tested without any horrific > consequences.If you want to test this before, then do this in a separated installation and not in production. Then you're save from any horrific consequences. Not if you do this in with other production DCs/workstations. Even if you've turned most computers off, you don't know what the others change in the meantime in AD (eg. machine password changes). If you roll-back, you can run into problems. Use a test installation and don't test in production. Regards, Marc
On 24/01/15 19:38, Marc Muehlfeld wrote:> If you want to test this before, then do this in a separated > installation and not in production. Then you're save from any horrific > consequences. Not if you do this in with other production > DCs/workstations. Even if you've turned most computers off, you don't > know what the others change in the meantime in AD (eg. machine password > changes). If you roll-back, you can run into problems. > > Use a test installation and don't test in production.Hello Marc Thanks for your reply. OK, I will take copies of real DC1 and DC2 to my VirtualBox at home... well away from the client's network. I will then fire up and check databases, DNS, Kerberos, etc. If they both talk to each other, and a dummy Windows PC can join the domain, am I OK to roll it out to the client's network? Are there any other strict checks I need to do? Regards, Paul Littlefield
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Or you try this: http://relax-and-recover.org/ With Rear it ist possible to do a P2V migration. Am 24.01.2015 um 19:45 schrieb Paul Littlefield:> On 24/01/15 17:56, Marc Muehlfeld wrote: >> The second way, and the one I would go, is - shutdown Samba on >> DC1 - copy all databases and SysVol content to the new host, into >> the folders, where your new OS expect them - disconnect the old >> machine from the network - start Samba on the new host It's very >> important that the old host is never connected to the network any >> more or you will mess up your AD! >> >> I don't know what Samba version Gentoo and Ubuntu are shipping. >> But I suggest that the OS on the new host, doesn't have an older >> version. > > > Hello Marc > > Thanks for your reply. > > Yes, that's what I thought... belt and braces copy all databases > and sysvol content using the backup script and restore instructions > on the wiki. > > Yes, I was going to literally turn OFF both the old 'real' DC1 and > 'real' DC2 just in case the 'virtual' DC1 went fooey and interfered > with DC2. > > I am also going to turn off all non-essential computers on the > network so that Windows DC and login can be tested without any > horrific consequences. > > What do the others think? Am I being paranoid or wise? > > :) > > Paul Littlefield > > PS: now I think about it, I amy as well 'virtualise' DC2 as well AS > IS, then use that (with the same IP addresses, hostnames, etc. to > test the new 'virtual' DC1 for replication, etc. > > Thoughts?- -- Stefan Kania Landweg 13 25693 St. Michaelisdonn Signieren jeder E-Mail hilft Spam zu reduzieren. Signieren Sie ihre E-Mail. Weiter Informationen unter http://www.gnupg.org Mein Schl?ssel liegt auf hkp://subkeys.pgp.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlTFMMIACgkQ2JOGcNAHDTbnvACbBBJbym8E5JLlA45H0DrkVi1d FT0An1u0BEUELbOWTMhinNeFP+U9hGeN =5YN4 -----END PGP SIGNATURE-----
On 25/01/15 18:07, Stefan Kania wrote:> Or you try this: > http://relax-and-recover.org/ > With Rear it ist possible to do a P2V migration.Hello Stefan Oh wow, amazing piece of software... the YouTube video sold it to me. REAR could be very useful. List - I'll take all your comments under my wing, and return with a full report. Many thanks. :) Paul Littlefield
Hi Stefan, On 01/25/2015 07:07 PM, Stefan Kania wrote:> Or you try this: > http://relax-and-recover.org/ > With Rear it ist possible to do a P2V migration.Thanks for sharing this, I did not know about this!