I have a local repository that is pretty big - about 10TB - and I need to create a seed for offsite backup. The rub is that creating that seed is proving to literally take days and none of the backups run during this time, which isn't acceptable.
Is there a way I can more efficiently create a seed without impacting backup?
-
bunger
- Expert
- Posts: 145
- Liked: 10 times
- Joined: Jun 23, 2010 5:39 pm
- Full Name: Bill Unger
- Contact:
-
Dima P.
- Product Manager
- Posts: 14726
- Liked: 1706 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Creating Seed without Impacting Backups
Hello Bill,
You need to copy the backup and deliver those to a secondary repository, backup files ideally should be in a latest state. From the top of my head the best option is to copy the backup files to an external storage one by one during the maintenance window and ship those to a secondary site as soon as possible. Thanks!
You need to copy the backup and deliver those to a secondary repository, backup files ideally should be in a latest state. From the top of my head the best option is to copy the backup files to an external storage one by one during the maintenance window and ship those to a secondary site as soon as possible. Thanks!
Who is online
Users browsing this forum: massimiliano.rizzi, nathang_pid, veremin and 105 guests