Yandex.Cloud
  • Services
  • Why Yandex.Cloud
  • Pricing
  • Documentation
  • Contact us
Get started
Use cases
  • Web service
    • All use cases
    • Static website in Object Storage
    • Website on LAMP or LEMP stack
    • Fault-tolerant website with load balancing from Yandex Network Load Balancer
    • Fault-tolerant website using DNS load balancing
    • Joomla-based website with PostgreSQL
    • WordPress website
    • WordPress website on a MySQL database
    • 1C-Bitrix website
  • Online stores
    • All use cases
    • 1C-Bitrix online store
    • Opencart online store
  • Data archive
    • All use cases
    • Single-node file server
    • Configuring an SFTP server on Centos 7
    • Backup to Object Storage via Acronis Backup
    • Backup to Object Storage via CloudBerry Desktop Backup
    • Backup to Object Storage via Duplicati
    • Backup to Object Storage via Bacula
    • Digitizing archives in Yandex Vision
  • Test environment
    • All use cases
    • Testing applications with GitLab
    • Creating test VMs using GitLab CI
    • High-performance computing on preemptible VMs
  • Infrastructure management
    • All use cases
    • Getting started with Terraform
    • Uploading Terraform states to Object Storage
    • Getting started with Packer
    • VM images building automation using Jenkins
    • Continuous deployment of containerized applications using GitLab
    • Creating a cluster of 1C:Enterprise Linux servers with a Managed Service for PostgreSQL cluster
    • Creating a cluster of 1C:Enterprise Windows servers with MS SQL Server
    • Migrating to Yandex.Cloud using Hystax Acura
    • Emergency recovery in Yandex.Cloud using Hystax Acura
    • Configuring a fault-tolerant architecture in Yandex.Cloud
  • Windows in Yandex.Cloud
    • All use cases
    • Deploying Active Directory
    • Deploying Microsoft Exchange
    • Deploying Remote Desktop Services
    • Deploying an Always On availability group
    • Deploying an Always On availability group with an internal network load balancer
  • Network routing
    • All use cases
    • Routing through a NAT instance
    • Creating a VPN tunnel
    • Installing a Cisco CSR1000v virtual router
    • Installing a Mikrotik CHR virtual router
    • Creating a VPN connection using OpenVPN
  • Data visualization and analytics
    • All use cases
    • Visualizing data from a CSV file
    • Visualizing data from a ClickHouse database
    • Visualizing data from Yandex.Metrica
    • Visualizing data from Yandex.Metrica Logs API
    • Publishing a chart with a map from a CSV file to DataLens Public
    • Visualizing data from AppMetrica
    • Visualizing geodata from a CSV file
  • Internet of things
    • Use cases for the internet of things
    • Status monitoring of geographically distributed devices
    • Monitoring sensor readings and event notifications
  1. Infrastructure management
  2. Creating a cluster of 1C:Enterprise Linux servers with a Managed Service for PostgreSQL cluster

Creating a cluster of 1C:Enterprise Linux servers with Managed Service for PostgreSQL

  • Before you start
    • Required paid resources
  • Prepare the infrastructure
  • Create a VM for the 1C:Enterprise server
  • Create a VM for the license server
  • Create a cluster Managed Service for PostgreSQL
  • Set up a Samba server
  • Install the 1C:Enterprise server
  • Set up a Samba server for the license server
  • Install the 1C:Enterprise server for the license server
  • Set up a server cluster
  • Set up the infobase
  • Connect to the infobase
  • Delete the created resources

Yandex.Cloud lets you create PostgreSQL clusters optimized for 1C:Enterprise. To configure the use of 1C:Enterprise, you need to create a working server, a license server, and a Managed Service for PostgreSQL cluster. For 1C servers to run correctly, you should disable security services on them. Therefore the cluster will be accessed via an encrypted OpenVPN server connection, while the 1C servers will have no access to the internet. The 1C servers will be running CentOS 8. The 1C cluster will be configured using the Windows administration console.

Note

To use 1C:Enterprise, you need a license. For more information about licenses and their installation, see the 1C:Enterprise website.

To configure 1C:Enterprise servers:

  1. Before you start.
  2. Prepare the infrastructure.
  3. Create a VM for the 1C:Enterprise server.
  4. Create a VM for the license server.
  5. Create a Managed Service for PostgreSQL cluster.
  6. Set up a Samba server.
  7. Install the 1C:Enterprise server.
  8. Set up a Samba server for the license server.
  9. Install the 1C:Enterprise server for the license server.
  10. Set up a server cluster.
  11. Set up an infobase.
  12. Connect to the infobase.

If you no longer need the created resources, delete them.

Before you start

