Backup strategy for livecache 7.6

[Former Member]

Hi

Can anybody explain me the backup strategy for livecache 7.6?

I am trying to schedule <b>rslvcbackup</b> to take Incremental and log backup. I created variants for FULL backup, Incremental backup and Log and gave an existing logical backup medium name ( BACK_FULL ) for Logical Backup Medium and LCA for DB Connection Name. But when I try to run the report with the variant it says the file already exists.

Logical Command: DBMCLI

Parameter: -d LCS -n v012 -tpi SCS -tpc LCA -tpp no_longer_used -uUTL -c

backup_start BKUP_530 RECOVERY DATA AUTOIGNORE

ERR

-24958,ERR_BAOVERWRITE: file already exists, cannot overwrite

External program terminated with exit code 1

Logical backup medium is created with No overwrite property, if I change it to allow overwrite, it may work (didn’t try). My question is

If I change it to allow overwrite and if the backup fails, will I loose the previous backup file or is it going to create a backup file before overwriting it

Thanks

Prince

[Former Member]

Hi Prince,

first, we don't recommend having a backup medium with the 'overwrite' property in a production system. We recommend that you always write to a new file and you have some old backups available to be restored in case of a system crash.

Your problem is that the backup medium is created with 'No overwrite' property. If you change it to allow overwrite, the backup should work.

If you set it to allow overwrite and if the backup fails, you may or may not lose the previous backup file. If the backup fails even before starting to write the datapages to the backup, the previous backup may be available. But if the backup fails in the middle (for example, after writing 4 GB out of 5 GB), then the previous backup won't be available. You cannot depend on the old backup in case the new backup fails; that's why we recommend against having only one data backup file set to overwrite.

Regards,

Ashwath

[Former Member]

Hi Ashwath,

Thanks for your quick reply. You said that its not recommended to use overwrite property, then how do schedule RSLVCBACKUP to take backups everyday ?

I have gone through the help files and it says to create a backup template

( LC10 --> Administration --> Configuration --> Backup Template , but i cat see this I can see only backup Media ).

I took a backup using Database Manager GUI ( Backup --> Backup Wizard )

database: asap12:LCS

Version: 7.6.00.29

Rundirectory: /sapdb/data/wrk/LCS

Backup Type: Complete Data

Backup Device: BKUP_530

Device Type: FILE

Device/File: LCS_COM

Here i assume that LCS_COM is the backup file name and I can see this in /sapdb/data/wrk/LCS . But my doubt is that, LCA_COME is only 5MB where as my sapdata 1 to 4 each have 17gig is full !! Wondering whether this backup is valid even though it says successful!!

asap12:sctadm 49> df -g |grep /sapdb

/dev/sctlv18 2.94 2.25 24% 574 1% /sapdb

/dev/sctlv19 17.06 0.07 100% 5 1% /sapdb/LCS/sapdata1

/dev/sctlv20 17.06 0.07 100% 5 1% /sapdb/LCS/sapdata2

/dev/sctlv21 17.06 0.07 100% 5 1% /sapdb/LCS/sapdata3

/dev/sctlv22 17.06 0.07 100% 5 1% /sapdb/LCS/sapdata4

/dev/sctlv23 5.75 1.84 68% 6 1% /sapdb/LCS/saplog

Thanks

Prince

[Former Member]

Hi Prince,

you can schedule RSLVCBACKUP to use different a backup medium everyday. For e.g., use medium A on Monday, medium B on Tuesday, etc. if you are taking daily backups.

Are the two medium names LCS_COM and LCA_COME the same? It is not clear from your question.

Are you saying that the file LCA_COME is only 5MB when sapdata 1 to 4 each are 17 GB? 17 GB may be the size of each of your data volumes, but how much of the data volume is full? Check in the backup history file if the size of the backup is equal to the filled size in liveCache.

If you are an SAP customer and need further help, please open a message and R/3 service connection so that we can logon and do some analysis.

Thanks,

Ashwath

[Former Member]

Hi Ashwath ,

Thanks again .. medium names is LCS_COM , the other one is a typo ( LCS_COME ) . Sapdata 1 to 4 are 17gig abd its 100% full .

asap12:sctadm 8> pwd

/sapdb/data/wrk/LCS

asap12:sctadm 7> du -k LCS_COM

<i><b>5056</b></i> LCS_COM

asap12:scsadm 9> df -k |grep /sapdb

/dev/sctlv18 3080192 2355980 24% 575 1% /sapdb

/dev/sctlv19 17891328 70668 <b>100%</b> 5 1% /sapdb/LCS/sapdata1

/dev/sctlv20 17891328 70668 <b>100%</b> 5 1% /sapdb/LCS/sapdata2

/dev/sctlv21 17891328 70668 <b>100%</b> 5 1% /sapdb/LCS/sapdata3

/dev/sctlv22 17891328 70668 <b>100%</b> 5 1% /sapdb/LCS/sapdata4

/dev/sctlv23 6029312 1932044 68% 6 1% /sapdb/LCS/saplog

asap12:sctadm 10> cd /sapdb/LCS/sapdata1

asap12:scsadm 11> ls

DISKD0001 lost+found

asap12:scsadm 12> du -m DISKD0001

<b>17400.00</b> DISKD0001

Yes we are SAP customer , Do you see anything wrong here ?

Thanks

Prince

[Former Member]

Hi Prince,

the command you are using, df -k, tells us how much of the device is being used. It doesn't tell you how much of the 17 GB data volume is being used. From the OS point of view, all 17 GB are assigned to the liveCache when it is installed.

Please check in DBMgui (and not the OS level) the filling level of the liveCache, and then see if the backup size matches this filling level.