Tales Developer 1C: Admin
All 1C developers work in one way or another with IT services and directly with system administrators. But this interaction is not always smooth. I would like to tell you some funny stories about this.
Most of our customers are large holdings with their large IT departments. And for backup copies of information databases, as a rule, client specialists are responsible. But there are also relatively small organizations. Especially for them, we have a service, according to which we take care of all issues related to backing up the entire 1C-th one. About such a company and will be discussed in this story.
A new client came in support of 1C and, among other things, the contract had a clause that we are responsible for backup copies, although they had their own system administrator in the state. The base client-server, as a DBMS - MS SQL. A fairly standard situation, but still there was one nuance: the main base was quite large, but the monthly increase was quite small. That is, the database contained a lot of historical data. Considering this feature, I set up backup maintenance plans as follows: a full backup was made on the first Saturday of each month, it was quite heavy, then a differential copy was made every night — a relatively small volume and a copy of the transaction log every hour. Moreover, full and differential copies, moreover, that were copied to a network resource, were also additionally uploaded to our FTP server. This is a mandatory requirement when providing this service.
All this was successfully configured, put into operation and worked in general without failures.
')
But a few months later the system administrator changed in this organization. The new sysadmin began to gradually rebuild the company's IT infrastructure in accordance with modern trends. In particular, virtualization, disk shelves appeared, access was closed everywhere and everything, etc., which in the general case, of course, can not but rejoice. But not always everything went smoothly for him, often there were problems with the performance of 1C, which caused some disagreements and misunderstandings with our support. Also, it should be noted that our relations with him were generally quite cold and somewhat strained, which only increased the degree of tension in the event of any problems.
But one morning it was discovered that the server of this client is unavailable. I called the system administrator to find out what happened and received something like “Our server crashed, we are working on it, it's not up to you”. Well, that work. So the situation is under control. After dinner, I call again, in the admin's voice, instead of irritation, we already feel fatigue and apathy. Trying to clarify what happened, and can we somehow help? As a result of the conversation, the following became clear:
He moved the server to a new storage system with a newly assembled raid. But something went wrong, and after a few days, this raid crumbled safely. Either the controller burned, or something happened to the disks, I don’t remember exactly, but all the information turned out to be irretrievably lost. And the main thing was that the network resource with backups also appeared on the same disk array during all migrations. That is, both the productive base itself and all its backup copies were lost. And what to do now is not clear.
Calmly, I say. We have your night backup. In response - silence, according to which I understand that I have just saved a person’s life. We are starting to discuss how to transfer this copy to a new, just-deployed server. But there was a problem.
Remember, I said that the full backup was quite large? I knowingly did it once a month on Saturdays. The fact is that the company was a small factory, which was located far from the city and the Internet was so-so. By Monday morning, that is, over the weekend, this copy with a grief in half had time to upload to our FTP server. But to wait a day or two until it boots in the opposite direction was not possible. After several unsuccessful attempts to overwrite the file, the admin took out the hard drive direct from the new server, found somewhere a car with a driver and quickly rushed to our office, since we are still in the same city.
While we were in the server room and waited for the files to be copied, we first met, so to speak, "live", drank a cup of coffee, and talked in an informal setting. I sympathized with his grief and with a full screw backups sent back, hastily restore the stopped work of the company.
Subsequently, all of our applications to the IT department were resolved very quickly and there were no more disagreements.
Once, with a single client, I couldn’t publish 1C for web access through IIS for a very long time. It seems to be an ordinary task, but it didn’t work out everything. Local system administrators connected, tried different settings and configuration files. 1C on the web normally did not want to work in any. Something was wrong with the domain security policies, the local firewall, or even the devil knows what. On the Nth iteration, the admin drops me a link with the words:
- Try again on this here instructions. Everything is quite detailed there. If you fail, write to the author of this site, maybe he will help.
“No,” I say, “will not help.”
- Why?
- I am the author of this site ... (
As a result, without any problems launched on Apache. IIS could not win.
We had a client - a small manufacturing enterprise. They had a server, such a kind of “classic” 3 in 1: terminal server + application server + database server. They worked in some industry configuration based on SCP, users were around 15-20, the system's performance suited everyone in principle.
As time went on, everything worked more or less stably. But then Europe imposed sanctions against Russia, as a result of which the Russians began to buy mainly domestic-made products, and things from this company went uphill sharply. The number of users has grown to 50-60 people, a new branch has opened, and the workflow has also increased accordingly. And now the current server has ceased to cope with a sharply increased load, and 1C began, as they say, to “slow down”. During peak hours, the documents were carried out for several minutes, blocking errors occurred, forms were opened for a long time, and the whole other bouquet of related services was opened. The local system administrator dismissed all the problems, they say, "This is your 1C, and you understand." We have repeatedly proposed to conduct an audit of the system on performance, but that was not the case until the audit itself. The client simply asked for recommendations for troubleshooting.
Well, I sat down and wrote a rather lengthy letter that it was necessary to separate the roles of the terminal server and the application server from the DBMS (which, in principle, had already been said many times before). I wrote about DFSS on terminal servers, about Shared Memory, added links to authoritative sources and even offered some options for the equipment. This letter reached the authorities in the company, descended back to the IT department from the “Execute” resolutions and the ice was broken.
After some time, the admin sends me an aypishnik new server and login credentials. He says that MS SQL and 1C server components are deployed there, and it is necessary to transfer the bases, but so far only to the DBMS server, as there have been some problems with the 1C keys.
I went, really, all services are running, the server is not very powerful, well, I think, better than nothing. Transferred while the database to somehow unload the current server. In the agreed time, I carried out all the transfers, but the situation did not change - all the same performance problems. Strange, of course, well, let's register the bases in the 1C cluster, we'll see.
It takes several days, the keys are not transferred. I'm interested in what the problem is, everything seems to be simple there - I took it out of one server, stuck it in another, put the driver and was done. Admin responds yulit, says something about port forwarding, virtual server and so on.
Hmm ... Virtual server? It seems that there has never been any virtualization and they were not ... I remember a fairly well-known problem with the impossibility of forwarding the 1C server key to a virtual machine on Hyper-V in Windows Server 2008. And then I begin to suspect some of my suspicions ...
I open the server manager - Roles - a new role has appeared - Hyper-V. I go to the Hyper-V dispatcher, see one virtual machine, connect ... And really ... Our new database server ...
So what? The instructions of the authorities and my recommendations are fulfilled, the roles are separated. The task can be closed.
After some time, the crisis had already happened, the new branch had to be closed, the load had decreased, the system performance had become more or less tolerable.
Well, the server key, of course, could not be forwarded to the virtual machine. As a result, everything is as it was and left: the terminal server + 1C cluster on a physical machine, the database server in the same virtual one.
And it would be okay if this was some kind of sharashkin office. So no. Well-known company, whose products you probably know and have seen in the relevant departments of every kind of Tapes and Auchans.
One large holding with ambitious plansto take over the world once again bought a small company with the goal of including it in its mega-corporation. In all divisions of this holding, users work in their bases, but with identical configuration. And here we have started a small project to include a new division in this system.
First of all, it is necessary to deploy combat and test bases. The developer received the data for the connection, enters the server, sees the installed MS SQL, 1C server, sees 2 logical drives: a 250 Gigabyte “C” drive and a 1 terabyte “D” drive. Well, “C” is a system, “D” is for data, the developer logically decides and deploys all the databases there. Even service plans, including backups, are set up just in case (although we are not responsible for this). True backups evolved here on the "D". In the future, it was planned to reconfigure already on some separate network resource.
The project started, the consultants conducted training on work in the new system, the remnants were transferred, some small point improvements were made and users started working in the new information base.
Everything went well until one Monday morning it was discovered that the database disk was gone. There is simply no “D” on the server and that's it.
Further investigation revealed the following: in fact, this “server” was the work computer of the local system administrator. The truth was still on it server OS. A private USB drive of this admin was inserted into the server. And now the administrator went on vacation, taking with him and his screw, in order to pump films on him for the road.
Thank God, he did not manage to delete the database files and managed to restore the working database.
It is noteworthy that everyone, in general, was satisfied with the performance of the system located on the USB drive. Nobody complained of any unsatisfactory work 1C. This later, in the holding, a megaproject began to transfer all information bases to a single centralized platform with super-servers, storage systems for a million rubles, heaped hypervisors and intolerable 1C brakes in all branches.
But that's another story ...
High speed communication channel
Most of our customers are large holdings with their large IT departments. And for backup copies of information databases, as a rule, client specialists are responsible. But there are also relatively small organizations. Especially for them, we have a service, according to which we take care of all issues related to backing up the entire 1C-th one. About such a company and will be discussed in this story.
A new client came in support of 1C and, among other things, the contract had a clause that we are responsible for backup copies, although they had their own system administrator in the state. The base client-server, as a DBMS - MS SQL. A fairly standard situation, but still there was one nuance: the main base was quite large, but the monthly increase was quite small. That is, the database contained a lot of historical data. Considering this feature, I set up backup maintenance plans as follows: a full backup was made on the first Saturday of each month, it was quite heavy, then a differential copy was made every night — a relatively small volume and a copy of the transaction log every hour. Moreover, full and differential copies, moreover, that were copied to a network resource, were also additionally uploaded to our FTP server. This is a mandatory requirement when providing this service.
All this was successfully configured, put into operation and worked in general without failures.
')
But a few months later the system administrator changed in this organization. The new sysadmin began to gradually rebuild the company's IT infrastructure in accordance with modern trends. In particular, virtualization, disk shelves appeared, access was closed everywhere and everything, etc., which in the general case, of course, can not but rejoice. But not always everything went smoothly for him, often there were problems with the performance of 1C, which caused some disagreements and misunderstandings with our support. Also, it should be noted that our relations with him were generally quite cold and somewhat strained, which only increased the degree of tension in the event of any problems.
But one morning it was discovered that the server of this client is unavailable. I called the system administrator to find out what happened and received something like “Our server crashed, we are working on it, it's not up to you”. Well, that work. So the situation is under control. After dinner, I call again, in the admin's voice, instead of irritation, we already feel fatigue and apathy. Trying to clarify what happened, and can we somehow help? As a result of the conversation, the following became clear:
He moved the server to a new storage system with a newly assembled raid. But something went wrong, and after a few days, this raid crumbled safely. Either the controller burned, or something happened to the disks, I don’t remember exactly, but all the information turned out to be irretrievably lost. And the main thing was that the network resource with backups also appeared on the same disk array during all migrations. That is, both the productive base itself and all its backup copies were lost. And what to do now is not clear.
Calmly, I say. We have your night backup. In response - silence, according to which I understand that I have just saved a person’s life. We are starting to discuss how to transfer this copy to a new, just-deployed server. But there was a problem.
Remember, I said that the full backup was quite large? I knowingly did it once a month on Saturdays. The fact is that the company was a small factory, which was located far from the city and the Internet was so-so. By Monday morning, that is, over the weekend, this copy with a grief in half had time to upload to our FTP server. But to wait a day or two until it boots in the opposite direction was not possible. After several unsuccessful attempts to overwrite the file, the admin took out the hard drive direct from the new server, found somewhere a car with a driver and quickly rushed to our office, since we are still in the same city.
While we were in the server room and waited for the files to be copied, we first met, so to speak, "live", drank a cup of coffee, and talked in an informal setting. I sympathized with his grief and with a full screw backups sent back, hastily restore the stopped work of the company.
Subsequently, all of our applications to the IT department were resolved very quickly and there were no more disagreements.
Contact your system administrator.
Once, with a single client, I couldn’t publish 1C for web access through IIS for a very long time. It seems to be an ordinary task, but it didn’t work out everything. Local system administrators connected, tried different settings and configuration files. 1C on the web normally did not want to work in any. Something was wrong with the domain security policies, the local firewall, or even the devil knows what. On the Nth iteration, the admin drops me a link with the words:
- Try again on this here instructions. Everything is quite detailed there. If you fail, write to the author of this site, maybe he will help.
“No,” I say, “will not help.”
- Why?
- I am the author of this site ... (
As a result, without any problems launched on Apache. IIS could not win.
One level deeper
We had a client - a small manufacturing enterprise. They had a server, such a kind of “classic” 3 in 1: terminal server + application server + database server. They worked in some industry configuration based on SCP, users were around 15-20, the system's performance suited everyone in principle.
As time went on, everything worked more or less stably. But then Europe imposed sanctions against Russia, as a result of which the Russians began to buy mainly domestic-made products, and things from this company went uphill sharply. The number of users has grown to 50-60 people, a new branch has opened, and the workflow has also increased accordingly. And now the current server has ceased to cope with a sharply increased load, and 1C began, as they say, to “slow down”. During peak hours, the documents were carried out for several minutes, blocking errors occurred, forms were opened for a long time, and the whole other bouquet of related services was opened. The local system administrator dismissed all the problems, they say, "This is your 1C, and you understand." We have repeatedly proposed to conduct an audit of the system on performance, but that was not the case until the audit itself. The client simply asked for recommendations for troubleshooting.
Well, I sat down and wrote a rather lengthy letter that it was necessary to separate the roles of the terminal server and the application server from the DBMS (which, in principle, had already been said many times before). I wrote about DFSS on terminal servers, about Shared Memory, added links to authoritative sources and even offered some options for the equipment. This letter reached the authorities in the company, descended back to the IT department from the “Execute” resolutions and the ice was broken.
After some time, the admin sends me an aypishnik new server and login credentials. He says that MS SQL and 1C server components are deployed there, and it is necessary to transfer the bases, but so far only to the DBMS server, as there have been some problems with the 1C keys.
I went, really, all services are running, the server is not very powerful, well, I think, better than nothing. Transferred while the database to somehow unload the current server. In the agreed time, I carried out all the transfers, but the situation did not change - all the same performance problems. Strange, of course, well, let's register the bases in the 1C cluster, we'll see.
It takes several days, the keys are not transferred. I'm interested in what the problem is, everything seems to be simple there - I took it out of one server, stuck it in another, put the driver and was done. Admin responds yulit, says something about port forwarding, virtual server and so on.
Hmm ... Virtual server? It seems that there has never been any virtualization and they were not ... I remember a fairly well-known problem with the impossibility of forwarding the 1C server key to a virtual machine on Hyper-V in Windows Server 2008. And then I begin to suspect some of my suspicions ...
I open the server manager - Roles - a new role has appeared - Hyper-V. I go to the Hyper-V dispatcher, see one virtual machine, connect ... And really ... Our new database server ...
So what? The instructions of the authorities and my recommendations are fulfilled, the roles are separated. The task can be closed.
After some time, the crisis had already happened, the new branch had to be closed, the load had decreased, the system performance had become more or less tolerable.
Well, the server key, of course, could not be forwarded to the virtual machine. As a result, everything is as it was and left: the terminal server + 1C cluster on a physical machine, the database server in the same virtual one.
And it would be okay if this was some kind of sharashkin office. So no. Well-known company, whose products you probably know and have seen in the relevant departments of every kind of Tapes and Auchans.
Holiday Schedule
One large holding with ambitious plans
First of all, it is necessary to deploy combat and test bases. The developer received the data for the connection, enters the server, sees the installed MS SQL, 1C server, sees 2 logical drives: a 250 Gigabyte “C” drive and a 1 terabyte “D” drive. Well, “C” is a system, “D” is for data, the developer logically decides and deploys all the databases there. Even service plans, including backups, are set up just in case (although we are not responsible for this). True backups evolved here on the "D". In the future, it was planned to reconfigure already on some separate network resource.
The project started, the consultants conducted training on work in the new system, the remnants were transferred, some small point improvements were made and users started working in the new information base.
Everything went well until one Monday morning it was discovered that the database disk was gone. There is simply no “D” on the server and that's it.
Further investigation revealed the following: in fact, this “server” was the work computer of the local system administrator. The truth was still on it server OS. A private USB drive of this admin was inserted into the server. And now the administrator went on vacation, taking with him and his screw, in order to pump films on him for the road.
Thank God, he did not manage to delete the database files and managed to restore the working database.
It is noteworthy that everyone, in general, was satisfied with the performance of the system located on the USB drive. Nobody complained of any unsatisfactory work 1C. This later, in the holding, a megaproject began to transfer all information bases to a single centralized platform with super-servers, storage systems for a million rubles, heaped hypervisors and intolerable 1C brakes in all branches.
But that's another story ...
Source: https://habr.com/ru/post/449946/
All Articles