SAP Sybase ASE Database Backup

[Former Member]

Hi all,

Actually i want to about SAP Sybase ASE backup .

Should we stop all activity of SAP application server,

like no user log in time of backup before taking the

backup of Sybase with dump command.

Please help me asap

Thanks

Ashish Kumar

[kimon_moschandreou · Accepted solution]

Hello,

It is not necessary to stop user activity and you may check this SyBooks Online for more information

Regards,

Kimon

[Former Member · Accepted solution]

Thanks Sir,

sir i did not find any information  the link you are shared to me

please can you give me more clarity .

[kimon_moschandreou · Accepted solution]

the link sends you in ASE documentation where the backup is described. concerning the question if you need to stop the App server in order to take a backup the answer is no, the database can be online while dump command is running

[Former Member · Accepted solution]

Sir

my intention is not ask for proof, actually you gave me link that's why i asked you where it is mention

Thanks for reply

[former_member188958 · Accepted solution]

I think a better reference to the documentation would be the Commands Reference page on the dump database command.

This page has a bullet point giving the general rule that it is not necessary to stop activity while taking a backup:

Scheduling dumps

• Adaptive Server databasedumps are dynamic—they can take place while the database is active. However, they may slow the system down slightly, so you may want to run dump database when the database is not being heavily updated.

[If your recovery strategy is to take only daily full database dumps but not transaction log dumps, another reason to schedule the dumps for slow times is that when loaded, there will be less recovery to do so the database will be able to come online faster.]

This page also discusses the exception, which is when the dump is to be used for a cross-platform dump and load:

Before you run dump database, for a cross platform dumpand load, move the database to a transactional quiescent status:

1. Verify the database runs cleanly by executing dbcc checkdb and dbcc checkalloc.
2. To prevent concurrent updates from open transactions by other processes during dump database, use sp_dboption to place the database in a single-user mode.
3. Flush statistics to systabstats using sp_flushstats.
4. Wait for 10 to 30 seconds, depending on the database size and activity.
5. Run checkpoint against the database to flush updated pages.
6. Run dump database.

[Former Member · Accepted solution]

Thanks Bret !!!!

It's very helpful to me

[Former Member · Accepted solution]

Bret !!  i have one more question,

Can we take Sybase database dump backup on shared drive.

scenario like this :

Suppose i shared a drive on computer name as \\palsapdev\t  and i accessed it on another computer name as palsapqas, now i want to take backup at share drive \\palsapdev\t

[former_member188958 · Accepted solution]

I believe that would work.

-bret

[Former Member · Accepted solution]

but

i think it is not working ?

[kimon_moschandreou · Accepted solution]

it works, but it will be slower. Also you need to check permissions, so the user running the Sybase Backup server should have access on this remote drive.

Kimon

[Former Member · Accepted solution]

Thanks Kimon,

Can you give me more clarity about this process step by step.

While i already gave all permission to shared partition,

but i do not the process of what permission have to

provide to Sybase backup server

i use following command :

dump database model to "\\palsapdev\t\model.dmp"

but give error

[kimon_moschandreou · Accepted solution]

Hi,

Check on the machine of ASE which user runs the Sybase Backup Server service. The defaule is "Local System" which a local user and has not permissions to run anything in the network. Change the user to a domain user which has access to the path you want to take the back and it will work

Regards,

Kimon

[Former Member · Accepted solution]

HI Ashish,

What is the error message ? From what you have posted it look like you are running Windows platform and then ASE will use the Windows Operting system call createfile , writefile .

If you are on Windows and start ASE as a service it is possibly that it is started with the system account.

Dumping across a network

Niclas