Before deploying the server, you need to sign up for Yandex.Cloud and create a billing account:

  1. Go to the management console. Then log in to Yandex.Cloud or sign up if don't already have an account.
  2. On the billing page, make sure you linked a billing account, and it has the ACTIVE or TRIAL_ACTIVE status. If you don't have a billing account, create one.

If you have an active billing account, you can create or select a folder to run your VM in from the Yandex.Cloud page.

Learn more about clouds and folders.

Required paid resources

The infrastructure support cost for 1C-Enterprise in Yandex.Cloud includes:

  • A fee for the disks and continuously running VMs (see Yandex Compute Cloud pricing).
  • A fee for the continuously running Managed Service for PostgreSQL cluster (see pricing for Yandex Managed Service for PostgreSQL).
  • A fee for using a dynamic or static external IP address (see Yandex Virtual Private Cloud pricing).

Prepare the infrastructure

  1. Make sure that you install the 1C:Enterprise client to check the performance of the infobase and the 1C administration console to manage the server cluster on your computer.
  2. Make sure you have a VM running in your cloud with OpenVPN configured for a secure connection to the 1C servers.

Note

You can download the necessary distributions from the 1C:Enterprise website.

Create a VM for the 1C:Enterprise server

To create a VM:

  1. On the folder page in the management console, click Create resource and select Virtual machine.

  2. In the Name field, enter the VM name: server-1c.

  3. Select the availability zone to host the VM in.

  4. Under Images from Cloud Marketplace, click Select. Select a public CentOS 8 image.

  5. Under Computing resources:

    • Choose a platform.
    • Specify the number of vCPUs and amount of RAM:
      • vCPU: 4.
      • Guaranteed vCPU share: 100%.
      • RAM: 4 GB.
  6. In the Network settings section, select the network and subnet to connect the VM to. If you don't have a network or subnet, create them right on the VM creation page.

  7. In the Public address field, leave the value No address. The VM will be accessed via the OpenVPN server.

  8. Specify data required for accessing the VM:

    • Enter the username in the Login field.

    • In the SSH key field, paste the contents of the public key file.

      You need to create a key pair for the SSH connection yourself. Learn how to connect to VMs via SSH.

  9. Click Create VM.

Creating the VM may take several minutes.

Create a VM for the license server

Install the 1C:Enterprise license on a separate server. This way changes to the configuration of other servers won't affect the installed license.

To create a VM:

  1. On the folder page in the management console, click Create resource and select Virtual machine.

  2. In the Name field, enter the VM name: licensing-server-1c.

  3. Select the availability zone to host the VM in.

  4. Under Images from Cloud Marketplace, click Select. Select a public CentOS 8 image.

  5. Under Computing resources:

    • Choose a platform.
    • Specify the number of vCPUs and amount of RAM:
      • vCPU: 4.
      • Guaranteed vCPU share: 100%.
      • RAM: 4 GB.
  6. In the Network settings section, select the network and subnet to connect the VM to. The VM should be created in the same subnet as the OpenVPN server.

  7. In the Public address field, leave the value No address. The VM will be accessed via the OpenVPN server.

  8. Specify data required for accessing the VM:

    • Enter the username in the Login field.
    • In the SSH key field, paste the contents of the public key file.
  9. Click Create VM.

Creating the VM may take several minutes.

Create a cluster Managed Service for PostgreSQL

Yandex.Cloud lets you create Managed Service for PostgreSQL clusters optimized for 1C:Enterprise. Cluster settings may vary depending on your project requirements.

To create a Managed Service for PostgreSQL cluster optimized for 1C:

  1. On the folder page in the management console, click Create resource and select Managed Service for PostgreSQL cluster.

  2. In the Name field, enter the cluster name: 1c-pg.

  3. In the Version list, select 10-1c.

  4. Under Host class, select s2.small.

  5. Under Storage size, enter local-ssd and 100 GB.

  6. Under Database, enter:

    • DB name: 1c-database.
    • Username: user1.
    • Password: The password you'll use to access the database.
    • Network: The network where the cluster will reside.
    • Sorting locale: ru_RU.UTF-8.
    • Character set locale: ru_RU.UTF-8.
  7. Under Hosts, select different availability zones for your hosts to ensure their fault tolerance.

  8. Click Create cluster.

Creating the DB cluster may take several minutes.

Set up a Samba server

