How would it be more correct to update and space out an outdated server (2003+SQL+1C)?

O

other_letter2015-08-20 11:49:26

System administration

other_letter, 2015-08-20 11:49:26

There is a server in the park that you want to rebuild.
2003+SQL2008+1C 8.2 and everything in general. Windows services are transferred easily and clearly, there are no questions here.
And here's how to do it in general, I ask for advice or recipes.
The server is very important for work and therefore, alas, nothing worthwhile can be done with it.
A comprehensive approach is needed.
As I see it:
1. We put SQL server somewhere else. Fresh.
2. We transfer it using the same means of the base.
3. 1C redirect to the fact that now the bases are in a different place. Well, more precisely on another server. It's complicated?
4. If everything is OK, you will have to transfer 1C. And here it is not easy, since it will be necessary to reconfigure all clients. Well, the benefit of everything, it seems, can be done massively and remotely through the registry.
As a pre-question:
Has anyone tried similar servers to catch up to 2012 in update mode?

Reply

Answer the question

In order to leave comments, you need to log in

4 answer(s)

S

Sergey Kovalev, 2015-08-20
@other_letter

1C server can work with several SQL servers at the same time.
1. That's right.
2. Transfer the base either by means of SQL through uploading to .bak, or through 1C through uploading through .dt. It is not worth doing direct copying of databases from one SQL server to another using SQL tools.
3. Register a new infobase in 1C Enterprise indicating a new SQL server.
4. Easy management of 1C database lists for the final solution of issues related to prescribing lists to users.

M

Max, 2015-08-20
@MaxDukov

well, the process. Yes, the idea is correct.
one weekend you are pulling the database, do not forget to test the transition.
In the next - 1C.
here the person describes the solution to this problem.

A

Andrey Ermachenok, 2015-08-20
@eapeap

It makes sense to first conduct an "Administrative installation" of 1C with clients. Register all the bases in it. Then the version of the platform will be updated "by itself" in the future for clients, databases can be added and moved by simply editing a text file.
Search the Internet for the course "Administering 1C from scratch (2014)" - it helped me a lot.

D

DastiX, 2015-08-20
@DastiX

Let's say you have two servers, one current, one empty.
1. Raise on an empty MsServer 2012 + MsSql 2014 (enter into the domain, update and trawl)
1.a Share sql, set up access rights
2. Copy the databases to the new server (in any way convenient for you)
2.a Check the availability of the databases from MsSqlStudio
3. Kill the old server, raise a new one (enter into the domain, update and trawl)
4. Raise 1C on it (do not forget that you will have to reactivate all the licenses that you had, so stock up on pin codes, but what if usb -keys, then it doesn't matter)
5. Set up 1C for a new server.
If you name the server with 1C in the same way as it was named, then there will be no need to change anything for clients.
I did it for Saturday-Sunday, but I also had a new raid and so on.