4 4 3 Grolar:OwnCloud Single File Restore

From SEPsesam
Draft.png WORK IN PROGRESS
This article is in the initial stage and may be updated, replaced or deleted at any time. It is inappropriate to use this document as reference material as it is a work in progress and should be treated as such.

Copyright © SEP AG 1999-2024. All rights reserved.

Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.

Docs latest icon.png Welcome to the latest SEP sesam documentation version 4.4.3/4.4.3 Grolar. For previous documentation version(s), check SEP sesam Archive.


Overview

SEP sesam enables you to restore single files from your ownCloud backup. Note that only ownCloud without server-side encryption is supported.

Restore tasks can be saved, scheduled and run automatically in continuous intervals to check and control data integrity. For details, see Scheduling Restore.

Configuring ownCloud restore

A restore task involves browsing and selecting the desired save sets by time and task/filename, selecting restore type and restore target, enabling post interface for the client that runs ownCloud and specifying a special command for the post script.

Prerequisites

  • Depending on what you want to restore, make sure that you have the proper restore permissions and access rights.
  • Make sure that there is sufficient free space on the target system to which you are restoring your data.
  • Prepare a special routine to scan the recovered files after a restore via the sbc_pre interface
  • To use a pre/post interface, you have to activate it first and create a command as shown below. In the GUI menu bar, click Configuration -> Interfaces, select the Post interface, and then select the Restore interface and your ownCloud client.
  • Configure owncloud post restore.png Configure owncloud post restore-2.png Configure owncloud post restore-3.png

  • In the interface script window, add the following command
  • sudo -u "userThatOwnsOwnCloudDir" php "pathToOwnCloudDir"/occ files:scan -all under the line: #=== Please insert your specific actions here================== where "userThatOwnsOwnCloudDir" must be replaced by the user that owns the ownCloud directory
    and "pathToOwnCloudDir" must be replaced by the location of the ownCloud directory. For example, on a Debian with Apache2 and ownCloud located in /var/www/, the command would be: #=== Please insert your specific actions here================== sudo -u www-data php /var/www/owncloud/occ files:scan -all Configure owncloud post restore-command.png

  • Once done, click Save to activate the interface. The interface is saved to the <SESAM_ROOT>/bin/sesam directory. For details, see Using Pre and Post Scripts.
  • Steps

    You should look at the standard restore procedure for general instructions on how to configure a restore task. The following procedure shows only ownCloud-specific steps when configuring a restore task.

    1. From the SEP sesam GUI menu bar, select Activities -> Restore -> select the save set for restore. In the third step of the wizard: Select task, from the list of the save sets click the desired backup version from which you want to restore restore, and then click Next.
    2. Rst owncloud-select bck task.png
    3. In the Select files dialog, select the data you want to restore and click Next.
    4. Rst owncloud-select file.png
    5. In the Save and start step of the restore wizard, click Expert options and then select the tab Pre/Post. Select the check box Execute Post to enable running the post script for this task. Click OK and then Save.
    6. Rst owncloud-enable post.png

    You can view the status of your restore jobs by selecting Job state -> Restore from the Main selection. Restore overview provides detailed information on the last run of restore jobs, including the task name, status (successful, error, in queue ...), start and stop time of the last backup, data size, throughput, client and message.

    See also

    ownCloud Backup