Volume validation error: illegal volume change

[O. Bridge]

Hi folks,

I have a problem with dumping a database from a Win2K3 server onto a
Solaris server. The process of dumping works fine, however, when loading
I get error messages complaining about "Volume validation error: illegal
volume change" etc. Errormessage is attached below.

I have checked out the Win2K3 server with several dbcc commands, and the
database is in good health.

The database is dumped out to a single file.

I have scoped around on the 'net for answers, but to no avail. Hope you
gurus can help me!

Thanks!

Regards,
O. Bridge

Errormessage from Solaris server:
Backup Server: 6.66.2.1: Volume validation error: illegal volume change,
device /dumpspace/proddb1: volume mounted out of order, expected volume
0001, got volume 16777216.
Backup Server: 6.36.2.4: Header labels of rejected volume:
Backup Server: 6.34.2.4:
VOL1 0
7
HDR1findb062960C013 ^A
HDR2F
Backup Server: 1.14.2.2: Unrecoverable I/O or volume error. This DUMP
or LOAD session must exit.
Backup Server: 6.32.2.3: /dumpspace/proddb1: volume not valid or not
requested (server:
, session id: 5.)
Backup Server: 1.14.2.4: Unrecoverable I/O or volume error. This DUMP
or LOAD session must exit.
Msg 8009, Level 16, State 1:
Server 'RECOVER', Line 1:
Error encountered by Backup Server. Please refer to Backup Server
messages for details.

let us have the details

1. Which version of ASE are you using on Win2K3 and Solaris
2. Page sizes of target and source sybase servers
3. is it a compressed dump

thanks
krv

Post by O. Bridge
Hi folks,
I have a problem with dumping a database from a Win2K3 server onto a
Solaris server. The process of dumping works fine, however, when loading I
get error messages complaining about "Volume validation error: illegal
volume change" etc. Errormessage is attached below.
I have checked out the Win2K3 server with several dbcc commands, and the
database is in good health.
The database is dumped out to a single file.
I have scoped around on the 'net for answers, but to no avail. Hope you
gurus can help me!
Thanks!
Regards,
O. Bridge
Backup Server: 6.66.2.1: Volume validation error: illegal volume change,
device /dumpspace/proddb1: volume mounted out of order, expected volume
0001, got volume 16777216.
VOL1 0 7
HDR1findb062960C013 ^A
HDR2F
Backup Server: 1.14.2.2: Unrecoverable I/O or volume error. This DUMP or
LOAD session must exit.
Backup Server: 6.32.2.3: /dumpspace/proddb1: volume not valid or not
, session id: 5.)
Backup Server: 1.14.2.4: Unrecoverable I/O or volume error. This DUMP or
LOAD session must exit.
Error encountered by Backup Server. Please refer to Backup Server
messages for details.

[Mark A. Parsons]

Please provide @@version from *both* the source and target dataservers.

----------------------

My guesstimate is that you dumped a database from a small endian server and tried to load it into a large endian server (or vice versa) ...

... error message says it's expecting volume 0001, but got 16777216.

Convert these 2 numbers to hex and you get:

0001 = 0x 0000 0001
16777216 = 0x 0100 0000

The bytes are in reverse order ... which is exactly what happens when you take binary data from one endian machine and try to read it on a machine with a different endianness.

Post by O. Bridge
Hi folks,
I have a problem with dumping a database from a Win2K3 server onto a
Solaris server. The process of dumping works fine, however, when loading
I get error messages complaining about "Volume validation error: illegal
volume change" etc. Errormessage is attached below.
I have checked out the Win2K3 server with several dbcc commands, and the
database is in good health.
The database is dumped out to a single file.
I have scoped around on the 'net for answers, but to no avail. Hope you
gurus can help me!
Thanks!
Regards,
O. Bridge
Backup Server: 6.66.2.1: Volume validation error: illegal volume change,
device /dumpspace/proddb1: volume mounted out of order, expected volume
0001, got volume 16777216.
VOL1 0 7
HDR1findb062960C013 ^A
HDR2F
Backup Server: 1.14.2.2: Unrecoverable I/O or volume error. This DUMP
or LOAD session must exit.
Backup Server: 6.32.2.3: /dumpspace/proddb1: volume not valid or not
, session id: 5.)
Backup Server: 1.14.2.4: Unrecoverable I/O or volume error. This DUMP
or LOAD session must exit.
Error encountered by Backup Server. Please refer to Backup Server
messages for details.

