Initialization
Language selection, backup location, number of folders, administrator information and configuration saving.
Existing functionBackup · restore · scheduling · administration
Existing product · functional · operationalPraticalSystem SRSave & Restore — back up and restore without waiting for new development.
PraticalSystem SR is running today. The product already includes configuration, scheduling, automatic backup, single or multiple restore, administration and licensing. For a new client, the work to be done is the deployment in its environment : architecture, installation, configuration, testing and commissioning.
WHAT ALREADY EXISTS
A real product, with real functions already documented and used.
PraticalSystem SR does not start from a blank page. Its functional documentation and interfaces show a complete chain from initialization to restore and license renewal.
Folders & documents
Selection of folders or documents to protect, organization by backup folder and modification of choices.
Existing functionScheduling
Operating hours, backup times, intervals and technical windows configurable from the interface.
Existing functionAutomatic backup
The backup engine is launched automatically by PraticalSystem SR according to the defined configuration.
Existing functionRestore
Selection of the backup to restore, single or multiple restore, folder/document selection and confirmation before execution.
Existing functionAdministration & licensing
Password-protected actions, administrator management, controlled shutdown, annual license, renewal and serial number.
Existing functionREAL VISUAL EVIDENCE
The product can be seen in its own interfaces.
The screenshots below come from the real documents and interfaces supplied for PraticalSystem SR. They are neither generated nor reconstructed.
PREREQUISITES & ARCHITECTURE
Deployment requirements are already documented.
The historical prerequisites supplied with PraticalSystem SR make it possible to frame the client environment before installation.
Documented prerequisites
- Microsoft Windows Server 2019 or Windows 10/11.
- Microsoft Office Pro 2019 / 2024.
- Word, Excel, Outlook and Access within the documented Office scope.
- Configured internal network.
- Internet / VPN depending on the selected deployment architecture.
- RDS application server, PDC data server, backup/restore server and Replica depending on the scenario.
The presence of Access in the prerequisites does not, by itself, establish that Access is PraticalSystem SR’s internal data engine.
DOCUMENTED ARCHITECTURES
Deployment adapts to the client context.
The historical documentation describes several deployment models. They provide a working basis for defining the actual deployment for each client.
Client-integrated architecture
Application, data and backup/restore can be located within the client environment.
Data Center architecture
RDS, PDC and the backup/restore server can be located in a Data Center according to the documented scenario.
Hybrid architecture
Application and data servers can remain at the client site while backup/restore is hosted remotely, with network/VPN according to the architecture.
The separation between application / data / backup-restore / Replica is a concrete historical foundation. The final implementation must be validated according to the client’s network, storage, security and continuity constraints.
CLIENT DEPLOYMENT
What remains to be done is not “develop the product”.
The next commercial and technical step is deployment in the client’s real environment, with checks before production use.
Environment
Identify servers, data, network, folders and constraints.
Architecture
Determine the appropriate deployment: local, Data Center or hybrid.
Product
Install the components and verify the prerequisites.
Backups
Folders, documents, schedules, intervals and administration.
Backup & restore
Run controlled backups and restores.
Operations
Validate real operation and license management.
FUTURE EVOLUTIONS — RETAINED
Everything already considered remains on the roadmap.
These subjects are not removed. They represent possible modernization and evolution paths for the existing product, without calling into question the fact that PraticalSystem SR already works today.
Modernization foundation studied
- storage model;
- modernized scheduling;
- retention and versioning;
- encryption;
- immutability / offline if retained;
- integrity checks;
- structured restore tests.
Operations & integration studied
- RPO / RTO;
- monitoring;
- API;
- RBAC / MFA;
- monitoring or operations via GCC when contractually relevant;
- controlled migration from historical installations.
Rule: none of these evolutions may be presented as a currently proven function if it is not yet proven — and none may be presented as a condition for the current product to operate.
STANDALONE & INTEGRABLE
PraticalSystem SR remains a full product in its own right.
Save & Restore is PraticalSystem SR: they are not two different products. The product can operate independently and can fit into a broader environment when integration is relevant.
Standalone product
Backup and restore do not depend on UNIDESK, GCC or any other TECKINFO product.
Integration history
A historical interaction with ERP / Sales Management has been documented and remains a reference for real usage.
Future integrations
Other systems can be connected when the need, contract and technical architecture justify it.
The next step is to show you a live demonstration.
Let’s review your environment, the data to protect and your architecture and, as proof, run the necessary tests.