Skip to content

cellsv5alpha14 admin datasource capture

Capture index and objects into JSON or BoltDB format for sync debugging purposes

Synopsis

DESCRIPTION

Sometimes a subtle glitch may break structured datasources resynchronization, and for debugging purpose it can be handy to capture both the "left" and "right" endpoints, namely the sql index and the s3 storage listing.

EXAMPLES

  1. Capture datasource pydiods1 into a given location $ /home/pydio/go/src/github.com/pydio/cells/cellsv5alpha14 admin datasource capture --datasource=pydiods1 --target=/path/to/folder --format=bolt
1
/home/pydio/go/src/github.com/pydio/cells/cellsv5alpha14 admin datasource capture [flags]

Options

1
2
3
4
5
6
  -d, --datasource string   Name of datasource to capture
  -f, --format string       One of bolt|json storage, bolt by default (default "bolt")
  -h, --help                help for capture
      --load-pydio-uuids    If side is providing content, load content as metadata when reading a '.pydio' node
  -s, --sides string        Capture both sides, can be restricted by specifying s3 or index. (default "both")
  -t, --target string       Target folder where to store the snapshots

Options inherited from parent commands

1
2
3
      --cluster string               Name of the cluster for the node (default "default")
      --config string                Configuration storage URL. Supported schemes: etcd|file|mem|vault|vaults (default "file:///home/pydio/cells-working-dir/cells/pydio.json")
      --grpc_client_timeout string   Default timeout for long-running GRPC calls, expressed as a golang duration (default "60m")
Auto generated by Pydio Cells Home Edition v4.9.92-alpha15 on 6-Nov-2025