In order to run this process a scheduled Backup must be in place and must have run at least one time. Please follow the steps below to successfully move the file location of your Backup Job.
1.Select the backup job for which you wish to move the file location - the backup jobs are found in the Backup Navigator panel.
2.Right click on the backup job and select Delete, or click the Delete button from the Backup Navigator ribbon.
3.On the Confirm Backup Delete pop-up, click Ok. Do not check the box to delete content.
4.On the Summary pop-up, click Ok.
5.Restart the Essentials Console.
6.Go to the View tab within Essentials and Select Scheduler.
7.Select the Task that you are moving and choose the Edit Script option from the bottom menu.
NOTE: If your Backup Job was created before July 20, 2015 Select Script to edit the Script. If your Backup Job was created on July 20, 2015 or after select Edit Script to make changes to the Script.
8.A script window will appear. Within the script find the portion that refers to the project folder location (for example: "C:/Users/username/Essentials/.metadata/tasks/SharePoint-Backup.cmd"), and change the location to where you want the Backup to be saved. Close the script window once you have made your changes.
9.Go to the location of the original Backup and Cut and Paste the entire Archive Folder from the old location to the new location.
10. Restart Essentials and then use the steps for Importing Backup Archives to link the Tool to the new Backup Location.
11. Run the Backup from the Scheduler by selecting the job and clicking Run in order to make sure the Backup runs without error.
If you do run into any errors contact Support and we will help you with any issues.
Essentials uses the Apache Derby Database when creating a backup on File System Storage. Its an open source relational database implemented entirely in Java. No extra tools or services are required to be installed. (https://db.apache.org/derby/)
For Azure Storage, Essentials uses the Table Storage Service - a NoSQL key-value store for rapid development using massive semi-structured datasets. In order for this to work, you must have the Table Storage Service. (https://docs.microsoft.com/en-us/azure/storage/tables/table-storage-quickstart-portal)
For Amazon S3 storage, Essentials requires you to have the Amazon DynamoDB service. Amazon DynamoDB is a key-value and document database that delivers single-digit millisecond performance at any scale.
If you use Amazon S3 storage with Custom End points in Essentials with Amazon DynamoDBLocal service, then you do not require an amazon DynamoDB. This is because the DynamoDB databases are placed locally on the file system and synchronize with backup project located on Amazon S3 storage. (https://docs.aws.amazon.com/en_us/amazondynamodb/latest/developerguide/DynamoDBLocal.html)
This section provides an overview of importing and exporting backup archives.
Metalogix Backup allows users to export/import projects to/from external archives.
To export a Backup project:
1.In the Backup Navigator panel, navigate to the backup project that you would like to export, select the object that you would like to export and right click on it and select Export.
Alternatively, you can select the object that you would like to export and click the export button in the Backup Navigator ribbon.
2.In the provided window select a location where the export will be saved. You may also select to split the export into multiple files and/or add a password to the export file.
3.Press Finish to Start the Export.
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Nutzungsbedingungen Datenschutz