Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Unable to load compress database from remote backup server

127 views
Skip to first unread message

jdenwigr

unread,
Apr 16, 2008, 5:28:09 AM4/16/08
to
I did a dump stripe with compression=4 using remote backup
server. when try to load, it fails. Here is error msg.

Backup Server session id is: 142. Use this value when
executing the 'sp_volchanged' system stored procedure after
fulfilling any volume change request from the Backup Server.
Backup Server: 5.21.2.1: Remote DUMP/LOAD is not allowed
when interfacing to a stripe for device
'compress::/u01/sybase/dump/NJPXDBS52_SYB01/DBfrom53.dp1'.

Command I use to dump,
dump database JDTESTDB
to "/u01/sybase/dump/NJPXDBS52_SYB01/DBfrom53.dp1" at
NJPXDBS52_SYB01_BS
stripe on "/u01/sybase/dump/NJPXDBS52_SYB01/DBfrom53.dp2" at
NJPXDBS52_SYB01_BS
with compression = "4"
go

Command I use to load,
load database JDTESTDB
from
"compress::/u01/sybase/dump/NJPXDBS52_SYB01/DBfrom53.dp1" at
NJPXDBS52_SYB01_BS
stripe on
"compress::/u01/sybase/dump/NJPXDBS52_SYB01/DBfrom53.dp2" at
NJPXDBS52_SYB01_BS
go

This is ASE 12.5.4. Thanks in advance for assistance.

Luc Van der Veurst

unread,
Apr 16, 2008, 9:53:58 AM4/16/08
to

you should leave out the compress:: before the filenames when you load
the database.

Luc.


<jdenwigr> wrote in message news:4805c6a9.107...@sybase.com...

Bret Halford

unread,
Apr 16, 2008, 2:04:59 PM4/16/08
to
Right. There are two different compression methods, and you are mixing the

two. The older one is the "compress::" syntax, which uses a backupserver
API module. That syntax does not work with remote backupservers, and does
have to be used for both the DUMP and LOAD coperations. The
more modern "with compression =<n>" syntax can be used with remote
servers and only needs to be used with the DUMP; load recognizes this
kind of dump is compressed and does the right thing.

=bret

0 new messages