3.6.0 Matrix Server Release Notes (5697-7087, February 2008)

PolyServe Matrix Server Release Notes 28

16276 Backup instance monitor can remain disabled

This issue can occur when multiple Virtual SQL Servers use the

same backup node and have instances with identical names.

When a Virtual SQL Server is moved to maintenance mode, the

SQL monitors for the associated instances are disabled. On the

backup node, this affects the other Virtual SQL Servers having

instances with the same names; their monitors are also disabled.

When the Virtual SQL Server is returned to operational mode,

the SQL monitors for that Virtual SQL Server are re-enabled on

the backup node. However, the SQL monitors for the other

Virtual SQL Servers may remain disabled.

Workaround. If your configuration uses the same backup node

for multiple Virtual SQL Servers having instances with the same

name, check all SQL monitors after moving a Virtual SQL Server

from maintenance to operational mode. If any monitors are

disabled, re-enable them manually.

16564

MxMigrate Utility cannot back up databases when

LocalSystem account is used

To check for access to the backup directory, the Migration tool

executes Exec master..xp_cmdshell N’dir <backup_path or

restore_path> from the source and target server. It is necessary to

allow xp_cmdshell execution during the migration.

The user running the Migration Utility and the user account

under which the SQL Server process is running must have read,

write, list, create, and delete permission within the folder.

LocalSystem account is a highly privileged account that has full

access to the local machine but does not have access to network

shares. It is recommended that you use a domain user account

for your SQL Server service instead. This applies to both the

source and target server.

Bug

Description