Hi,
I think being able to precise a second location for database backup would be a great addition. Espcially when you have multiple locations for repositories.
Thanks for considering it.
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Oct 25, 2023 11:47 am
- Contact:
-
- VP, Product Management
- Posts: 7148
- Liked: 1532 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Re: [Feature request] Second location for database backup
You can define a Backup Copy Job that copies the data to an additional repository after the backup finishes.
This has the advantage that you give the Backup Copy Job a separate retention that works independent from the DB side. So no DBA can delete those backups from the DB side (by mistake).
With the RMAN Plug-in there is an option to write directly to up to 4 Repositories as it is a native functionality from RMAN.
https://helpcenter.veeam.com/docs/backu ... ml?ver=120
This has the advantage that you give the Backup Copy Job a separate retention that works independent from the DB side. So no DBA can delete those backups from the DB side (by mistake).
With the RMAN Plug-in there is an option to write directly to up to 4 Repositories as it is a native functionality from RMAN.
https://helpcenter.veeam.com/docs/backu ... ml?ver=120
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Oct 25, 2023 11:47 am
- Contact:
Re: [Feature request] Second location for database backup
Hi,
I was refering to the configuration backup of database veeam used to restore veeam.
I was refering to the configuration backup of database veeam used to restore veeam.
Who is online
Users browsing this forum: Semrush [Bot] and 97 guests