The Locations tab of the SQL Safe Backup wizard allows you to specify the backup location you want to use to store the backup set. For a TSM backup, you can change the TSM connections settings to override the values set in the client options file if you need to write the backup files to a TSM Server other than the TSM Server already specified in the dsm.opt file.
You can select the location type and the UNC or full path of an existing archived backup set.
If you do not have an existing archive file, SQL Safe creates a new archive file that includes this backup set, using the name you specified.
You can Append to an existing archived backup set or choose to Overwrite it.
To specify a UNC, type the UNC path directly in the field. You cannot specify a UNC when using the browse option.
Using a UNC path allows you to restore backups to a different or new server from the original archive. |
SQL Safe supports the following location types:
Location Type | Action |
---|---|
Single File | Enter the name of the backup archive. |
Striped Files | Enter as many backup archive names as the number of striped files you want. When backing up SQL Server 2000 databases, consider using as few striped files as possible since a high number of striped files can significantly degrade performance due to SQL Server memory allocation. |
Tape | Enter the path of the TSM configuration file and the Object Name. |
If you want to take advantage of distributing I/O overhead for a large database, select striped files, and select backup locations on different local disks.
When backing up SQL Server 2000 databases, consider using as few striped files as possible since a high number of striped files can significantly degrade performance due to SQL Server memory allocation.
Click Enable Resiliency and access the Network Resiliency Settings window where you can specify how often you want to retry when errors occur and after how much time the operation will fail. You can also configure how much time is allowed for the total retry time of the backup.
Click Mirroring Archives, and then specify where you want the mirror copies to be stored.
For each mirror, SQL Safe creates a copy of the backup archive set. You can specify up to 2 mirrors for each backup operation. Keep in mind that creating mirrors can impact the performance of your backup operation.
If you want to stop the backup operation when the mirror location is unavailable, select the corresponding option.
Select Retry writing backup files after network errors, and then click Configure to change the default settings. By default, SQL Safe will retry the backup operation every 10 seconds and then fail after 5 minutes (300 seconds) of continuous errors. Also, over the course of the operation, SQL Safe allows a total of 60 minutes in which to retry the backup before stopping the operation.
This option is not available when backing up to tape using Tivoli Storage Manager.
When a TSM location is selected, you must specify the following settings:
You can change the TSM connections settings to override the values set in the client options file. You can also configure SQL Safe to mark these files as inactive after a specified age.
Note that SQL Safe accepts up to 260 characters for the TSM file path name. |
Yes. Under TSM Client Settings, specify the name of the node you want to use and the password required to access the node.
Click Change to specify the node name, the password required to access the node, and the TCP/IP Server address and port.
IDERA Website | Products | Purchase | Support | Community | About Us | Resources | Legal |
---|