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.

dumping of transaction logs for master, model, etc.

4 posts in Backup and Recovery Last posting was on 2001-04-18 00:32:22.0Z
L_Broman Posted on 2001-04-17 00:44:30.0Z
From: L_Broman
Date: Mon, 16 Apr 2001 20:44:30 -0400
Newsgroups: sybase.public.sqlserver.backup+recovery
Subject: dumping of transaction logs for master, model, etc.
Message-ID: <BF603B060E76D8A8000412F985256A31.0004130985256A31@webforums>
Lines: 14
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com!webforums.sybase.com!news
Xref: forums-1-dub sybase.public.sqlserver.backup+recovery:313
Article PK: 1060830

For all of our corporate dbs, we either have cron processes that dump the
tran on regular intervals to tape or we have the trunc_log_on_chkpt option
set to true. This keeps the tran log at a manageable size.

I have been reviewing this situation today and realize that the master,
model, sybsystemdb, and sybsystemprocs databases are not being dumped or
truncated on any of our servers.

What is the correct way of managing the tran logs on these databases. What
do I need to do on each of the dbs in order to keep the tran log down but
also be able to backup and recover responsibly?

Thanks,
Lisa


Anthony Mandic <amandic Posted on 2001-04-17 06:30:25.0Z
Date: Tue, 17 Apr 2001 16:30:25 +1000
From: Anthony Mandic <amandic@*t.com.au>
Organization: Mandic Consulting Pty. Ltd.
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i686)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: dumping of transaction logs for master, model, etc.
References: <BF603B060E76D8A8000412F985256A31.0004130985256A31@webforums>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Message-ID: <6orakqwxAHA.274@forums.sybase.com>
Newsgroups: sybase.public.sqlserver.backup+recovery
Lines: 29
NNTP-Posting-Host: 210.9.51.46
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.backup+recovery:312
Article PK: 1060827


L_Broman wrote:

> I have been reviewing this situation today and realize that the master,
> model, sybsystemdb, and sybsystemprocs databases are not being dumped or
> truncated on any of our servers.
>
> What is the correct way of managing the tran logs on these databases. What
> do I need to do on each of the dbs in order to keep the tran log down but
> also be able to backup and recover responsibly?

Sybsystemprocs should have the db option "trunc log" set. You don't
need to dump it because you can recreate it by rerunning the installmaster
script. Dumping it won't hurt though. Model can be recreated by the
buildmaster program. You shouldn't be using it, so there's no need
to change its options or dump its log. It serves as a template for
new databases (and tempdb on server start). You can't set options
for master or dump its log, so the usual practise is to truncate the
log and then dump the database. Do this as part of your regular dump
cycle. The dump is usually quite small, so I usually also keep a
recent copy on disk. This helps if there is a tape drive problem too.

-am © 2001


L Broman Posted on 2001-04-17 14:52:24.0Z
Reply-To: "L Broman" <lisa@etrieve.com>
From: "L Broman" <lisa@etrieve.com>
References: <BF603B060E76D8A8000412F985256A31.0004130985256A31@webforums> <6orakqwxAHA.274@forums.sybase.com>
Subject: Re: dumping of transaction logs for master, model, etc.
Date: Tue, 17 Apr 2001 07:52:24 -0700
Lines: 34
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Message-ID: <dX$CVB1xAHA.178@forums.sybase.com>
Newsgroups: sybase.public.sqlserver.backup+recovery
NNTP-Posting-Host: 198.107.63.162
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.backup+recovery:309
Article PK: 1060828

Thanks!
What about for sybsystemdb, I know this is the db that handles distributed
transactions. I don't know exactly how we are using it here... I just know
that the logsegment is about 60% full and I want to get it lower than that.
-L Broman

"Anthony Mandic" <amandic@*t.com.au> wrote in message
news:6orakqwxAHA.274@forums.sybase.com...
> L_Broman wrote:
>
> > I have been reviewing this situation today and realize that the master,
> > model, sybsystemdb, and sybsystemprocs databases are not being dumped or
> > truncated on any of our servers.
> >
> > What is the correct way of managing the tran logs on these databases.
What
> > do I need to do on each of the dbs in order to keep the tran log down
but
> > also be able to backup and recover responsibly?
>
> Sybsystemprocs should have the db option "trunc log" set. You don't
> need to dump it because you can recreate it by rerunning the installmaster
> script. Dumping it won't hurt though. Model can be recreated by the
> buildmaster program. You shouldn't be using it, so there's no need
> to change its options or dump its log. It serves as a template for
> new databases (and tempdb on server start). You can't set options
> for master or dump its log, so the usual practise is to truncate the
> log and then dump the database. Do this as part of your regular dump
> cycle. The dump is usually quite small, so I usually also keep a
> recent copy on disk. This helps if there is a tape drive problem too.
>
> -am © 2001


Anthony Mandic <amandic Posted on 2001-04-18 00:32:22.0Z
Date: Wed, 18 Apr 2001 10:32:22 +1000
From: Anthony Mandic <amandic@*t.com.au>
Organization: Mandic Consulting Pty. Ltd.
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i686)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: dumping of transaction logs for master, model, etc.
References: <BF603B060E76D8A8000412F985256A31.0004130985256A31@webforums> <6orakqwxAHA.274@forums.sybase.com> <dX$CVB1xAHA.178@forums.sybase.com>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Message-ID: <EQJ3JH6xAHA.191@forums.sybase.com>
Newsgroups: sybase.public.sqlserver.backup+recovery
Lines: 11
NNTP-Posting-Host: 210.9.51.46
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.backup+recovery:303
Article PK: 1060818


L Broman wrote:

> What about for sybsystemdb, I know this is the db that handles distributed
> transactions. I don't know exactly how we are using it here... I just know
> that the logsegment is about 60% full and I want to get it lower than that.

Sorry, I missed that. Yes, its used by two phased commit. ASE 12 now
installs it by default. I think you can safely truncate the log.

-am © 2001