Connect to the server-1c VM via SSH.

  1. Install Samba, the necessary dependencies, and the nano text editor:

    $ sudo yum install nano samba samba-client samba-common, net-utils
    
  2. Disable IPv6 to avoid server conflicts. To do this, open the file /etc/sysctl.conf :

    $ sudo nano /etc/sysctl.conf
    
  3. Add the following lines to the file:

    net.ip6.conf.all.disable_ipv6 = 1
    net.ip6.conf.default.disable_ipv6 = 1
    
  4. Add the following lines to the file /etc/sysconfig/network:

    NETWORKING_IPv6=no
    HOSTNAME=server-1c
    
  5. Configure a shared directory. Open the Samba configuration file:

    $ sudo nano /etc/samba/smb.conf
    
  6. Make the file look like:

    [global]
            workgroup = WORKGROUP
            server string = Samba Server%v
            netbios name = centos
            security = user
            map to guest = bad user
            dns proxy = no
            passdb backend = tdbsam
            printing = cups
            printcap name = cups
            load printers = yes
            cups iptions = raw
            security = user
    
    [files]
            path = /1c-files
            browsable = yes
            writable = yes
            guest ok = yes
            read only = no
    
  7. Create a shared directory and grant access rights to it:

    $ sudo mkdir /1c-files
    $ sudo chmod -R 777 /1c-files
    
  8. Disable the firewall:

    $ sudo systemctl stop firewalld
    $ sudo systemctl disable firewalld
    
  9. Disable SELinux. Run sudo nano /etc/sysconfig/selinux to open the SELinux configuration file and edit the SELINUX parameter:

    SELINUX=disabled
    
  10. Add the Samba server service to the startup script and restart it:

    $ sudo systemctl enable smb.service
    Created symlink from /etc/systemd/system/multi-user.target.wants/smb.service to /usr/lib/systemd/system/smb.service.
    $ sudo systemctl restart smb.service
    

Install the 1C:Enterprise server

