Backup and Restore

backup and restore an edge device from lem ui trigger lem > edge lifecycle management > edge devices > select device > backups > make backup / restore backups are stored in lem managed s3 and accessed via pre signed urls (no further auth needed on the url itself) the backup target on restore can be a different device than the source, which enables configuration cloning across devices step table step name in collection method endpoint body / notes output 1 make device backup post {{lem url}}/api/v1/backup/init backup?projectid={{project id}}\&deviceid={{edge device id}} no body asynchronous backup runs on the device { "code" "200", "content" null } 2 list backups get {{lem url}}/api/v1/backup/list?projectid={{project id}}\&deviceid={{edge device id}} poll until the new entry appears list with timestamp and backuptype (typically master ) 3 get pre signed s3 url to backup post {{lem url}}/api/v1/backup/get?projectid={{project id}}\&deviceid={{edge device id}}\&backuptype=master\&timestamp={ts} pre signed s3 get url valid 7 days 4 (optional, cross tenant) save backup to pre signed s3 url post {{lem url}}/api/v1/backup/put? used only when relocating the dat to a different s3 location new pre signed put url 5 restore from backup post {{lem url}}/api/v1/backup/init restore?projectid={{project id}}\&deviceid={{target edge device id}}\&backuptype=master\&timestamp={ts} deviceid query param can target a different device than the source restore initiated on target device distinct from "lem backup" this chain backs up a single edge device ( /api/v1/backup/ ) to back up the lem instance itself, use admin console > admin console settings > backup ( /admin/v1/lem backup/ ) auth all calls use x authtoken {{lem adminapitoken}} the pre signed s3 url from step 3 carries sigv4 query params and needs no auth header