Every backup suite on the planet (and some others, too) uses SAN snapshot capabilities for backing up Oracle database using snapshot. In general, there are 2 cases:
1. The database is on the ASM storage
2. The database is on the file system.
The procedure goes like this:
1. You set the database in the backup mode ("ALTER DATABASE BEGIN BACKUP")
2. The volumes on which the database files and archive logs reside are
3. Backup mode is turned off.
Next, you have several options:
1. Copy the snapshot to spare location using SAN (SRDF, SnapVault)
2. Use the snapshot to create a proxy instance and then use rman to
back it up. You need rman catalog for that.
3. Copy the files from the snapshot to some kind of long term storage
(LTO, NAS, cheapo SAN, S3 or Glacier. If it is Glacier, please be
aware that it is much more expensive to get the data out of Glacier
than to get the data into the Glacier. Glacier has 2-pass
de-duplication which means that it squeezes lots of data into the
very small disk space at the cost of speed.)
I don't know much about history and I don't know much about Veeam but I KNOW that this what all backup suites (Veeam, Rubrik, Cohesity, Avamar, TSM, CommVault, NetBackup) do with snapping the Oracle database.
On 6/7/2021 11:48 AM, Tharmarajah, Sam wrote:
We have been requested to look into using the Veem snapshot backup for our off
site backups. Presently we use TSM and RMAN for our regular operations.
We are interested to know of any gotchas that we need to pay attention to when
thinking about this.