cells admin datasource capture

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



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.


  1. Capture datasource pydiods1 into a given location $ ./cells admin datasource capture --datasource=pydiods1 --target=/path/to/folder --format=bolt
./cells admin datasource capture [flags]


  -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

      --advertise_address string     Default advertise address (default "")
      --broker string                Pub/sub service for events between services (default "grpc://:8030")
      --config string                Configuration storage URL. Supported schemes: etcd|etcd+tls|file|grpc|mem|vault|vaults (default "file:///home/teamcity/.config/pydio/cells/pydio.json")
      --discovery string             Registry and pub/sub (default "grpc://:8030")
      --grpc_client_timeout string   Default timeout for long-running GRPC calls, expressed as a golang duration (default "60m")
      --registry string              Registry used to contact services (default "grpc://:8030")


Auto generated by Pydio Cells Home Edition v4.4.0 on 3-Apr-2024
Back to top