[Mark A. Parsons]

And if I'd read the first line of your post I wouldn't have said 'guesstimate', ie, this *is* an endianess issue ... you typically cannot dump from Windows and load into Solaris (or any of the 'big' unix OS's).

One of the newer ASE releases (12.5.4?) has a backupserver binary that has the ability to load across hardware with different endianness.

You might try dumping the Win2K3 database remotely using the Solaris backupserver ... then load said dump using the Solaris backupserver. (I honestly don't know if that's a viable workaround in this case ... 50% of me says it might work ... 50% of me says it probably won't work ... while the other 50% isn't sure ... when in doubt 'try it out' ... or wait for someone to post something more definitive ...)

Post by Mark A. Parsons
----------------------
My guesstimate is that you dumped a database from a small endian server
and tried to load it into a large endian server (or vice versa) ...
... error message says it's expecting volume 0001, but got 16777216.
0001 = 0x 0000 0001
16777216 = 0x 0100 0000
The bytes are in reverse order ... which is exactly what happens when
you take binary data from one endian machine and try to read it on a
machine with a different endianness.

Post by O. Bridge
Hi folks,
I have a problem with dumping a database from a Win2K3 server onto a
Solaris server. The process of dumping works fine, however, when
loading I get error messages complaining about "Volume validation
error: illegal volume change" etc. Errormessage is attached below.
I have checked out the Win2K3 server with several dbcc commands, and
the database is in good health.
The database is dumped out to a single file.
I have scoped around on the 'net for answers, but to no avail. Hope
you gurus can help me!
Thanks!
Regards,
O. Bridge
Backup Server: 6.66.2.1: Volume validation error: illegal volume
change, device /dumpspace/proddb1: volume mounted out of order,
expected volume 0001, got volume 16777216.
VOL1 0 7
HDR1findb062960C013 ^A
HDR2F
Backup Server: 1.14.2.2: Unrecoverable I/O or volume error. This DUMP
or LOAD session must exit.
Backup Server: 6.32.2.3: /dumpspace/proddb1: volume not valid or not
, session id: 5.)
Backup Server: 1.14.2.4: Unrecoverable I/O or volume error. This DUMP
or LOAD session must exit.
Error encountered by Backup Server. Please refer to Backup Server
messages for details.

[O. Bridge]

OK, thanks for you help!

-O. B.

Post by Mark A. Parsons
And if I'd read the first line of your post I wouldn't have said
'guesstimate', ie, this *is* an endianess issue ... you typically cannot
dump from Windows and load into Solaris (or any of the 'big' unix OS's).
One of the newer ASE releases (12.5.4?) has a backupserver binary that
has the ability to load across hardware with different endianness.
You might try dumping the Win2K3 database remotely using the Solaris
backupserver ... then load said dump using the Solaris backupserver. (I
honestly don't know if that's a viable workaround in this case ... 50%
of me says it might work ... 50% of me says it probably won't work ...
while the other 50% isn't sure ... when in doubt 'try it out' ... or
wait for someone to post something more definitive ...)

Post by Mark A. Parsons
----------------------
My guesstimate is that you dumped a database from a small endian
server and tried to load it into a large endian server (or vice versa)
...
... error message says it's expecting volume 0001, but got 16777216.
0001 = 0x 0000 0001
16777216 = 0x 0100 0000
The bytes are in reverse order ... which is exactly what happens when
you take binary data from one endian machine and try to read it on a
machine with a different endianness.

Post by O. Bridge
Hi folks,
I have a problem with dumping a database from a Win2K3 server onto a
Solaris server. The process of dumping works fine, however, when
loading I get error messages complaining about "Volume validation
error: illegal volume change" etc. Errormessage is attached below.
I have checked out the Win2K3 server with several dbcc commands, and
the database is in good health.
The database is dumped out to a single file.
I have scoped around on the 'net for answers, but to no avail. Hope
you gurus can help me!
Thanks!
Regards,
O. Bridge
Backup Server: 6.66.2.1: Volume validation error: illegal volume
change, device /dumpspace/proddb1: volume mounted out of order,
expected volume 0001, got volume 16777216.
VOL1 0 7
HDR1findb062960C013 ^A
HDR2F
Backup Server: 1.14.2.2: Unrecoverable I/O or volume error. This
DUMP or LOAD session must exit.
Backup Server: 6.32.2.3: /dumpspace/proddb1: volume not valid or not
, session id: 5.)
Backup Server: 1.14.2.4: Unrecoverable I/O or volume error. This
DUMP or LOAD session must exit.
Error encountered by Backup Server. Please refer to Backup Server
messages for details.

