Saving Files

In this article

    You can save backed-up Microsoft Teams files.

    When you save files, the request command archives the files and places the ZIP archive to a temporary folder on the Veeam Backup for Microsoft 365 server. After that, the archive is transferred as application/octet-stream media to the client. To download, read or perform other actions with the octet-stream, use features of programming languages.

    Saving Files Tip

    You can use Swagger UI to download data from the stream by clicking the Download action link in the response body. For more information, see Evaluation in Swagger UI.

    Request

    POST https://<hostname>:4443/v6/RestoreSessions/{restoreSessionId}/organization/teams/{teamId}/files/save

    Request Headers

    The request header must contain an authorization token of the current session.

    Request Parameters

    The following parameters must be specified in the URL of the request:

    Parameter

    Type

    Description

    restoreSessionId

    string

    Specifies the identification number of the restore session. For more information on how to get this parameter, see Getting Restore Sessions.

    teamId

    string

    Specifies the identification number of the team. For more information on how to get this parameter, see Getting Teams.

    Request Body

    Saving Files Note

    Files are always saved in a ZIP archive.

    You must specify one of the following properties in the request body:

    Property

    Type

    Description

    channelId

    string

    Specifies the ID of the channel whose files you want to save. Veeam Explorer for Microsoft Teams will save all files of this channel.

    You do not need to use this property if you use the files property to specify what files to save.

    files

    file[]

    Specifies the IDs of files that you want to save. The files must reside in the same channel. You do not need to use this property if you use the channelId property to specify a channel whose files to save. For more information on how to get such IDs, see Getting Files.

    Request Example 1

    The following example shows how to save backed-up files of a specified channel.

    Request Body:

    {
       "channelId": "19:94e57dbfaa634f999353b374b69b5800@thread.tacv2"

    }

    Request Example 2

    The following example shows how to save the selected backed-up files.

    Request Body:

    {

       "files": [

       {"id": "94e5f006-77da-4c52-8f1e-1051a195844a"},

       {"id": "1c750ff5-f22f-4c42-8522-97925a5a2e5e"}

       ]

    }

    Response

    The server returns the following response to the client.

    Response Codes

    A successfully completed operation returns response code 200 OK.

    Response Headers

    The response to this request contains the following headers. The response may also include additional standard HTTPS headers.

    Header

    Description

    Content-length

    The length of the response body.

    Content-type

    The media type and syntax of the response body message for the requests with the export and save actions: application/octet-stream.

    The media type and syntax of the response body message for the requests with the restore and send actions: null.

    Response Body

    In the response body, the server returns binary data stream.

    Example

    The example shows how to save backed-up files with the IDs 94e5f006-77da-4c52-8f1e-1051a195844a and 1c750ff5-f22f-4c42-8522-97925a5a2e5e.

    Request:

    POST https://abc.tech.local:4443/v6/RestoreSessions/380d7caf738d3d9f-268b-435b-93e2-64e70f8032b6/organization/teams/448c5b66-8dcd-4c75-b636-d3b500bce36f/files/save

     

    Request Header:

    Authorization: Bearer <Access-Token>

     

    Request Body:

    {

       "files": [

       {"id": "94e5f006-77da-4c52-8f1e-1051a195844a"},

       {"id": "1c750ff5-f22f-4c42-8522-97925a5a2e5e"}

       ]

    }

     

    Response:

    200 OK