SQL Safe allows you to modify any of the default settings of the application, and you can change your Management Console Preferences at any time. To access this option, go to the Tools menu and select the respective option. The window for Management Console Preferences allows you to modify settings in the following categories:
What Backup settings can you change?
On the Backup tab, you can set the default parameters that appear on the Backup Wizard. Set the default parameters to the values you typically use. If you want to use different settings on any given backup, you can still make changes to the wizard itself.
The parameters you can set include the following:
- Backup archives location.
- Tivoli Storage Manager backup archives location.
- Default compression and encryption algorithms.
- Generating maps containing metadata for use with InstantRestore and SQL virtual database.
- Auto-generated backup file names.
- The number of threads employed in a backup.
What Agent Deployment settings can you change?
On the Agent Deployment tab, you can identify the service account used to run the agents. Choose whether or not you want to automatically upgrade the Backup Agents and the XSP if you upgrade to a new SQL Safe version. You can also set the timeout from 30 to 600 seconds for the SQL Safe Agent upgrade operation.
What User Experience settings can you change?
On the User Experience tab, you can:
- Enable automatic refresh on the screen and set the number of seconds between each refresh.
- Change display settings for server status.
- Set the Total Cost of Ownership parameter necessary to calculate your return on investment.
- Configure troubleshooting settings.
What Policy Data settings can you change?
On the Policy Data tab, you can define the location of your policy data files.
By default, policy data files are stored in the C:\InstallPath\SQL Safe\PolicyData folder, but you can use this option to specify a different location. Click Local Path and browse the folder where you want to store your policy data files or select the respective option for creating a new folder.
By default, each agent uses its own installation directory to store policy data. If a custom location cannot be created on a specific server, the Backup Agent will use <InstallPath>\PolicyData.
What Amazon S3 Cloud settings can you change?
On the Amazon S3 Cloud tab, you can:
- Specify the Access Key generated in the security credentials of your Amazon S3 web console. For more information, click here.
- Specify the Secret Key generated in the security credentials of your Amazon S3 web console. For more information, click here.
- Select the region where your information will be stored. You can find more information about these regions here.
- Set the Bucket Name where your backup will be stored.
- Set the SubFolder(s) (Optional) where your backup will be stored or restored from. Consider the following situations:
- If the SubFolder field is left empty, the backup file will be saved in the root of the specified container.
- If the SubFolder field is populated with the name of a folder that does not exist on the storage container \ bucket, the folder will be created and the backup file will be saved to the specified Subfolder.
- Multiple SubFolders can be specified by separating each folder with a forward slash: MyFolder/MySubfolder/MyNestedFolder.
- The SubFolder field can contain static values as well as tokens like %instance%, %database%, %backuptype%, %policyguid%, and %timestamp%.
- The storage class is currently locked to the 'Standard' class and cannot be changed.
- Specify the Part Size in megabytes of the backup file that will be sent to the bucket simultaneously.
The default value for File Size is 10 MB.
- Specify the Temporary Download Location to improve resiliency and performance when downloading large backup files from Amazon S3 Cloud Storage. This location will be displayed when the "Download File from Cloud" option is checked in a restore wizard or restore policy.
When Amazon cloud settings are set in the Management Console Preferences, they can be used in backup and restore operations.
What Azure Cloud settings can you change?
On the Azure Cloud tab, you can:
- Specify the name of the Azure Container where the new blob will be created and the backup stored. Every Azure blob must reside in a container. The container forms part of the blob name. If no container with the input name exists, a new one will be created. For more information, click here.
- Specify the Azure Storage Account Name of your storage account. Every object that you store in Azure Storage has a unique URL address. The storage account name forms the subdomain of that address. You can find more information on the following link.
- Specify the Access Key provided to your Azure Storage Account. For more information about Azure Keys, click here.
- Set the SubFolder(s) (Optional) where your backup will be stored or restored from. Consider the following situations:
- If the SubFolder field is left empty, the backup file will be saved in the root of the specified container.
- If the SubFolder field is populated with the name of a folder that does not exist on the storage container \ bucket, the folder will be created and the backup file will be saved to the specified Subfolder.
- Multiple SubFolders can be specified by separating each folder with a forward slash: MyFolder/MySubfolder/MyNestedFolder.
- The SubFolder field can contain static values as well as tokens like %instance%, %database%, %backuptype%, %policyguid%, and %timestamp%.
- Define the Azure Sector Type:
- Public - commercial cloud storage solution.
- Government - cloud storage solution offered to US government customers and their partners.
- Specify the Authentication Type:
- Key
- SAS (Shared Access Signature Service URL).
- Specify the Part Size in megabytes of the backup file that will be sent to the bucket simultaneously.
The default value for File Size is 10 MB.
- Specify the Temporary Download Location to improve resiliency and performance when downloading large backup files from Microsoft Azure Blob Storage. This location will be displayed when the "Download File from Cloud" option is checked in a restore wizard or restore policy.
When Azure settings are set in the Management Console Preferences, they can be used in backup and restore operations.
What S3 Compatible settings can you change?
On the S3 Compatible tab, you can:
- Specify the Access Key generated in the security credentials of your Amazon S3 web console. For more information, click here.
- Specify the Secret Key generated in the security credentials of your Amazon S3 web console. For more information, click here.
- Specify the REST Endpoint (IP:Port) with its respective signature.
- Set the Bucket Name where your backup will be stored.
- Set the SubFolder(s) (Optional) where your backup will be stored or restored from. Consider the following situations:
- If the SubFolder field is left empty, the backup file will be saved in the root of the specified container.
- If the SubFolder field is populated with the name of a folder that does not exist on the storage container \ bucket, the folder will be created and the backup file will be saved to the specified Subfolder.
- Multiple SubFolders can be specified by separating each folder with a forward slash: MyFolder/MySubfolder/MyNestedFolder.
- The SubFolder field can contain static values as well as tokens like %instance%, %database%, %backuptype%, %policyguid%, and %timestamp%.
- Select the Storage Class: Standard, Standard-IA, and OneZone-IA. This setting is optional. The default value is Standard.
- Specify the Part Size in megabytes of the backup file that will be sent to the bucket simultaneously.
The default value for File Size is 10 MB.
- Specify the Temporary Download Location to improve resiliency and performance when downloading large backup files from Amazon S3 Cloud Storage. This location will be displayed when the "Download File from Cloud" option is checked in a restore wizard or restore policy.
When Amazon cloud settings are set in the Management Console Preferences, they can be used in backup and restore operations.