how did you resolve ?

Post by O. Bridge
OK, thanks for you help!
-O. B.

Post by Mark A. Parsons
And if I'd read the first line of your post I wouldn't have said
'guesstimate', ie, this *is* an endianess issue ... you typically cannot
dump from Windows and load into Solaris (or any of the 'big' unix OS's).
One of the newer ASE releases (12.5.4?) has a backupserver binary that
has the ability to load across hardware with different endianness.
You might try dumping the Win2K3 database remotely using the Solaris
backupserver ... then load said dump using the Solaris backupserver. (I
honestly don't know if that's a viable workaround in this case ... 50% of
me says it might work ... 50% of me says it probably won't work ... while
the other 50% isn't sure ... when in doubt 'try it out' ... or wait for
someone to post something more definitive ...)

Post by Mark A. Parsons
----------------------
My guesstimate is that you dumped a database from a small endian server
and tried to load it into a large endian server (or vice versa) ...
... error message says it's expecting volume 0001, but got 16777216.
0001 = 0x 0000 0001
16777216 = 0x 0100 0000
The bytes are in reverse order ... which is exactly what happens when
you take binary data from one endian machine and try to read it on a
machine with a different endianness.

Post by O. Bridge
Hi folks,
I have a problem with dumping a database from a Win2K3 server onto a
Solaris server. The process of dumping works fine, however, when
loading I get error messages complaining about "Volume validation
error: illegal volume change" etc. Errormessage is attached below.
I have checked out the Win2K3 server with several dbcc commands, and
the database is in good health.
The database is dumped out to a single file.
I have scoped around on the 'net for answers, but to no avail. Hope you
gurus can help me!
Thanks!
Regards,
O. Bridge
Backup Server: 6.66.2.1: Volume validation error: illegal volume
change, device /dumpspace/proddb1: volume mounted out of order,
expected volume 0001, got volume 16777216.
VOL1 0 7
HDR1findb062960C013 ^A
HDR2F
Backup Server: 1.14.2.2: Unrecoverable I/O or volume error. This DUMP
or LOAD session must exit.
Backup Server: 6.32.2.3: /dumpspace/proddb1: volume not valid or not
, session id: 5.)
Backup Server: 1.14.2.4: Unrecoverable I/O or volume error. This DUMP
or LOAD session must exit.
Error encountered by Backup Server. Please refer to Backup Server
messages for details.

[m***@peppler.org]

Post by Mark A. Parsons
And if I'd read the first line of your post I wouldn't
have said 'guesstimate', ie, this *is* an endianess issue
... you typically cannot dump from Windows and load into
Solaris (or any of the 'big' unix OS's).

As of ASE 12.5.3 the cross platform dump/load works in most
cases (I've seen some problems with compressed dumps, but
otherwise I've been able to take dumps from HP to AIX, from
AIX to Linux, from Windows to Linux, etc. with no problems)

Michael