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.

dump file size w/compression

3 posts in Backup and Recovery Last posting was on 2009-04-29 18:35:07.0Z
John Flynn Posted on 2009-04-28 15:30:39.0Z
From: "John Flynn" <jflynn@miqs.com>
Newsgroups: sybase.public.ase.backup+recovery
Subject: dump file size w/compression
Lines: 20
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <49f7211f@forums-1-dub>
Date: 28 Apr 2009 08:30:39 -0700
X-Trace: forums-1-dub 1240932639 10.22.241.152 (28 Apr 2009 08:30:39 -0700)
X-Original-Trace: 28 Apr 2009 08:30:39 -0700, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.backup+recovery:3953
Article PK: 48041

Hi.

I am on ASE15 on Solaris. The manual says "If the device file already
exists, Backup Server overwrites it; it does not truncate it. For example,
suppose you dump a database to a device file and the device file becomes
10MB. If the next dump of the database to that device is smaller, the device
file is still 10MB." In my experience this has been true; for example one
time when I increased the number of stripes, resulting in more (but smaller)
dump files, each "new" dump file was smaller than before, but the "existing"
dump files did not shrink. Granted, this might have been on a pre-ASE15
server, I forget. But the ASE15 manual seems unambiguous.

So I was surprised recently when I started using compression, and it
appeared that the dump file actually shrank in place. I don't mind this
behavior, but I was wondering whether this should be expected to happen.

Thanks.
- John.


Bret Halford [Sybase] Posted on 2009-04-28 16:00:00.0Z
From: "Bret Halford [Sybase]" <bret@sybase.com>
Organization: Sybase, Inc.
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
Newsgroups: sybase.public.ase.backup+recovery
Subject: Re: dump file size w/compression
References: <49f7211f@forums-1-dub>
In-Reply-To: <49f7211f@forums-1-dub>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <49f72800$1@forums-1-dub>
Date: 28 Apr 2009 09:00:00 -0700
X-Trace: forums-1-dub 1240934400 10.22.241.152 (28 Apr 2009 09:00:00 -0700)
X-Original-Trace: 28 Apr 2009 09:00:00 -0700, vip152.sybase.com
Lines: 36
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.backup+recovery:3954
Article PK: 48042


John Flynn wrote:
> Hi.
>
> I am on ASE15 on Solaris. The manual says "If the device file already
> exists, Backup Server overwrites it; it does not truncate it. For example,
> suppose you dump a database to a device file and the device file becomes
> 10MB. If the next dump of the database to that device is smaller, the device
> file is still 10MB." In my experience this has been true; for example one
> time when I increased the number of stripes, resulting in more (but smaller)
> dump files, each "new" dump file was smaller than before, but the "existing"
> dump files did not shrink. Granted, this might have been on a pre-ASE15
> server, I forget. But the ASE15 manual seems unambiguous.t
>
> So I was surprised recently when I started using compression, and it
> appeared that the dump file actually shrank in place. I don't mind this
> behavior, but I was wondering whether this should be expected to happen.
>
> Thanks.
> - John.

Hi John,

As of 15.0.2, backupserver deletes the original file and opens a new
one. If you are on an earlier version and using the "compress::"
backupserver api module, then it may be that has always worked that way,
I'm not sure either way. That doc section was written about the
typical generic backupserver dumps.

The change in behavior was to fix CR 377674 "A 624 error may be reported
in case a database is dumped to an existing file and ASE crashes during
dump operation. " - the circumstances resulted in loadable dump file
that contained a mix of old and new page images

Cheers,
-bret


John Flynn Posted on 2009-04-29 18:35:07.0Z
From: "John Flynn" <jflynn@miqs.com>
Newsgroups: sybase.public.ase.backup+recovery
References: <49f7211f@forums-1-dub> <49f72800$1@forums-1-dub>
Subject: Re: dump file size w/compression
Lines: 10
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <49f89ddb@forums-1-dub>
Date: 29 Apr 2009 11:35:07 -0700
X-Trace: forums-1-dub 1241030107 10.22.241.152 (29 Apr 2009 11:35:07 -0700)
X-Original-Trace: 29 Apr 2009 11:35:07 -0700, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.backup+recovery:3955
Article PK: 48045

Hi Bret,

> As of 15.0.2, backupserver deletes the original file and opens a new
> one.

Thanks, that explains it perfectly.

- John.