syb通过bsr把solaris[syb11.9.2]的数据备份到nt[syb11.5.1]出错

zhsh

dump database dbname to "c:\d" at ntbsname;

bslog中出现以下错误，请各位大侠分析分析　怎么回事

查了一些资料，　说是两个　ｂｓ　的字符集不一样，１１。５上没有　ｕｓ＿ｅｎｇｌｉｓｈ，但用sp_helplanguage　显示、ｕｓ＿ｅｎｇｌｉｓｈ是支持的，两个　　ｂｓ　的字符集（charset ）都是iso_1.　

请赐教，，先谢过了

Mar 26 10:23:49 2003: Open Server Error: 5704.10.0: Changed client character set setting to 'iso_1'
.
Mar 26 10:23:49 2003: Open Server Error: 5704.10.0: Changed client character set setting to 'iso_1'
.
Mar 26 10:23:49 2003: Open Server Error: 5704.10.0: Changed client character set setting to 'iso_1'
.
Mar 26 10:23:49 2003: Open Server Error: 5704.10.0: Changed client character set setting to 'iso_1'
.
Mar 26 10:23:49 2003: Open Server Error: 5704.10.0: Changed client character set setting to 'iso_1'
.
Mar 26 10:23:49 2003: Open Server Error: 5704.10.0: Changed client character set setting to 'iso_1'
.
Mar 26 10:23:49 2003: Open Server Error: 5704.10.0: Changed client character set setting to 'iso_1'
.
Mar 26 10:23:49 2003: Open Server Error: 5704.10.0: Changed client character set setting to 'iso_1'
.
Mar 26 10:23:49 2003: Open Server Error: 5704.10.0: Changed client character set setting to 'iso_1'
.
Mar 26 10:23:49 2003: Open Server Error: 5704.10.0: Changed client character set setting to 'iso_1'
.
Mar 26 10:23:49 2003: Open Server Error: 5704.10.0: Changed client character set setting to 'iso_1'
.
Mar 26 10:23:49 2003: Open Server Error: 5704.10.0: Changed client character set setting to 'iso_1'
.
Mar 26 10:23:49 2003: Open Server Error: 5704.10.0: Changed client character set setting to 'iso_1'
.
Mar 26 10:23:49 2003: Open Server Error: 5704.10.0: Changed client character set setting to 'iso_1'
.
Mar 26 10:23:49 2003: Open Server Error: 5704.10.0: Changed client character set setting to 'iso_1'
.
Mar 26 10:23:49 2003: Open Server Error: 5704.10.0: Changed client character set setting to 'iso_1'
.
Mar 26 10:23:49 2003: Open Server Error: 5704.10.0: Changed client character set setting to 'iso_1'
.
Mar 26 10:23:49 2003: Open Server Error: 5704.10.0: Changed client character set setting to 'iso_1'
.
Mar 26 10:23:49 2003: Open Server Error: 5704.10.0: Changed client character set setting to 'iso_1'
.
Mar 26 10:23:49 2003: Open Server Error: 5704.10.0: Changed client character set setting to 'iso_1'
.
Mar 26 10:23:49 2003: Open Server Error: 5704.10.0: Changed client character set setting to 'iso_1'
.
Mar 26 10:23:49 2003: Open Server Error: 5704.10.0: Changed client character set setting to 'iso_1'
.
Mar 26 10:23:49 2003: Open Server Error: 5704.10.0: Changed client character set setting to 'iso_1'
.
Mar 26 10:23:49 2003: Open Server Error: 5704.10.0: Changed client character set setting to 'iso_1'
.
Mar 26 10:23:49 2003: Open Server Error: 5704.10.0: Changed client character set setting to 'iso_1'
.
Mar 26 10:23:49 2003: Open Server Error: 5704.10.0: Changed client character set setting to 'iso_1'
.
Mar 26 10:23:49 2003: Backup Server: 5.16.2.2: DB-Library error, error number 20011, severity 8: Maximum number of DBPROCESSes already allocated.
Mar 26 10:23:49 2003: Backup Server: 5.3.2.1: Cannot open a connection to the slave site 'james_bs'.
Mar 26 10:23:49 2003: Backup Server: 5.16.2.2: DB-Library error, error number 20018, severity 5: General SQL Server error: Check messages from the SQL Server.
Mar 26 10:23:49 2003: Backup Server: 5.16.2.2: DB-Library error, error number 20018, severity 5: General SQL Server error: Check messages from the SQL Server.
Mar 26 10:23:49 2003: Backup Server: 5.16.2.2: DB-Library error, error number 20018, severity 5: General SQL Server error: Check messages from the SQL Server.
Mar 26 10:23:49 2003: Backup Server: 5.16.2.2: DB-Library error, error number 20018, severity 5: General SQL Server error: Check messages from the SQL Server.
Mar 26 10:23:49 2003: Backup Server: 5.16.2.2: DB-Library error, error number 20018, severity 5: General SQL Server error: Check messages from the SQL Server.
Mar 26 10:23:49 2003: Backup Server: 5.16.2.2: DB-Library error, error number 20018, severity 5: General SQL Server error: Check messages from the SQL Server.
Mar 26 10:23:49 2003: Backup Server: 5.16.2.2: DB-Library error, error number 20018, severity 5: General SQL Server error: Check messages from the SQL Server.
Mar 26 10:23:49 2003: Backup Server: 5.16.2.2: DB-Library error, error number 20018, severity 5: General SQL Server error: Check messages from the SQL Server.
Mar 26 10:23:49 2003: Backup Server: 5.16.2.2: DB-Library error, error number 20018, severity 5: General SQL Server error: Check messages from the SQL Server.
Mar 26 10:23:49 2003: Backup Server: 5.16.2.2: DB-Library error, error number 20018, severity 5: General SQL Server error: Check messages from the SQL Server.
Mar 26 10:23:49 2003: Backup Server: 5.16.2.2: DB-Library error, error number 20018, severity 5: General SQL Server error: Check messages from the SQL Server.
Mar 26 10:23:50 2003: Backup Server: 5.16.2.2: DB-Library error, error number 20018, severity 5: General SQL Server error: Check messages from the SQL Server.
Mar 26 10:23:50 2003: Backup Server: 5.16.2.2: DB-Library error, error number 20018, severity 5: General SQL Server error: Check messages from the SQL Server.
Mar 26 10:23:50 2003: Backup Server: 5.16.2.2: DB-Library error, error number 20018, severity 5: General SQL Server error: Check messages from the SQL Server.
Mar 26 10:23:50 2003: Backup Server: 5.16.2.2: DB-Library error, error number 20018, severity 5: General SQL Server error: Check messages from the SQL Server.
Mar 26 10:23:50 2003: Backup Server: 5.16.2.2: DB-Library error, error number 20018, severity 5: General SQL Server error: Check messages from the SQL Server.
Mar 26 10:23:50 2003: Backup Server: 5.16.2.2: DB-Library error, error number 20018, severity 5: General SQL Server error: Check messages from the SQL Server.
Mar 26 10:23:50 2003: Backup Server: 5.16.2.2: DB-Library error, error number 20018, severity 5: General SQL Server error: Check messages from the SQL Server.
Mar 26 10:23:50 2003: Backup Server: 5.16.2.2: DB-Library error, error number 20018, severity 5: General SQL Server error: Check messages from the SQL Server.
Mar 26 10:23:50 2003: Backup Server: 5.16.2.2: DB-Library error, error number 20018, severity 5: General SQL Server error: Check messages from the SQL Server.
Mar 26 10:23:50 2003: Backup Server: 5.16.2.2: DB-Library error, error number 20018, severity 5: General SQL Server error: Check messages from the SQL Server.
Mar 26 10:23:50 2003: Backup Server: 5.16.2.2: DB-Library error, error number 20018, severity 5: General SQL Server error: Check messages from the SQL Server.
Mar 26 10:23:50 2003: Backup Server: 5.16.2.2: DB-Library error, error number 20018, severity 5: General SQL Server error: Check messages from the SQL Server.
Mar 26 10:23:50 2003: Backup Server: 5.16.2.2: DB-Library error, error number 20018, severity 5: General SQL Server error: Check messages from the SQL Server.
Mar 26 10:23:50 2003: Backup Server: 5.16.2.2: DB-Library error, error number 20018, severity 5: General SQL Server error: Check messages from the SQL Server.

Blackrose

我觉得你的关键问题应该是
Cannot open a connection to the slave site 'james_bs'.


在 主数据库 所在主机上 使用 DSEDIT 添加 远程备份服务器的名字，
并且此处配置的服务器名字 必须跟 远程主机上配置的服务器名字完全相同。
另外，本地及远程服务器必须启动，并且名字上不能冲突

之后在主数据库主机上使用命令，

1>; dump database pubs2 to 'c:\temp\pubs2.dmp' at REMOTE_BACKUPSERVER
2>; go

zhsh

可以连到 james_bs 只是不知道为什么 dump 产生很多连接，导致

Mar 26 10:23:49 2003: Backup Server: 5.16.2.2: DB-Library error, error number 20011, severity 8: Maximum number of DBPROCESSes already allocated.

而无法继续连接，我重起了solaris 上的 sybserver 和 bs还是不行

另外 错误日志是在nt下面的 backup.log 中，
谢谢

Blackrose

不知道跟你 两个不一致 有没有关系

一般来说 远程备份要求版本一致

看看这个 http://www.sybase.com/detail?id=20334

仔细检查你在 interfaces 文件及sql.ini文件中配置的信息是否正确，backup server 是否一致。