Install the 1C:Enterprise server on the VM:

  1. Upload the distribution archive to your VM's 1c-files directory.

  2. Unpack the distribution and run the installation:

    $ sudo tar –xvf  /1c-files/<archive name>
    $ sudo yum localinstall /1c-files/*.rpm 
    
  3. Start the 1C server:

    $ sudo systemctl start srv1cv83
    
  4. Make sure the 1C:Enterprise server service is running:

    $ systemctl status srv1cv83
    ● srv1cv83.service - SYSV: Starts and stops the 1C:Enterprise daemons
       Loaded: loaded (/etc/rc.d/init.d/srv1cv83; bad; vendor preset: disabled)
       Active: active (exited) since Tue 2020-02-04 14:40:43 UTC; 4 days ago
       Docs: man:systemd-sysv-generator(8)
    Process: 27364 ExecStart=/etc/rc.d/init.d/srv1cv83 start (code=exited, status=0/SUCCESS)
    

Set up a Samba server for the license server

Connect to the server-1c VM via SSH.

  1. Install Samba, the necessary dependencies, and the nano text editor:

    $ sudo yum install nano samba samba-client samba-common, net-utils
    
  2. Disable IPv6 to avoid server conflicts. To do this, open the file /etc/sysctl.conf :

    $ sudo nano /etc/sysctl.conf
    
  3. Add the following lines to the file:

    net.ip6.conf.all.disable_ipv6 = 1
    net.ip6.conf.default.disable_ipv6 = 1
    
  4. Run sudo nano /etc/sysconfig/network to add the following lines to the /etc/sysconfig/network file:

    NETWORKING_IPv6=no
    HOSTNAME=server-1c
    
  5. Configure a shared directory. To do this, open the Samba configuration file:

    $ sudo nano /etc/samba/smb.conf
    
  6. Make the file look like:

    [global]
            workgroup = WORKGROUP
            server string = Samba Server%v
            netbios name = centos
            security = user
            map to guest = bad user
            dns proxy = no
            passdb backend = tdbsam
            printing = cups
            printcap name = cups
            load printers = yes
            cups iptions = raw
            security = user
    
    [files]
            path = /1c-files
            browsable = yes
            writable = yes
            guest ok = yes
            read only = no
    
  7. Create a shared directory and grant access rights to it:

    $ sudo mkdir /1c-files
    $ sudo chmod -R 777 /1c-files
    
  8. Disable the firewall:

    $ sudo systemctl stop firewalld
    $ sudo systemctl disable firewalld
    
  9. Disable SELinux. Run sudo nano /etc/sysconfig/selinux to open the SELinux configuration file and edit the SELINUX parameter:

    SELINUX=disabled
    
  10. Add the Samba server service to the startup script and restart it:

    $ sudo systemctl enable smb.service
    Created symlink from /etc/systemd/system/multi-user.target.wants/smb.service to /usr/lib/systemd/system/smb.service.
    $ sudo systemctl restart smb.service
    

Install the 1C:Enterprise server for the license server

Install the 1C:Enterprise server on the VM:

  1. Upload the distribution archive to your VM's 1c-files directory.

  2. Unpack the distribution and run the installation:

    $ sudo tar –xvf  /1c-files/<archive name>
    $ sudo yum localinstall /1c-files/*.rpm 
    
  3. Start the 1C server:

    $ sudo systemctl start srv1cv83
    
  4. Make sure the 1C:Enterprise server service is running:

    $ systemctl status srv1cv83
    ● srv1cv83.service - SYSV: Starts and stops the 1C:Enterprise daemons
       Loaded: loaded (/etc/rc.d/init.d/srv1cv83; bad; vendor preset: disabled)
       Active: active (exited) since Tue 2020-02-04 14:40:43 UTC; 4 days ago
       Docs: man:systemd-sysv-generator(8)
    Process: 27364 ExecStart=/etc/rc.d/init.d/srv1cv83 start (code=exited, status=0/SUCCESS)
    

Set up a server cluster

Before getting started, configure the server roles and add the infobase to the cluster.

  1. Run the 1C administration console on your computer.
  2. Add the 1C:Enterprise central server Open the context menu of the server list, select New and 1C:Enterprise central server 8.3.
  3. In the Name field, enter server-1c and click OK. You'll see the local cluster in the tree on the left.
  4. Add the working server to the cluster. Open the Working servers context menu, choose New and Working server. In the Computer field of the window that opens, enter licensing-server-1c. This server will be used to issue licenses to other servers.
  5. In the Requirements of functionality purpose section of the licensing-server-1c, open the context menu and select New and Requirement of functionality purpose.
    • In the Requirement object list, select Any requirement object.
    • In the Requirement type list, select Do not assign.
    • Leave the other parameters as they are and click OK.
  6. Apply requirements for assigning functionality to the cluster: open the cluster's context menu and select Apply requirements of functionality purpose (full).
  7. Add another requirement for assigning functionality to the licensing-server-1c with the following parameters:
    • In the Requirement object list, select Licensing service.
    • In the Requirement type list, select Assign.
    • Leave the other parameters as they are and click OK.
  8. Apply requirements for assigning functionality to the cluster: open the cluster's context menu and select Apply requirements of functionality purpose (full).
  9. Add a requirement for assigning functionality to the server-1c with the following parameters:
    • In the Requirement object list, select Client connection.
    • In the Requirement type list, select Assign.
    • Leave the other parameters as they are and click OK.
  10. Add another requirement for assigning functionality to the server-1c with the following parameters:
    • In the Requirement object list, select Licensing service.
    • In the Requirement type list, select Do not assign.
    • Leave the other parameters as they are and click OK.
  11. Apply requirements for assigning functionality to the cluster: open the cluster's context menu and select Apply requirements of functionality purpose (full).

Set up the infobase

  1. In the administration console, open the Infobases context menu, select New and Infobase.

  2. In the window that opens, set the parameters:

    • Name: The name of the database in the Managed Service for PostgreSQL cluster, 1c-database.
    • Secure connection: continuously.
    • Database server: Your DB host address and port, such as rc1a-cwxzr4yimhzgn5pp.mdb.yandexcloud.net port=6432.
    • DBMS type: PostgreSQL.
    • Database: The DB name, 1c-database.
    • Database server user: user1.
    • Database user password: The user password that you set when creating the cluster.
    • Allow license issuing by 1C:Enterprise server: Yes.
    • Language (Country): English (United States).
    • Create database if none present: Disabled.
    • Lock execution of scheduled jobs: Disabled.

    Click OK.

Connect to the infobase

  1. Connect to the OpenVPN server using the client.

  2. Run the 1C:Enterprise client.

  3. Click Add.

  4. Select Add an existing infobase to the list and click Next.

  5. Enter the infobase name, select On 1C:Enterprise server, and specify the following settings:

    • Server cluster: server-1c.ru-central1.internal.
    • Infobase name: 1c.

    Click Next.

  6. Click Ready.

The infobase should appear on the list of infobases. You can now start configuring and using the database.

Delete the created resources

To stop paying for the deployed infrastructure, delete the server-1c and licensing-server-1c VMs and the 1c-pg cluster.

If you reserved a public static IP address, delete it.

In this article:
  • Before you start
  • Required paid resources
  • Prepare the infrastructure
  • Create a VM for the 1C:Enterprise server
  • Create a VM for the license server
  • Create a cluster Managed Service for PostgreSQL
  • Set up a Samba server
  • Install the 1C:Enterprise server
  • Set up a Samba server for the license server
  • Install the 1C:Enterprise server for the license server
  • Set up a server cluster
  • Set up the infobase
  • Connect to the infobase
  • Delete the created resources
Language
Careers
Privacy policy
Terms of use
© 2021 Yandex.Cloud LLC