Google Enables Document Backup to Drive in Stable Play Services 26.26 Release
Google has finally activated automatic backup of documents from Android smartphones to the cloud. The feature, prepared by the company for almost a year, is now distributed in the stable version of Google Play Services 26.26.
On Pixel devices a new “Documents” item appears in the path Settings → Accounts and backup → Google Backup. By default the option stays turned off, so Google does not automatically feed Drive with the contents of the Downloads folder.
After activation, documents are uploaded to a newly created Android backups folder on Google Drive. Inside this folder a separate directory is created for each smartphone. Supported formats include PDF, DOC, PPT, XLS, ZIP and others; even APK files located in the downloads directory are included.
Users pay for the convenience with storage space: copies occupy quota in Google Drive. The settings page allows checking remaining capacity, freeing space or purchasing additional storage.
Disabling the backup does not delete already uploaded files, so manual cleanup of the Drive folder is required. Full synchronization is also absent: changes made on the device are not reflected in the cloud copy and vice versa.
First traces of the function were discovered in August 2025. In February 2026 Google officially mentioned it in a Play System update. The capability later appeared in the beta channel of Play Services and has now reached the stable build.
Related articles
Bridging Manual and Automated Testing: InfoWatch Engineer Outlines Unified Quality Process
InfoWatch senior test engineer Mikhail Shalepo has published a detailed article describing how his team built a reproducible process that links manual and automated testing into a single quality system. The approach addresses the growing complexity of server-side products that undergo quarterly releases and require extensive matrix testing across multiple operating systems and installation scenarios. Shalepo explains that the regulation focuses on decision points rather than prescribing exact test volumes, ensuring that choices about automation candidates, smoke-test gates, failure ownership, and manual compensation are documented and visible to the entire team. The framework divides work into two main blocks—feature development and pre-release regression—each containing preparation, execution, and completion stages. Key outputs include linked artifacts in TMS Scale, explicit Definition of Done criteria, and traceable coverage data that prevents reliance on individual knowledge. The article also shares practical lessons, including why separate mind maps and tables failed to stay current and how the team now integrates automation status directly with test cases.
Indeed Certificate Manager 7.3 Adds OpenLDAP, Dogtag CA and Linux Domain Support
Indeed has released Certificate Manager 7.3, a major update focused on Linux environments and expanded PKI capabilities. The new version integrates with OpenLDAP and Alt Domain, allowing organizations to build certificate infrastructures without relying on a single vendor. Dogtag CA support enables certificate issuance and lifecycle management while hiding native administrative complexity. Kerberos SSO has been added for Linux services, reducing password exposure. Hardware security improvements include Rutoken BIO three-factor authentication and complex password scenarios with Rutoken Logon. The release also adds compatibility with Windows Server 2025, Debian 13, Alt 11 and ALD Pro 3.0, plus new JaCarta models and SafeTech CA service certificates.
Russian Data Centers Above 500 kW May Receive Protection from Forced Relocation Under Gilotina 2.0 Roadmap
Land plots hosting large data centers in Russia could gain special protection against seizure for state or municipal needs as part of the Gilotina 2.0 roadmap for the data center sector. The proposed ban, set to take effect on December 15, 2027, would apply to facilities with at least 500 kW capacity listed in the Russian registry of data centers. The measure aims to prevent the demolition of operational sites for territory redevelopment, recognizing that data centers cannot be easily disassembled and relocated like simpler structures. Industry groups have raised concerns over the 500 kW threshold and mandatory registry linkage, noting that participation in the registry is voluntary and that standardized methods to separate IT load from total power capacity are lacking. If relocation becomes unavoidable, developers would need to provide equivalent land or fund new construction, including full equipment transfer, power and connectivity infrastructure, capacity reservation, and compensation for early contract terminations with clients. Major operators including RTK-COD, MTS, and Megafon have backed the initiative while opposing compulsory registry ties, highlighting acute capacity shortages in Moscow where utilization reaches 95 percent.
R-Vision SIEM Debuts at Standoff 17 Cyber Battle and Processes 8.8 Million Correlation Events
R-Vision presented its SIEM solution for the first time at the Standoff 17 cyber exercise, where the akPots team used it to monitor a telecom operator infrastructure and investigate incidents. The product was deployed in two weeks, with 80 percent of required event sources already supported out of the box. During four days of continuous attacks the system triggered 46 correlation rules, generated more than 8.8 million correlation events and 40 thousand alerts, while analysts created 13 custom widgets and executed over 9,000 search queries. Resource consumption remained low, with the collector averaging 0.7 CPU and 1.9 GB RAM even under peak load. Participants rated the solution 4 or 5 out of 5 and highlighted raw-text search, the RQL query language and event grouping as the most useful features. The exercise also identified areas for interface and alert-description improvements.