Hi,
At the moment we are using a scale-out repository. The perfomance tier uses a local repository with one large backup file for all VM. The capacity tier uses an S3 storage. All backup data older than x days are only available in the S3 storage.
Now we are switching to a new backup server. This would be a good time to switch to a per machine backup, because the backup chain needs to be recreated anyway. But what about the S3 storage? Can the existing data simply be reused or would we have to create a new backup chain in the S3 storage and upload a complete full backup?
Thanks
Dennis
-
- Novice
- Posts: 5
- Liked: never
- Joined: Apr 11, 2013 9:21 am
- Contact:
-
- Product Manager
- Posts: 20400
- Liked: 2298 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Changing to a per machine backup - what about the s3 storage
Are you going to re-create the backup infrastructure the same, including servers, components, and job sources?
-
- Novice
- Posts: 5
- Liked: never
- Joined: Apr 11, 2013 9:21 am
- Contact:
Re: Changing to a per machine backup - what about the s3 storage
Hi,
yes. The plan is to migrate the current Veeam configuration to the new backup server with the same jobs, VMs, etc. Only the Backup server Hardware (CPU, RAM,much more disk space) is changed.
yes. The plan is to migrate the current Veeam configuration to the new backup server with the same jobs, VMs, etc. Only the Backup server Hardware (CPU, RAM,much more disk space) is changed.
Who is online
Users browsing this forum: Majestic-12 [Bot] and 22 guests