backup file name changed

[Former Member]

Dear All,

Everyday my backup file name has start with "bd*".

But suddenly today onwards my backup file name has changed,

it start with "be*"

Can anyone help to solve this problem.

any spciefic format is using for creating the backup file name format

Thanks in advance

Sundar.C

[Former Member · Accepted solution]

Don't worry. I suppose everyone will notice the same.

'b' means 'backup', and the rest of the name is some kind of timestamp, translated to alphabetic characters. You will notice that names were increasing steadily in alphabetic order.

Your last backups probably began with bdzz...

And, well, the next letter after 'd' is ....

[Former Member · Accepted solution]

Dear Joe Bo,

Yes you are right, my last backup file is

bdzzvtna

bdzzqvrx

bdzzlxww

bdzzccsf

But one more thing i want to clear, my last four backup file name is started from "bdzz*",

How to identify the last file name for current second character?

Thanks in advance

Regards

Sundar.C

[Former Member · Accepted solution]

How to identify the last file name for current second character?

Not sure if I understood your question.

You may order filenames by time,

on Unix: ls -rtl

on Windows: dir /od

Or, as names are just alpabetically encoded timestamps, the normal order of ls or dir command will give you the same.

And from now on, for the next few years, the second character will always be 'e'.

If this doesn't answer your question, then please clarify!

regards

[Former Member · Accepted solution]

Dear Joe Bo,

I understood the backup concept, that is The backup file name is generated authomatically and alphabetic order.

Actually my doubt is

1. Can you tell me how many files are creating per character ( such as ba,bb,bc,bd).

2. What is the logic (or format) it use for create the file name ( is it depend on date or time).

Regards,

Sundar.C

[JPReyes · Accepted solution]

Can you tell me how many files are creating per character?

Why is this important?... anyhow file has 8 characters 1 is fixed so 7 can change; from a to z - 27 letters so start multiplying.

Regards

Juan

[Former Member · Accepted solution]

Hello Sundar,

like Juan, I don't think that's an important problem.

And then, as it is a timestamp, the number of files beginning with be will be the number of backups that will run during the period from now to some (currently not exactly known to me) date in future.

So the only way to answer this question will be a crystal ball.

Maybe your question was when will the period of 'be' end?

I don't know, and I am not aware of a SAP ducoment describing this.

If I really had to find out, then I would be able to reverse engineer that timestamp algorithm by comparing timestamps of the last backups. But I think it isn't worth it.

regards

[Former Member · Accepted solution]

Dear Joe Bo,

Yes i agree this is not much more important for SAP.but for me ,

usally we are copying the backup file to device (TAPE), for this copying i have given the below command in unix ( in script)

cd /backup2/bd*

/usr/bin/tar -cvf /dev/rmt1 *

But on that day , the file name was changed as be*. so my tar backup has failed.

That's why i am finding the logic for that backup file format. anyhow now i have changed the script as

cd /backup2/b*

/usr/bin/tar -cvf /dev/rm1 *

Thanks Joe Bo

Thanks for all the replies

Regards,

Sundar.C

[Former Member]

Sundar,

Please check out following link.

[http://help.sap.com/saphelp_nw04s/helpdata/EN/0d/d30ed24a0c11d182b80000e829fbfe/content.htm]

Hope this helps.

Manoj