All 1C developers, one way or another, closely interact with IT services and directly with system administrators. But this interaction does not always go smoothly. I would like to tell you a few funny stories about this.
High-speed communication channel
Most of our clients are large holdings with their own large IT departments. And, as a rule, the client's specialists are responsible for backing up infobases. 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 the backup of the entire 1C. About such a company and will be discussed in this story.
A new client came to support 1C and, among other things, there was a clause in the contract that we were responsible for backups, although they had their own system administrator in the state. The base is client-server, as a DBMS - MS SQL. A fairly standard situation, but there was still one nuance: the main base was quite large, but at the same time, the monthly increase was very small. That is, the database contained a lot of historical data. Given this feature, I set up backup maintenance plans as follows: on the first Saturday of each month, a full backup was taken, it was quite heavy, then every night a differential backup was taken - a relatively small amount, and every hour a copy of the transaction log. Moreover, full and differential copies were not only copied to a network resource, but also additionally uploaded to our FTP server. This is a mandatory requirement for this service.
All this was successfully configured, put into operation and worked, in general, without failures.
But a few months later, the system administrator in this organization changed. The new system administrator began to gradually rebuild the company's IT infrastructure in accordance with modern trends. In particular, virtualization appeared, disk shelves, access was closed everywhere and everything, etc., which in the general case, of course, cannot 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 generally developed rather cold and somewhat strained, which only increased the degree of tension in the event of any problems.
But one morning it turned out that the server of this client is unavailable. I called the system administrator to find out what happened and received as an answer something like "We have a server down, we are working on it, not up to you." Well, it's good that they work. So the situation is under control. After lunch, I call back again, instead of irritation, fatigue and apathy are already felt in the admin's voice. I'm trying to figure out what's wrong and is there any way we can help? The result of the conversation was the following:
He moved the server to a new storage system with a freshly assembled raid. But something went wrong and a few days later this raid safely crumbled. Toli the controller burned out, toli something happened to the disks, I donβt remember exactly, but all the information was irretrievably lost. And the main thing was that the network resource with backups also ended up on the same disk array in the process of any migrations. That is, both the productive base itself and all its backup copies were lost. And what to do now is not clear.
Calm down, I say. We have your nightly backup. In response - silence, by which I understand that I just saved a man's life. We begin to discuss how to transfer this copy to a new, newly deployed server. But here, too, a problem arose.
Remember when I said that the full backup was quite large? I did it once a month on Saturdays for a reason. The fact is that the company was a small factory, which was located far outside the city and their Internet was very so-so. By Monday morning, that is, over the weekend, this copy with grief in half had time to upload to our FTP server. But it was not possible to wait a day or two until it loads in the opposite direction. After several unsuccessful attempts to transfer the file, the admin removed the hard drive directly 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 standing in our server room and waiting 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 sent him back with a full screw of backups, hastily restoring the stopped work of the company.
Subsequently, all our requests to the IT department were resolved very quickly and there were no more disagreements.
Contact your system administrator
Once, for a client, I could not publish 1C for web access via IIS for a very long time. It seems to be an ordinary task, but here it didnβt work out to start everything. Local system administrators connected, tried different settings and configuration files. 1C on the web did not normally want to work in any. Something was wrong either with the domain security policies, or with the local sophisticated firewall, or with the devil knows what else. At the Nth iteration, the admin sends me a link with the words:
βTry again with these instructions. Everything is pretty detailed there. If it does not work, write to the author of this site, maybe he will help.
βNo,β I say, βit wonβt help.
- ΠΠΎΡΠ΅ΠΌΡ?
- I am the author of this site ... (
As a result, they launched it on Apache without any problems. 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-specific configuration based on SCP, there were around 15-20 users, the performance of the system, in principle, suited everyone.
Time passed, 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 products, and the business of this company went uphill. The number of users has grown to 50-60 people, a new branch has opened, and the document flow has grown accordingly. And now the current server has ceased to cope with the sharply increased load, and 1C began, as they say, βslow downβ. During peak hours, documents were processed for several minutes, blocking errors rained down, forms opened for a long time, and a whole bunch of other related services. The local system administrator shrugged off all the problems, saying "This is your 1C, you figure it out." We have repeatedly proposed to audit the system for performance, but it never came to the audit itself. The client simply asked for recommendations for troubleshooting.
Well, I sat down and wrote a rather voluminous letter about the need to separate the roles of the terminal server and the application server from the DBMS (which, in principle, we have already said many times before). I wrote about DFSS on terminal servers, about Shared Memory, gave links to authoritative sources, and even suggested some hardware options. This letter reached the powers that be in the company, descended back to the IT department with resolutions βPerformβ and the ice, in general, was broken.
After some time, the admin sends me the IP address of the new server and login credentials. He says that MS SQL and 1C server components are deployed there, and the databases need to be transferred, but so far only to the DBMS server, since there were some problems with the 1C keys.
I went, indeed, all services are running, the server is not very powerful, okay, I think it's better than nothing. I'll transfer the databases for now in order to somehow unload the current server. At the agreed time, I completed all the transfers, but the situation has not changed - all the same performance problems. Strange, of course, well, let's register the databases in the 1C cluster, we'll see.
A few days pass, the keys have not been transferred. Iβm wondering what the problem is, everything seems to be simple there - I took it out of one server, stuck it in another, installed the driver and thatβs it. The admin responds by hustling, saying something about port forwarding, a virtual server, and so on.
Hmm⦠Virtual server? It seems that there has never been any virtualization and they never existed ... I recall a fairly well-known problem with the impossibility of forwarding a 1C server key to a virtual machine on Hyper-V in Windows Server 2008. And here some suspicions begin to form in me ...
I open the server manager - Roles - a new role has appeared - Hyper-V. I go to the Hyper-V manager, I see one virtual machine, I connect ... And indeed ... Our new database server ...
So what? The instructions of the authorities and my recommendations have been fulfilled, the roles have been separated. The task can be closed.
Some time later, a crisis hit, the new branch had to be closed, the load decreased, the system performance became more or less tolerable.
Well, the server key, of course, could not be forwarded to the virtual machine. As a result, everything was left as is: a terminal server + 1C cluster on a physical machine, a database server in the same virtual machine.
And it would be okay if it was some kind of sharashka office. So no. A well-known company, whose products you probably know and have seen in the relevant departments of all Lenta and Ashanov.
Hard drive vacation schedule
One large holding with ambitious plans to take over the world once again bought a small company in order to include it in its mega-corporation. In all subdivisions of this holding, users work in their databases, but with an identical configuration. And so we started a small project to include a new unit in this system.
First of all, you need to deploy a productive and test bases. The developer received the connection data, enters the server, sees the installed MS SQL, 1C server, sees 2 logical disks: the C drive for 250 gigabytes and the D drive for 1 terabyte. Well, βCβ is the system, βDβ is for data, the developer decides logically and deploys all the databases there. I even set up maintenance plans, including backup, just in case (although we are not responsible for this). True, backups were added here on "D". In the future, it was planned to reconfigure it to some separate network resource.
The project started, the consultants conducted training on how to work in the new system, the leftovers were transferred, some minor point improvements were made, and users began to work in the new information base.
All was going well until one Monday morning it was discovered that the database disk was missing. There is simply no "D" on the server and that's it.
Further investigation revealed this: in fact, this "server" was the work computer of the local system administrator. True, it still had a server OS on it. This admin's personal USB drive was plugged into the server. And so the administrator went on vacation, taking with him his screw, in order to pump movies on it on the road.
Thank God, he did not have time to delete the database files and the productive database was restored.
It is noteworthy that everyone, in general, was satisfied with the performance of the system located on the USB drive. No one complained about any unsatisfactory work of 1C. It was later that the holding began a mega-project to transfer all information databases to a single centralized platform with super-servers, storage systems for a million+ rubles, fancy hypervisors and unbearable 1C brakes in all branches.
But this is a completely different story ...
Source: habr.com