services	platforms	owner
service-fabric	.NET, windows	roshanroutray, anantshankar17

Service Fabric Backup Explorer (Preview)

This tool should not be used in Production deployments

Review and Update Utility for Service Fabric Reliable Collections

The project empowers the Service Fabric Reliable Stateful application users to audit and review the contents of the Reliable Collections and edit the current state to a consistent view. It also creates backup of the current snapshot of the Reliable Collections which can be loaded in any of the existing Service Fabric cluster which is running the same implementation/version of the Reliable Stateful application.

The changes made to current state will be restored along with the other transactions to current running Service Fabric cluster, hence enabling a consistent view of the collection.

Service Fabric Backup Explorer helps in data correction in case of data corruption. The current state of data can be corrupted because of any bug introduced in application or any wrong entries made in the live clusters.

With the help of Backup Explorer following tasks can be performed :

• Querying of metadata for the collection.
• Current state and its entries in the collection of the backup loaded.
• Update the collection by adding, updating or deleting the entries in the collection.
• Take a fresh backup with the updated state.

The Service Fabric Backup Explorer can be consumed in any of the following ways for view/update of reliable collections of the backup.

1. Parser - NuGet package to view and alter the reliable collections.
2. HTTP Server - HTTP based Rest hosting to view and alter the reliable collections.
3. bkpctl - Backup Controller CLI to view and alter the reliable collections.

Reliable Collections Backup Parser

The NuGet package created to be consumed in application to view, enumerate and alter the reliable collection. Details

HTTP Server

An OWIN based REST API to view, enumerate and alter the state of Reliable Collections. Details

NOTE: Currently, only the Serializers which do not take any parameters as input are supported in Rest Server. Users with serializers having multiple params should use the Nuget in order to perform CRUD operations in the Backup

bkpctl

A Command Line Interface to view, enumerate and alter the state of Reliable Collections.

Details- bkpctl

Requirements

1. .NET Framework 4.8
2. MSBuild
3. Python 3.11
4. python-pip

Usage

Download and extract the latest release from the Repository.

Installing bkpctl CLI

To install the the CLI tool from local directory; for easy I/O operations on the backup :-

cd %release/bin%
pip install -e .\backup-explorer-cli

Using Rest Server

cd %release/bin%
cd ReliableCollectionBackupRestServer
.\Microsoft.ServiceFabric.ReliableCollectionBackup.RestServer.exe --config %path\of\config.json%

Using Parser Nuget

ReliableCollectionBackup Parser NuGet Package can be downloaded from nuget.org official repository. Details of using the Nuget are mentioned in the docs here.

Developer Help and & Documentation

Locally building the Parser and Rest Server

From Repository root folder, run in Powershell:

 .\build.ps1 -build

Build bkpctl CLI

From Repository root folder , run in Powershell:

 .\build.ps1 -buildCli

In order to use bkpctl, the REST Server must be up and running, so that CLI can fetch the required backup, and present it on the command line.

Build all packages including Tests

From Repository root folder , run in Powershell:

 .\build.ps1 -buildAll

User can choose to specify the path of MSBuild or the Visual Studio Version installed in the system. Default Version for VS is 2017.

Generating Nuget Packages

From Visual Studio Command Prompt which has MSBuild defined:

.\build.ps1 -nuget

Running Rest Server

From the Repository root folder, perform the following steps :

pushd src\BackupExplorer\RestServer\
dotnet run --no-build --config configs\sampleconfig.json

Testing REST API's

curl -v 'http://localhost:5000/$query/testDictionary?$top=2'

Configuring the Rest Server of Backup Viewer

The Rest Server takes in as input, path to config json file, where user can specify the necessary configurations for the Backup Viewer to Read the Backups.

Sample Config file can be seen at sampleconfig.json

In the config file, user can define the following :

1. App Name and Service Name
2. BackupChainPath - Location to where the Backups are located in the System.
3. CodePackagePath - Location to where binaries for Serializers and objects are located in the System.
4. Serializers - It's an array, where user needs to specify all the Classes, and their Serializers that are required for the Backup Viewer to read the Backups.

Running Tests

Once code and tests are locally built, you can run tests in order to validate your changes/ check whether everything works fine.

cd src\BackupExplorer\Parser.Tests
dotnet test --no-build --diag test_results.log --verbosity n --logger "console;verbosity=detailed" --configuration Debug

# running one test
dotnet test --no-build --diag test_results.log --verbosity n --logger "console;verbosity=detailed" --filter "FullyQualifiedName~BackupParser_EachTransactionHasRightChangesEvenWithBlockingTransactionAppliedEvents" --configuration Debug

Running Rest Server tests

cd src\BackupExplorer\RestServer.Tests
dotnet test --no-build --diag test_results.log --verbosity normal --logger "console;verbosity=detailed"

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

Ideas and Improvements

We encourage community feedback and contribution to improve this application. To make any contribution, our contribution guidelines needs to be followed. If you have any new idea, please file an issue for that.

Contribution Guidelines

Please create a branch and push your changes to that and then, create a pull request for that change. These is the check list that would be required to complete, for pushing your change to master branch.

1. Build the application with your changes.
2. The application should satisfy all the test cases written for Parser.
3. Add additional test cases relevant to your changes.
4. Verify whether Rest Server is working correctly or not, using the Tests present in RestServer.Tests.