Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Proper Backup Strategy

3 posts in General Discussion Last posting was on 2003-08-13 17:45:40.0Z
Dennis Cieri Posted on 2003-08-13 13:30:58.0Z
Sender: 4379.3f3a3d63.1804289383@sybase.com
From: Dennis Cieri
Newsgroups: ianywhere.public.general
Subject: Proper Backup Strategy
X-Mailer: WebNews to Mail Gateway v1.1s
Message-ID: <3f3a3d92.437f.846930886@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 13 Aug 2003 06:30:58 -0700
X-Trace: forums-1-dub 1060781458 10.22.241.41 (13 Aug 2003 06:30:58 -0700)
X-Original-Trace: 13 Aug 2003 06:30:58 -0700, 10.22.241.41
Lines: 20
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:1584
Article PK: 3812

Can someone point me to the best procedure for backup and
recovery?

I currently have a 14 GB database (Sybase 6.0.3) that I
backup every evening with the dbbackup command. The backup
is made to a another folder on the server disk and that file
is picked-up by a tape.

If my server fails, I can always use the backup. However, I
recently encounter an Assertion 200610 error with Sybase
8.0.0.2640 and if I restore the data, the Assertion error
may be contained in the backup file.

In short, what strategy should I invoke so that my backup
has the highest probability of being usable? Should I
always unload the db?

Any help is appreciated.

Thanks


Craig Stoss Posted on 2003-08-13 16:07:24.0Z
From: "Craig Stoss" <No_cstoss_Spam@sybase.com>
Newsgroups: ianywhere.public.general
References: <3f3a3d92.437f.846930886@sybase.com>
Subject: Re: Proper Backup Strategy
Lines: 38
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
NNTP-Posting-Host: cstoss-pc.sybase.com
X-Original-NNTP-Posting-Host: cstoss-pc.sybase.com
Message-ID: <3f3a623c$1@forums-1-dub>
Date: 13 Aug 2003 09:07:24 -0700
X-Trace: forums-1-dub 1060790844 172.31.142.117 (13 Aug 2003 09:07:24 -0700)
X-Original-Trace: 13 Aug 2003 09:07:24 -0700, cstoss-pc.sybase.com
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:1590
Article PK: 3819

Dennis,

I recommend the startegy of keeping at least 2 backups. ie if you backup
Monday night and the database is valid, and then Tuesday nights backup is
invalid, then you can simply use monday nights backup and apply the
transaction logs as necessary.

I would make a once a day fullbackup and then incremental transaction log
backups throughout the day. saving each to the appropriate days directory.

Regards,
HTH,
Craig Stoss
iAnywhere Technical Support

<Dennis Cieri> wrote in message news:3f3a3d92.437f.846930886@sybase.com...
> Can someone point me to the best procedure for backup and
> recovery?
>
> I currently have a 14 GB database (Sybase 6.0.3) that I
> backup every evening with the dbbackup command. The backup
> is made to a another folder on the server disk and that file
> is picked-up by a tape.
>
> If my server fails, I can always use the backup. However, I
> recently encounter an Assertion 200610 error with Sybase
> 8.0.0.2640 and if I restore the data, the Assertion error
> may be contained in the backup file.
>
> In short, what strategy should I invoke so that my backup
> has the highest probability of being usable? Should I
> always unload the db?
>
> Any help is appreciated.
>
> Thanks


Chris Keating (iAnywhere Solutions) Posted on 2003-08-13 17:45:40.0Z
From: "Chris Keating \(iAnywhere Solutions\)" <FightSpam_keating@iAnywhere.com>
Newsgroups: ianywhere.public.general
References: <3f3a3d92.437f.846930886@sybase.com>
Subject: Re: Proper Backup Strategy
Lines: 48
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
NNTP-Posting-Host: keating-xp.sybase.com
X-Original-NNTP-Posting-Host: keating-xp.sybase.com
Message-ID: <3f3a7944$1@forums-1-dub>
Date: 13 Aug 2003 10:45:40 -0700
X-Trace: forums-1-dub 1060796740 172.31.140.19 (13 Aug 2003 10:45:40 -0700)
X-Original-Trace: 13 Aug 2003 10:45:40 -0700, keating-xp.sybase.com
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:1595
Article PK: 3824

You missed *validation* as part of your backup strategy. As with any backup,
the value is in backing up something that can be used for recovery. The
validation does not need to be every night but perhaps weekly.

Review the documention for a discussion of backup and recovery.

--

Chris Keating
Sybase Adaptive Server Anywhere Professional Version 8

Sybase TechWave User Training and Solutions conference -- August 4 - 8, 2003
in Orlando, FL. -- A great place for education and in-depth discussions
on all our technology, future trends in the market, not to mention getting
time with the engineers who create the products! For more information,
visit http://www.ianywhere.com/techwave2003

iAnywhere Solutions http://www.iAnywhere.com

** Please only post to the newsgroup

** Whitepapers can be found at http://www.iAnywhere.com/developer
** EBFs can be found at http://downloads.sybase.com/swx/sdmain.stm
** Use CaseXpress to report bugs http://casexpress.sybase.com

<Dennis Cieri> wrote in message news:3f3a3d92.437f.846930886@sybase.com...
> Can someone point me to the best procedure for backup and
> recovery?
>
> I currently have a 14 GB database (Sybase 6.0.3) that I
> backup every evening with the dbbackup command. The backup
> is made to a another folder on the server disk and that file
> is picked-up by a tape.
>
> If my server fails, I can always use the backup. However, I
> recently encounter an Assertion 200610 error with Sybase
> 8.0.0.2640 and if I restore the data, the Assertion error
> may be contained in the backup file.
>
> In short, what strategy should I invoke so that my backup
> has the highest probability of being usable? Should I
> always unload the db?
>
> Any help is appreciated.
>
> Thanks