SAP Library - Find your answers

a) BRTOOLS- To add/resize/db admin tasks

b) BRBACKUP- To perform SAP backup of data file/parameter files

c) BRARCHIVE- To perform backup of offline archive log files

d) BRRESTORE- Restore database

e) BRRECOVER- Recover Database

f) BRCONNECT- Perform daily DBA activities like check task/ indexes/ clean up BRPACE- Space management

Keyword: BASIS
Title : SAP MaxDB - Connecting Third-Party Backup Tools

Keyword: BASIS
Title : SAP MaxDB - Using Third-Party Backup Tools

Keyword: BASIS
Title : SAP MaxDB - Defining Backup Templates

Perform the Backup for each Client Separately

I have 2 clients in one server. The database is SQL.
Would like to perform the backup for each client separately so that I can restore per client.
So far, I've only found information saying that we have to do the entire backup for the database and that individual client backup is not good.

Can anyone advise me on how to perform individual client backup and how's the data integrity.

Sharon

It little confusing with your statement when you are saying that "I have two clients in server".
Or is it rather you want to say that you are having two database instaces on one server.

Scenario 1:
You have One server hosting more that one client as you say. Lets assume it to be Developement & Test client on single databse. Here please note that any SAP DB instace always have more than two clients. The Defaulta clients are:
* Client 000 : SAP AG Konzen
* Client 066 : SAP Early Watch Client.

In addition you have your client specified as
* Client XXX : This will be your production / dev / test client

You can have as many client as you want in a system. Well that really depends on amount of workload and the hardware capacity of the server.

Scenario 2:
You have more that one Database instance on single server. Here you have a choice of having same programs files with multiple databases and or having two different databse instaces with saperate program files. Like in case of oracle you can have two oracle instances Oralce 8i and other with Oracle 9i or any combination you like.

An example of a DB Backup Strategy

Our SAP DB Backup strategy:

• Full Online Backup on 00:00 from Tuesday to Saturday.
• Redolog on 06:00 from Monday to Saturday
• And Once a month full offline backup

An example of a DB Strategy is as follows:-

• Full online SAP backup every day at 20:00 (including weekends)
• Full OS filesystem (minus SAP data) every weekday.
• Continuous archive logging from 15:00 to 11:00 next day (weekdays) and 15:00 to 14:30 (weekends).
• Archive log deletion at 14:45 every day.
• We perform a parallel backup on 2 tapes using 3 x 5 DLT tape autoloaders using a 7 day rotating tape cycle. OS backup onto single DAT.
• The tapes are stored offsite and brought in every weekday. On Friday the Friday,
• Saturday and Sunday tapes are brought in.

With this strategy if this happens you will be restoring the data from 00:00 Saturday and the logs from 06:00 Saturday. This means you could lose 48 hours worth of data.

Is your operation 24 x 7 or 24 x 5? If 24 x 5 it shouldn't be too bad unless you run weekly jobs over the weekend.

Do you have single tape drives or multiple autoloaders?

Is there anyone there to change the tapes over the weekend?

My own personal suggestion would be to forget the offline backup as you do not really want to restore data which could be a month old so why bother shutting the system down every month to back it up. I would perform a daily online backup every
possible day and continually archive the redo logs with a window for changing the tapes. If nobody is there over the weekend to change the tapes, run your archiving continually through the weekend i.e. start on Friday and finish on Monday.