Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  1. Fotoware Alto
    • 11.14 Schreckhorn
    • Terminology
    • Solutions
    • User Guide - Deutsch
    • User Guide - English
    • API Changelog
  2. Fotoware Veloz
    • Managing users and groups
    • Configuring archives
    • Configuring workflows
    • Configuring site behavior
    • Navigating and searching to find your assets
    • Working with your assets
    • Editing asset metadata
    • Uploading files
    • Version Control in Fotoware
    • Albums - Creating and sharing collections
    • Placing assets in a CMS
    • Working with the Fotoware Pro interface
    • Using the Fotoware plugins
    • Consent management
    • User guide to FotoWeb for iPad (Legacy)
    • Picture conferencing with FotoWeb Screens (Legacy)
    • What's what in Fotoware
    • GDPR
    • Fotoware Veloz releases
    • Activity Exports
    • Fotoware Example Workflows
  3. Fotostation
    • Getting started with Fotostation
    • Viewing, selecting and sorting files
    • Managing your assets with archives
    • Adding metadata to assets
    • Searching for assets
    • Working with your assets
    • Version Control in Fotostation
    • Automating tasks with Actions
    • Configuring metadata fields and editors
    • Configuring Fotostation
    • Configuring Fotostation for multi-user environments
    • Troubleshooting Fotostation
  4. Fotoware Flow
    • What is Flow?
    • Getting started
    • Flow dictionary
  5. Fotoware On-Premises
    • Getting started
    • Index Manager
    • FotoWeb
    • Color Factory
    • Connect
    • Operations Center Guide
  6. Integrations and APIs
    • The Fotoware API
    • Creating integrations using embeddable widgets
    • Authorizing applications using OAuth
    • Auto-tagging
    • FotoWeb Drag and Drop export
    • Integration using webhooks
    • Optimizely and Episerver plugin documentation
    • User Interface Integrations
  7. Fotoware Mobile
    • User guide for Fotoware Mobile for iPhone and Android
    • User guide to FotoWeb for iPad (Legacy)
    • User guide to FotoWeb for iPhone and Android (Legacy)

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Support

Table of Contents

What needs backing up? Assets Configuration files Autogenerated data Backing up assets Backing up configurations Fotoware ProgramData FotoWeb site configuration(s) Microsoft SQL and MongoDB databases Backing up autogenerated data (optional) Autogenerated data that can be backed up: Audio and video proxy files (configurable location) Index Manager cache (configurable location) FotoWeb cache (configurable location) Index Manager's indexes Restoring the system from a backup Restoring the Mongo DB
  • Home
  • Fotoware On-Premises
  • Getting started
  • Maintaining and tuning your system (On-Premises)
  • Reference library

Backing up a Fotoware system

30. April 2025

Elaine Foley

Table of Contents

What needs backing up? Assets Configuration files Autogenerated data Backing up assets Backing up configurations Fotoware ProgramData FotoWeb site configuration(s) Microsoft SQL and MongoDB databases Backing up autogenerated data (optional) Autogenerated data that can be backed up: Audio and video proxy files (configurable location) Index Manager cache (configurable location) FotoWeb cache (configurable location) Index Manager's indexes Restoring the system from a backup Restoring the Mongo DB

There are multiple levels at which the system can be backed up. If the FotoWeb server is virtualized, backing up the entire image is a simple solution.

Using backup software, it is also possible to make a complete backup of a physical server and then roll back to a previous server state through a restore operation.

At a lower level, file-based backup requires you to know which folders you need to back up to facilitate disaster recovery. That is the focus of this topic.

What needs backing up?

Assets

All the assets in the system need to be backed up. Often, these will reside on a shared network volume, such as a SAN, and there will often be separate backup routines that handle the safeguarding of the SAN data.

The XMP metadata that is stored with assets in a Fotoware system is either embedded in the actual files or travels with the files as "sidecars" - that way, it is sufficient to back up the assets to also include any XMP metadata that has been added to the files.

Configuration files

The configuration files need to be restorable within a reasonable amount of time. Configurations tend to grow over time, so these files should be regularly backed up to make sure the most recent version of the configuration can be restored in a disaster recovery scenario.

