1C server 8.2 + MsSql 2008 + BackUp

There are a lot of similar articles, but I first of all wrote this for myself, dwelling on notes, which describe possible problems. I hope the article will be useful to others.
1. Install the 1C platform
2. Install MS SQL server 2008. When installing, set the database user. (Which is sa).

After installation, open the administration panel of the 1C servers of the enterprise and see that it is empty.
We need to create a server: Open console root-> Central 1C: Enterprise 8.2 servers. We click on it with the right mouse button and select the new item. In the drop-down menu, select the Central server 1C Enterprise 8.2. A window with 4 fields will open before us:
Protocol - the protocol by which data will be transmitted
Name - the name of the computer on the network where the server is located
IP port port on which the server is available
Description - description . not necessary.

Note:
If the 1C platform was installed on a computer, and then the computer was renamed, then you will not be able to reach it, because the 1C platform is very smart and writes to certain files when you install the computer name, but then, when the computer name changes, their platform does not change rewrite. These files are needed for the operation of the RAGENT 1C service (it can be found in the running services through the windows server administration panel). All of this suggests that in order to rename these files, you must stop the RAGENT service. The files themselves are in the following locations:
C: \ Program Files (x86) \ 1cv82 \ srvinfo \ srvribrg
C: \ Program Files (x86) \ 1cv82 \ srvinfo \ reg_1541 \ 1CV8Reg
We open these files with a notebook and we rule the past the name of the car with the present handles. Save and run RAGENT.
')
Go back to the setting:
After the window with fields is filled, we press the OK button and if everything is done correctly, then we will have a server by the name of the machine on which it is located.

So. The server is running and now we need to create a database on the MYSQL server and associate it with North 1C. There are several ways, here I will describe the easiest:
On the enterprise 1C server, open our newly created server by clicking on the + next to the server name and click on the “INFORMATION DATABASES” item with the right mouse button, select New-> Information Base
Before us opens a window in which there will be the following fields:

The name is the name of our database on the server 1C (As a rule, many people write it the same as in the database field, so as not to be confused)
Description - description
Secure connection is disabled by default. you can turn on but then the server load will increase
Database server - if the server is on the same server, then we specify (local) exactly in parentheses, if not on this server, then we specify the server ip
DBMS Type -Select MS SQL Type
Database - database name on MS SQL server. If there is no base then you can tick one of the checkboxes and it will be created
Database server user -We specify either the user of which is created during installation, or we create a separate user in MS SQL, assign rights to it and register it here.
Database server user password - password
Allow the issuance of licenses by the server 1C Enterprise -We select yes
Country -Select a country
Dates offset - set to 0
Checkbox "Create a database in the case of lack of" is the same checkbox to create a database if it is not
Checkbox "Set blocking routine tasks" -not tick

We click OK and see that the servers are configured and we have an information base under the name we gave her in the tab “Information databases”.

Then it remains to configure BackUp. What I’m not going to talk about is information and so is the sea. You can for example look in this wonderful article .

To build Backup we need to open Microsoft SQL MANAGEMENT STUDIO.
Enter the login and connect to the server.
Before us is the administrative console. In Object explorer, open the Management tab and see Maintance plans in it . Here we will create the necessary BackUP. As usual, right click on the Maintance plans-> new maintance plan . The subplan tab will appear in the main window, and another ToolBox window will appear under the Object Explorer in which the Maintance Plans Tasks is embedded. In it we will select Back Up DataBase Task by clicking on it 2 times. It will be transferred to the main window. On it we click 2 times and in front of us a window appears again with fields where we can choose which Back Up to do, which BackUp database to use, and where to save it. At the end of the settings you need to click Ok.

Note:
Keeping Back Up in any network folder (by the way, you will have to register with pens, because the directory selection window sees only local resources), monitor access rights, and at the same time, track what kind of authentication you have on MySql server, because if authentication is not based on user accounts Windows, and the internal DBMS user, and if at the same time the AD server is raised, then BackUp will give an error when trying to execute, because it will do it on behalf of the internal DBMS user and AD will not let it go anywhere except locale computer information.

After you have configured the path, the base and the type of BackUp you need to configure the schedule. To do this, in the main window above the Task you created there is a SubPlan sign. At the end of the plate (on the right) there is a calendar icon. Clicking on it will take you to the schedule setting. By marking the checkboxes of the days and setting the time you set up the schedule. Clicking 2 times on the field called SubPlan you can change the name of Task-a. After setting all go to File-> Save All . After saving to Maintance plans, Task will appear with your name that you gave to BackUp.

At the end of the setting, it is imperative to check the Work. To do this, right-click on the created Task and execute Exicute.

Note:
If Exicute is executed with an error, read the errors that Studio will give you, and first check if you are running the SQL server agent . That he is engaged in the implementation of tasks and the Exicute function refers to him for the implementation of tasks. If it is not running, the attempt to perform will fail. To see if the agent is working or not in Studio in the Object Explorer, go to the SQL Server Agent tab. If the red circle with a cross is on the icon, the agent is stopped. You can start it by right-clicking on it and selecting the START option in the context menu.