LiteSpeed for SQL Server 8.8

Displays available TSM management classes with detailed information. If you specify a management class, the information returns only to the specified management class.

This topic covers:

Syntax
Arguments
Result Set
Returns

Syntax

EXEC master.dbo.xp_view_tsmmc
@tsmclientnode = 'TSM_client_node'
, @tsmclientownerpwd = 'TSM_client_owner_password'
, @tsmconfigfile = 'TSM_configuration_file'
[, @tsmmanagementclass = 'TSM_management_class']

Arguments

@tsmclientnode

Specifies the TSM server LiteSpeed connects to during backups and restores. Not required, if specified in the options file or if backing up with the Passwordaccess Generate option.

@tsmclientownerpwd

Specifies the TSM client owner user password. Not required, if specified in the options file or if backing up with the Passwordaccess Generate option.

@tsmconfigfile

Specifies the TSM configuration file.

You can use the %TSMDEFAULTPATH% variable to make LiteSpeed detect the default TSM configuration file path automatically (by getting from LiteSpeed defaults as a priority or the registry - HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\BackupClient)

@tsmmanagementclass

Specifies the TSM management class. If not specified, LiteSpeed uses the default management class.

Result Set

Column Name	Data Type	Description
Name	Nvarchar(128)	Management class name.
Backup copy group name	Nvarchar(128)	The name of the backup copy group.
Backup copy group destination	Nvarchar(128)	Names the destination where backups are stored. The destination can be either a storage pool of disk devices or a storage pool of devices that support removable media, such as tape.
Versions data exists	Nvarchar(128)	Specifies the maximum number of different backup versions retained. If you select a management class that permits more than one backup version, the most recent version is called the active version. All other versions are called inactive versions. If the maximum number of versions permitted is five, and you run a backup that creates a sixth version, the oldest version is deleted from server storage.
Versions data deleted	Nvarchar(128)	Specifies the maximum number of different backup versions retained for files and directories that you erased from your drive. This parameter is ignored as long as the file or directory remains on your drive. If you erase the file or directory, the next time you run an incremental backup, the active backup version is changed to inactive and the oldest versions are erased that exceed the number specified by this parameter.
Retain extra versions	Nvarchar(128)	Specifies how many days all but the most recent backup version is retained. The most recent version is the active version, and active versions are never erased. If Nolimit is specified, then extra versions are kept until the number of backup versions exceeds the versions data exists or versions data deleted parameter settings. In this case, the oldest extra version is deleted immediately.
Retain only versions	Nvarchar(128)	Specifies the number of days the last remaining inactive version of a file or directory is retained. If Nolimit is specified, the last version is retained indefinitely. This parameter goes into effect during the next incremental backup after a file is deleted from the client machine. Any subsequent updates to this parameter will not affect files that are already inactive. For example: If this parameter is set to 10 days when a file is inactivated during an incremental backup, the file will be expired in 10 days.
Archive copy group name	Nvarchar(128)	The name of the backup copy group.
Archive copy group destination	Nvarchar(128)	Names the destination where archives are stored. The destination can be either a storage pool of disk devices or a storage pool of devices that support removable media, such as tape.

Returns

0 (success) or non-zero (failure).

To capture the output message, run the following:

declare @rmsg varchar(999)
exec master..<procedure_name> <arguments>, @resultmsg=@rmsg output
select @rmsg

To capture the output message and the result code, run the following:

declare @rc int
declare @rmsg varchar(999)
exec master..<procedure_name> <arguments>, @resultmsg=@rmsg output, @resultcode=@rc output
select @rc, @rmsg

Troubleshoot LiteSpeed

Refer to the Release Notes for the current list of issues known to exist in this version of LiteSpeed.

Troubleshoot LiteSpeed Activity

Local repository is not populated

If the computer name is changed, the local repository settings are not found, because LiteSpeed refers to the old computer name. As a result, the Local Repository database is not being populated and you cannot view LiteSpeed activity.

You need to update @@SERVERNAME for all instances on that computer and re-run the Instance Configuration wizard.

To update @@SERVERNAME value

Run the following:

exec sp_dropserver 'old_name'
exec sp_addserver 'new_name', 'local'

To run Instance Configuration

Select Start | All Programs | Quest Software | LiteSpeed for SQL Server | Instance Configuration.
Review the names of the instances on the SQL Instances step.
Complete the wizard.

4.x jobs not displayed

The timeline does not automatically show 4.x backup/restore jobs. However, you can manually rename the jobs and they will appear in the timeline.

To view 4.x jobs

Rename backup jobs to:

LiteSpeed Backup SERVER_NAME.database_name
Rename restore jobs to:

LiteSpeed Restore SERVER_NAME.database_name

Be sure to use upper case for SERVER_NAME. Additionally, you need to add a comment to maintenance plans to provide information about the databases involved in the plan:

Comment should begin with /** and end with **/
Specify the databases inside {}. Use a semicolon as a separator. For example: {northwind;pubs;litespeedlocal}
{*system} means all system databases.
{*user} means all user databases.
{*} means all databases
It is possible to use combinations. For example: {northwind;pubs;litespeedlocal}{*system} means all system databases plus specified. {master}{*user} means all user databases plus master.

Dell storage appliance not working with LiteSpeed

LiteSpeed has been tested and is certified to work with Dell DR4000, DR4100, and DR6000 storage appliances. In rare cases the DR storage appliance may not work with LiteSpeed.

To check the DR storage appliance

Confirm the access rights of the SQLserver\agent startup account to the DR resource.
Confirm network connectivity between the SQL server and the DR storage appliance.

Troubleshoot Maintenance Plans

Leverage SSIS and LiteSpeed advanced options

Some tasks and advanced options can be unavailable if you do not select Use LiteSpeed when configuring tasks. See About Automating Maintenance Tasks for more information.

Install Backward Compatibility components

If you receive one of the following error messages, you probably need the Backward Compatibility components installed:

"Executed as user: ... sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed."- double-click a plan in the History page to view the event message.
"The SQLDMO 'Application' object failed to initialize." - run the maintenance plan task script in SSMS 2008.

For more information, see http://support.microsoft.com/kb/955626.

Resolve upgrade issues

LiteSpeed plans may fail after the in-place upgrade of SQL Server. Upgrade LiteSpeed Maintenance Plans

Analyze log information

Enable advanced logging and review log files for errors or work with Quest Software support to identify and resolve plan problems. Reporting and Logging in Maintenance Plans

NOTE: For all scenarios, the best is to upgrade all of your servers to the latest LiteSpeed version.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.