Source:FAQ - Backup

From SEPsesam
Other languages:

Which backup strategy is recommended to implement with SEP sesam?

You can implement various backup strategies with SEP sesam, such as the 3-2-1 backup strategy and its variations, the GFS backup rotation strategy, and the D2D2T strategy. However, it is recommended to keep backup copies both locally and externally (on tape, hard disk, in the cloud, etc.) to quickly and seamlessly recover lost data and ensure business continuity when all preventive measures fail. Before implementing the backup strategy, ensure that you select the one that is appropriate for your unique business needs. For details, see Backup Strategy Best Practices.

Is data that is collected for backup stored in a flat file or a database?

Data is stored in a flat file, but information about the backup is stored in the SEP sesam database, including index pointers for fast and easy data recovery.

Does SEP sesam back up open files?

Yes, SEP sesam can back up open files on both Linux and Windows systems as regular Path backups.

On Windows, open files can be backed up using SEP sesam Volume Shadow Copy Service (VSS). To perform an open file backup, a Windows snapshot is made of the data and partition intended for backup and the partition is backed up. Databases should only be backed up using the relevant SEP sesam database module, see SEP sesam Extensions. For details on VSS, see SEP sesam Volume Shadow Copy Service (VSS) for Windows.

Does SEP sesam perform incremental backups after the initial backup?

Depending on your backup strategy, SEP sesam can be set to perform any backup level in the desired sequence.

Are backups performed directly to disk or tape? How about cloud backup?

Backups can be written directly to different backup media such as disk, tape and cloud. The ability to move data between physical servers, virtual machines, and the cloud is a key for a successful backup strategy. All backup functions are written and/or controlled by the server and may be written directly to the backup disk, tape, remote tape server, or cloud.

  • SEP sesam supports disk-to-disk-to-tape (D2D2T) functionality and can also write directly from the backup tape to the server. It supports virtual tape libraries on disk with a pseudo autoloader function as well as removable disk media.
  • SEP cloud backup and recovery enables you to back up and replicate physical and virtual data to the cloud without having to build offsite infrastructure. For details, see S3 Cloud, HPE StoreOnce, Si3 Deduplication and Si3 Replication.

When several users save the same file on separate clients, does SEP sesam back up all the files?

For example, if members of a work group save the same file to their respective desktops, does SEP sesam make separate copies of the file or a single file with pointers to the changes?

Typically, SEP sesam stores separate files for each user, unless you are using the SEP Si3 target deduplication. With SEP Si3 target deduplication only one instance of the same data is stored directly on backup media. Si3 deduplication can be easily configured, but it also requires a special license. For explanation, see SEP Si3 target deduplication and SEP sesam extensions.

How to set up an Si3 deduplication store for replication?

Information sign.png Note
The Initial Seed feature does not work in v. 5.0.0 Jaglion, but you can use it in earlier SEP sesam versions. Note that SEP is working on this issue and will provide a fix as soon as possible.

The easiest way is to use the initial seed functionality – you can import the preconfigured Si3 deduplication store and use it for replication. When replicating from origin to new Si3 store, the savesets on the new Si3 deduplication store are identified and the content of the new Si3 store is updated in the SEP sesam database. For details, see Seeding Si3 Deduplication Store.

How are archive bits processed?

On Windows, archive bits are used for full and copy backups. The archive bits are treated the same for both backup levels.

Note that the archive bits are not deleted on Windows systems. If you want to force-reset of the archive bits, you can enter the following command in the backup task properties (Options tab -> Backup options field):

-o clear_archive

You can also add the files with the Archive ready attribute as follows:

-o add_archive_ready

To set the use of archive bits, proceed as follows:

sql "update defaults set value= 'yes' where key= 'with_archive_bit'"

Can I back up MS SQL/MS Exchange with the Volume Shadow Copy (VSS) functionality of Microsoft Windows?

Yes, the VSS functionality can be used to back up MS SQL or MS Exchange environments, but it is only recommended for small installations.

There are two strategies for consistently backing up a running MS Exchange or MS SQL environment:

  1. Using the SEP sesam online extensions for MS Exchange or MS SQL. For details, see MS Exchange Backup and MS SQL Backup.
  2. A regular file system path backup with the activated VSS writer for MS Exchange or MS SQL. For details, see SEP sesam Volume Shadow Copy Service (VSS) for Windows.
