dbTalk Databases Forums  

testing sybase backup on another machine

comp.databases.sybase comp.databases.sybase


Discuss testing sybase backup on another machine in the comp.databases.sybase forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Anandhi
 
Posts: n/a

Default testing sybase backup on another machine - 04-29-2004 , 10:24 AM






I am trying to test recovery of sybase on Host A on a new host B .
Partition names on Host B DO NOT match with ones on Host A. Also the
server name on Host A is SYB_DATA and I call it differently - NEW_DATA
on Host B. Here's what I have done so far (followed chapter 28
Restoring the System Databases on sybase Admin Guide docs).

1. Install sybase on Host B.
2. Configure backup server
3. Build master device
4. Start ASE in master-recover mode
5. Recreate device allocation for master
6. Verify connection to backup server
5. load dump of master database

At step 5 I got errors like:


00:00000:00001:2004/04/28 17:55:23.25 server Database 'master' is now
online.
00:00000:00001:2004/04/28 17:55:23.26 server The transaction log in
the database 'master' will use I/O size of 2 Kb.
00:00000:00001:2004/04/28 17:55:23.26 server 0 dump conditions
detected at boot time
00:00000:00001:2004/04/28 17:55:23.26 server server name is
'SYB_DATA'
00:00000:00001:2004/04/28 17:55:23.26 server Activating disk
'RPRDARCDAT0'.
00:00000:00001:2004/04/28 17:55:23.26 kernel Initializing virtual
device 31, '/dev/rrzg48d' with dsync 'on'.
00:00000:00001:2004/04/28 17:55:23.26 kernel dopen: open
'/dev/rrzg48d', No such file or directory
00:00000:00001:2004/04/28 17:55:23.26 kernel udactivate: error
starting virtual disk 31

and so forth for all devices.

I proceeded to restart ASE - but get same kind of message. And then
when I tried to create model from installmodel script:

Server 'SYB_DATA', Line 17:
The Model database is unavailable. It is being used to create a new
database.
00:00000:00001:2004/04/28 18:32:38.51 kernel current process
(0x140014) infected with 11
00:00000:00001:2004/04/28 18:32:38.58 kernel Error at address
0x0000000120236a1c (cm_which_cache)
00:00000:00001:2004/04/28 18:32:38.58 kernel
************************************
00:00000:00001:2004/04/28 18:32:38.58 kernel SQL causing error : if
exists (select *
from master..sysobjects
where name = 'sp_configure')
begin
execute sp_configure "allow updates", 1
end

00:00000:00001:2004/04/28 18:32:38.58 kernel
************************************
00:00000:00001:2004/04/28 18:32:38.58 server SQL Text: if exists
(select *
from master..sysobjects
where name = 'sp_configure')
begin
execute sp_configure "allow updates", 1
end
00:00000:00001:2004/04/28 18:32:38.58 kernel curdb = 1 pstat =
0x10000 lasterror = 0
00:00000:00001:2004/04/28 18:32:38.58 kernel preverror = 0 transtate
= 1
00:00000:00001:2004/04/28 18:32:38.58 kernel curcmd = 224 program =
isql
00:00000:00001:2004/04/28 18:32:38.77 kernel pc: 0x0000000120787238
pcstkwalk+0x58


My questions:

1. Can I call this new server by a different name? The "'Server
'SYB_DATA'" messages above bother me as I call my server now
'NEW_DATA', but sysservers, after the load of master shows entry for
SYB_DATA.

2. Looks to me from the error at step 5, that it was looking for the
same raw partition names - how can I resolve this.

3. I do not know if the kernel errors I get when I try to create model
is also related to the device naming - the OS itself did not register
any memory related errors.

I come from an Oracle background and apologize if my questions sound
too naive. I would also appreciate any pointers to docs about
recovering sybase on a different machine.

Thanks in advance
Anandhi

Reply With Quote
  #2  
Old   
Michael Peppler
 
Posts: n/a

Default Re: testing sybase backup on another machine - 04-29-2004 , 11:33 AM






On Thu, 29 Apr 2004 08:24:20 -0700, Anandhi wrote:

Quote:
I am trying to test recovery of sybase on Host A on a new host B .
Partition names on Host B DO NOT match with ones on Host A. Also the
server name on Host A is SYB_DATA and I call it differently - NEW_DATA on
Host B. Here's what I have done so far (followed chapter 28 Restoring the
System Databases on sybase Admin Guide docs).

1. Install sybase on Host B.
2. Configure backup server
3. Build master device
4. Start ASE in master-recover mode
5. Recreate device allocation for master
6. Verify connection to backup server
7. load dump of master database
Actually, unless your second machine is an exact clone of the first one
you shouldn't load a dump of the master database.

Instead create the server from scratch with srvbuild,
create appropriate disk devices for your user database that you wish to
recover, and then create this database with "for load", followed by a load
database.

The master database has all of the system information (path to devices,
existing databases, etc) which means that it should only be restored on
the same machine, or on a machine that has the same disk layout (and even
then you may run into problems, I think).

Michael
--
Michael Peppler Data Migrations, Inc.
mpeppler (AT) peppler (DOT) org http://www.peppler.org/
Sybase T-SQL/OpenClient/OpenServer/C/Perl developer available for short or
long term contract positions - http://www.peppler.org/resume.html



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.