Autogenerated data

Autogenerated data includes indexes, caches, and audio/video proxies. Although these can be regenerated automatically, including these in a restore operation will reduce the extra processing required to regenerate these files and make the system perform its best quickly after completing the restore operation.

Backing up assets

We recommend using commercially available backup tools to back up assets.

In the context of the Fotoware system, all assets crawled and indexed by Index Manager need backing up. With a FotoWeb system, there will typically also be a global upload area that requires backing up. The default location for the upload area is C:\ProgramData\Fotoware\FotoWeb\Operations\Upload\[SITENAME]

Backing up configurations

Fotoware ProgramData

All Fotoware server applications store their configuration files in C:\ProgramData\Fotoware

We recommend making a backup copy of this folder using an external scheduled task.

FotoWeb site configuration(s)

The default path to the site configuration is C:\ProgramData\Fotoware\FotoWeb\Site Settings\[SITENAME]. Note that the location of the site home folder is configurable, so if you're unsure which folder has been chosen as the site's home folder, go to the FotoWeb site configuration in the Operations Center and check the site identification settings.

These files should be backed up to a safe location. With multiple sites on the server, ensure all sites are backed up.

Microsoft SQL and MongoDB databases

FotoWeb uses MongoDB and Microsoft SQL databases. Backing these up is not as plain as copying a number of files from a to b.

These databases can be configured to create automatic backups. The backed-up files are, by default, stored in these locations to allow copying them to a safe location:

SQL server backup files: C:\ProgramData\Fotoware\FotoWeb\Site Settings\[SITENAME]\Backup

MongoDB backup files: C:\ProgramData\Fotoware\FotoWeb\Server Settings\Backup

Backing up autogenerated data (optional)

Autogenerated data, such as indexes, caches, and audio and video proxy files, are files that can be re-generated after a restore operation, so they are not critical. However, because regenerating these files from scratch can be time-consuming and will put a performance penalty on the server while being generated, including these in the backup and restore routines is recommended if getting quickly back up and running is a priority.

Autogenerated data that can be backed up:

Audio and video proxy files (configurable location)

Default location: C:\ProgramData\Fotoware\FotoWeb\Operations\Proxies

Index Manager cache (configurable location)

Default location: C:\ProgramData\Fotoware\Index Manager\ImCache

FotoWeb cache (configurable location)

Default location: C:\ProgramData\Fotoware\FotoWeb\Operations\Cache\[sitename]

Index Manager's indexes

Check where the indexes are stored in the Index Manager configuration through the Operations Center.

Restoring the system from a backup

  • All data except databases can be copied back to their original location on the server.
  • To restore FotoWeb's Microsoft SQL database, use the FotoWeb Administration Console application, found on the Windows start screen:
    • Expand the Server node and right-click on the Site node.
    • Choose All tasks - Restore database
    • Enter the user name and password for the database, or use a trusted connection, then press OK.

Restoring the Mongo DB

Important: FotoWeb must be running before the Mongo restore operation can start.

To restore the Mongo database, run the following command:

"C:\Program Files (x86)\Fotoware\FotoWeb\MongoDB\mongorestore.exe" /drop /uri:"mongodb://localhost:7200" "PATH_TO_MONGODB_BACKUP"
system backup data protection

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Installing Index Manager
  • Application registration using OAuth 2.0
  • Authorizing a client using OAuth 2.0
eco-lighthouse-miljøfyrtårn

Company

  • About us
  • Resellers
  • Careers
  • Contact us

Help & support

  • Support center
  • Consultancy
  • Tech partners
  • Fotostation
  • System status

Trust Center

  • Legal
  • Security
  • Sustainability & ESG

Locations

Fotoware AS (HQ)
Tollbugata 35
0157 OSLO
Norway
FotoWare Switzerland AG
Industriestrasse 25
5033 Buchs (AG)
Switzerland

Copyright 2025 Fotoware All rights reserved.

  • Terms of service
  • Privacy policy
  • Cookie policy

Knowledge Base Software powered by Helpjuice

Expand