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.

dbbackup -l ..more info

2 posts in General Discussion Last posting was on 2004-07-22 13:41:24.0Z
Steve Burbrink Posted on 2004-07-21 21:24:31.0Z
Reply-To: "Steve Burbrink" <sywalters@hotmail.com>
From: "Steve Burbrink" <sywalters@hotmail.com>
Newsgroups: ianywhere.public.general
Subject: dbbackup -l ..more info
Lines: 18
Organization: Compass Engineering
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
NNTP-Posting-Host: ztown2-1-18.adsl.one.net
X-Original-NNTP-Posting-Host: ztown2-1-18.adsl.one.net
Message-ID: <40fedf0f$1@forums-1-dub>
Date: 21 Jul 2004 14:24:31 -0700
X-Trace: forums-1-dub 1090445071 216.23.33.18 (21 Jul 2004 14:24:31 -0700)
X-Original-Trace: 21 Jul 2004 14:24:31 -0700, ztown2-1-18.adsl.one.net
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:3289
Article PK: 7203

Can you provide more details on this ?
Is the server running on the second machine? (I don't think so).
dbbackup -l path\filename.log -c "connection_string"I'm assuming the log
file ("path\filename.log) on the second machine.

For Linux, what will the connection string (or parameters) look like when
connecting to a machine on a different server?
(ie. SQLCONNECT='UID=DBA;PWD=SQL;DBN=blah;ENG=blah'

If the server is using a non-standard TCP/IP port, where will that be
modified on the SQLCONNECT?

The help file is kinda short on it also...

Thanks,
Steve


Greg Fenton Posted on 2004-07-22 13:41:24.0Z
From: Greg Fenton <greg.fenton_NOSPAM_@ianywhere.com>
Organization: iAnywhere Solutions Inc.
User-Agent: Mozilla Thunderbird 1.6.3.2f (Windows/20040707)
X-Accept-Language: en-us, en
MIME-Version: 1.0
Newsgroups: ianywhere.public.general
Subject: Re: dbbackup -l ..more info
References: <40fedf0f$1@forums-1-dub>
In-Reply-To: <40fedf0f$1@forums-1-dub>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: gfenton-xp.sybase.com
X-Original-NNTP-Posting-Host: gfenton-xp.sybase.com
Message-ID: <40ffc404$1@forums-1-dub>
Date: 22 Jul 2004 06:41:24 -0700
X-Trace: forums-1-dub 1090503684 10.25.100.188 (22 Jul 2004 06:41:24 -0700)
X-Original-Trace: 22 Jul 2004 06:41:24 -0700, gfenton-xp.sybase.com
Lines: 78
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:3293
Article PK: 7204


Steve Burbrink wrote:
> Can you provide more details on this ?
> Is the server running on the second machine? (I don't think so).
> dbbackup -l path\filename.log -c "connection_string"I'm assuming the log
> file ("path\filename.log) on the second machine.

The details for "live backup" are not linked to from the "dbbackup
utility" page. I'll post an enhancement to the docs team.

But looking up "live backup" in the documentation index for ASA 9.x
brought me to:

ASA Database Administration Guide
Backup and Data Recovery
Backup and recovery tasks
Making a live backup

That page contains further links to "Protecting against total machine
failure".

DBBackup is a client application. It can run anywhere that can connect
to the database you want "live backuped" (live backupified???)

Normally the dbbackup client will be running on the machine that will
host the backup database. This way, if the primary server goes down the
dbbackup utility can close down cleanly.

Essentially, the utility is making a live copy of the transaction log
from the main server in "real time". If the main server goes down, then
you would apply the transaction log to the secondary database and
then bring the secondary db online.


> For Linux, what will the connection string (or parameters) look like when
> connecting to a machine on a different server?
> (ie. SQLCONNECT='UID=DBA;PWD=SQL;DBN=blah;ENG=blah'

Are you asking what the parameters should be for the "-c" argument to
dbbackup?

The above string you have is one valid connection string (minus the
"SQLCONNECT=" part):

dbping -d -c 'UID=DBA;PWD=SQL;DBN=blah;ENG=blehk'

That will have the client broadcast on the network looking for an engine
named 'blehk' and if found, will connect to the database 'blah'.

To force a TCPIP connection to a machine named 'foo', the database
server running on port 555:

dbping -d -c 'uid=DBA;pwd=SQL;DBN=blah;links=TCPIP(host=foo;port=555)'

The entire subject of connection parameters is very well documented. In
the ASA 9.x docs see:

ASA Database Administration Guide
Connecting to a Database
Introduction to connections

The main rule of thumb is that for a production environment you should
explicitly list as many direct values in your connection string as
possible so as to avoid relying on defaults. Defaults are great for
quick administrative tasks, but for production applications they can
cause problems (e.g. if you don't specify a DBN and the order that
databases are opened on the database engine changes, then you
application would attempt to connect to a different database than
otherwise expected).

Hope this helps,
greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/