How to properly organize the relocation of IT Infrastructure?

Question

System administration

Good afternoon, in 3 months we have to organize the relocation of the IT infrastructure to another building, how best to organize it, who has come across it, so far I see the following action plan
: 2 weeks before moving) at least by gender, request 15,000 rubles for contingencies, tools if required, patch cords, etc.
2-Inform the current provider about the possibility of connecting their communication line.
3-on the day of the move (on Friday), organize the relocation of servers to a new location, contact the provider in parallel to connect the Internet and, in fact, with a margin on the weekend, check that everything works.
4-on business days, put client cars and connect to the network.
5-in a month, another, in the absence of SCs, hire an installation team to lay SCs with mounting sockets.
Well, it seems like something like this, did you paint everything correctly?

Answer 1

1. Designing to lay down at the stage when the site has just been selected.
2. SCS construction - during, immediately after, repair. (otherwise installers will take x10 of the price for cramped conditions and cover everything with dust from perforators
) this is the second most necessary resource after power supply
4. Directly connecting the WAN line is carried out during the construction of the SCS
5. Next, plan the strategy for the transfer itself
6. Ideally, organize a VPN tunnel between sites and generally without problems and, most importantly, the fuss / shutdown of work sequentially, in a week / two, transport each department/office

Answer 2

Everything is very much tied to what kind of infra you are transferring and whether there is excess capacity.
Infra can be intolerant of downtime, can be tolerant. Power may or may not exist. Let's consider all 4 options:
0. Create an infra scheme in a new building at all OSI levels. where are the sockets, where are the patches, where is the server room, where and how is the SCS, what vlans, what routes, etc
1. Network setup:
1.1. Regardless of the options: laying SCS in advance, mounting patch panels
If there is extra network equipment:
1.2. Mount routers and switches, set up a local network at the 2nd and 3rd levels.
If it's not there:
1.3. You set up the current switches in advance, if the current infra differs from the new one and is kept, for example, on crutches (as usual) - an excellent reason to get rid of them. You set it up, if there is no way in the old office in a new way, then they removed the dump - knocked it down - set it up as you want - removed the dump - returned the previous settings. When moving, it will be enough to fill in the dump.
1.4. Make the Internet in advance, so that by the time the servers in the old building are turned off, it will already work in the new one.
2. Setting up Servers:
2.1. Case one: downtime is prohibited, there is excess capacity:
We transfer free servers, raise replicas, move traffic there, kill old ones, transfer
2.2. Case two: Downtime is prohibited, there are no excess capacities:
Ask for excess capacity: s You can rent several VPSs for the duration of the move, pick up replicas there, and return later. Well, or move at the moments of minimal activity, at night
2.3. Case three: Internet, adshka, telephony services:
Without any problems we transfer to a new building, cut it down - moved it - turned it on. The problem is if the move is long: you need to leave the capacity for services in the old office too. If they are not there: move at once, all
3. We drag client cars for fuck's sake, these are client cars

Answer 3

Many useful things have already been written, I will only add - never hope that others will do everything on time! Connect the Internet and check in advance. If you have money, buy and put everything you can in a new place (router, switches, etc.) in order to set up, connect and test as much as possible in advance. Do not forget to include in the moving plan that you are also a person, and you need to eat and rest, it may be worth dividing the move into several days, because. tired, you can screw up, and then again, because tired - look for an error for a long time.

Answer 4

1-Inspection of the area, to see if there is an SCS, in the absence of SCS, already lay the cables (2 weeks before the move) at least on the floor

No, don't do that.
Lay the cables right away, while there is still nothing in the room, no one interferes with laying normal boxes, making holes in the walls (this is dirt, plaster, dust).
Cables can be laid with a margin. The boxes should be with a margin and access, and think over if something happens, how to report more in them, but this is an extreme case.
For a server room, it must be thought out in advance where everything will stand. Cooling system, switching cabinets / conventional cabinets / how many kilowatts you need to drag there.
Internet to spend there first. Set up vpn between both points, and network visibility. This will allow you to slowly transfer client machines at least one at a time already at normal times.
At the same time it will be possible to check the quality of the provider. If there are several providers, it is better to knock out a connection to several and check live how everything works, leave the two best for the main line and backup.