sudhir dubey wrote:
It will be overwritten if you do not change the dump file name. See this link for 15.7 esd #2.
This is from the same location
"
- If the device file already exists, Backup Server overwrites it; it does not truncate it. For example, suppose you dump a database to a device file and the device file becomes 10MB. If the next dump of the database to that device is smaller, the device file is still 10MB."
That note in the Reference Manual about the device file being overwritten if it already exists is actually no longer correct as of 15.0.2 due to a change made under CR 377674. The original dump file is now deleted and a new one created, so the size will be correct even if the new dump is smaller. I've just filed a documentation change request, CR 743959, to have this bullet point removed from the documentation.
Also, I note that in your first post you wrote that you had created a backup folder under /sybase.
If this same /sybase holds your databases's data and log devices, it isn't the best place to put the backups too, as a device failure would then wipe out both your database devices and your backup. You can't get too paranoid about backups, I once worked a support case where my customer's data center got hit by lightning and fried the production system. They switched over to the hot standby, only to be hit by lightning a second time. Fortunately, they had their backups on tape, stored in a desk in another room, so they were able to get running again the next day. I'm not sure their business would have survivied a flood, though, unless they also sent some backups to a remote site.
-bret