Information sign.png Note
The backup of MS Exchange or MS SQL environments via VSS is a viable option to get a consistent backup of the running environment as long as the data volume is not too large. It is an alternative for small environments with 1-5 users. However, in critical productive environments you should use the SEP sesam online extensions for MS Exchange/MS SQL to ensure consistent backup and restore.

SEP sesam online extensions

  • Dedicated backup of Groupware data/database data, independent of the files in the file system.
  • Available are FULL, DIFF (differential) and INCR (incremental) backup levels.
  • Provide granular backup of single databases and database instances.
  • Backup of the transaction log – other systems accessing the database are aware that a backup is performed.
  • Restore of the database/Groupware data only (without files from the file system).
  • Provide granular restore of single instances and databases. In a restore scenario, there is no need to restore the complete database – this is beneficial for larger databases/Groupware systems.
  • Perform online restore.

Backup via the Microsoft VSS Writer

  • The Volume Shadow Copy (VSS) functionality of Microsoft Windows is included in the regular SEP sesam file backup agent for Microsoft Windows. It also supports the VSS backup of MS Exchange and MS SQL.
  • A VSS-based backup of a database/Groupware system is always a file system backup. If the file backup agent starts backing up a file system with a MS SQL/MS Exchange database, the VSS functionality is used to inform the database about the backup. The database/Groupware system delivers the data consistently.
  • A VSS backup of a database/Groupware system always backs up all of the data. Incremental or differential backups are not supported and the backup of single databases or single instances is also not supported.
  • A database-only restore cannot be performed because the database/Groupware system is part of the complete file system backup, therefore the complete file system backup must be restored in order to restore the database.
  • Restore of single instances or single databases is not supported.
  • The transaction log file is not backed up – other applications are not informed about the backup of the database.

To enable a consistent restore in distributed environments, the different components must be informed if a backup of one of the systems is performed. For example, in a SharePoint Server environment, the database and mail server run on different servers. A VSS backup of a single server will result in an inconsistent restore. In this case, only the backup with the SEP sesam dedicated online extension can guarantee consistent data.

What is the difference between a GroupWise backup with the SEP sesam online extension and one without the extension on an OES Server?

There are two ways to back up a Micro Focus (formerly Novell) GroupWise Server with SEP sesam. You can use the SEP sesam GroupWise extension or the administrator can perform a TSA based file-level backup of the GroupWise Server.

In general, the backup of a GroupWise Server is always performed via TSA interface, either via tsafsgw or tsafs (gw-enabled). There is no difference between the two backup options. The difference is in the management of the backup and restore jobs.

For details on SEP sesam backup in a Micro Focus (formerly Novell) NetWare/OES environment, see Backup principles using SEP sesam in a Micro Focus OES environment.

For file-based backup and restore, you will need qualified knowledge of the GroupWise environment and the management of GroupWise systems. With the SEP sesam GroupWise online extension, the backup and – more importantly – restore of GroupWise systems can be performed by an administrator without any knowledge of the GroupWise environment.

Backup with SEP sesam GroupWise extension

When a new backup job is being defined for a client, the SEP sesam extension automatically recognizes that GroupWise is running on the client and offers the administrator a GroupWise backup. The administrator does not need to know where the GroupWise data is stored or which files are to be backed up.

The backup is started as a GroupWise backup process and is clearly identified as such. The SEP sesam Server recognizes that this is a GroupWise backup and not a normal file backup. This makes management and problem location (in the event of a problem) much easier. Technically, it is only a file backup but the SEP sesam agent ensures that the right files are backed up from the right directories.

The scenario for a restore is similar. The SEP sesam GroupWise extension recognizes the backup (technically a file backup) and is aware that all the files belong together to a GroupWise system. The SEP agent then restores all the relevant files to the GroupWise restore area on the GroupWise Server. Based on the data in the GroupWise restore area, GroupWise can start a recovery process to restore the data (mail or mailboxes). The administrator does not need to know which files need to be restored or where they should be restored to.

Backup without SEP sesam GroupWise extension

Backing up a GroupWise system without the SEP sesam GroupWise extension is performed much like a regular file backup. GroupWise is shown as a regular NSS volume in the file system with its volume name. The administrator needs to know:

  • which is the GroupWise volume
  • which files within the volume need to be backed up

The backup process itself starts as a file backup process. For the restore, the administrator needs to know:

  • which files need to be restored
  • the location of the GroupWise restore directory
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.