Availability for the Always-On Enterprise
Shestakov
Veeam Software
Posts: 6082
Liked: 524 times
Joined: May 21, 2014 11:03 am
Full Name: Nikita Shestakov
Location: Prague
Contact:

Re: changing of backups design

Post by Shestakov » Jan 02, 2018 4:55 pm

lravelo wrote:You're using storage integration features for this though, right? I've never seen targeted backups of datastores without using that...I could be wrong.
Storage integration is not required for this, you just need to create jobs based on the datastores. Job A works with VMs from Datastore A, Job B works with VMs from Datastore B etc.

lravelo
Influencer
Posts: 16
Liked: 2 times
Joined: Dec 28, 2017 8:04 pm
Full Name: Laz Ravelo
Location: Doral, FL
Contact:

Re: changing of backups design

Post by lravelo » Jan 02, 2018 4:58 pm

My bad. I just realized that this could be done when adding objects. Forgive my brain fart.

Shestakov
Veeam Software
Posts: 6082
Liked: 524 times
Joined: May 21, 2014 11:03 am
Full Name: Nikita Shestakov
Location: Prague
Contact:

Re: changing of backups design

Post by Shestakov » Jan 02, 2018 5:53 pm

No problem :)

lravelo
Influencer
Posts: 16
Liked: 2 times
Joined: Dec 28, 2017 8:04 pm
Full Name: Laz Ravelo
Location: Doral, FL
Contact:

Re: changing of backups design

Post by lravelo » Jan 14, 2018 1:23 pm

Ok so I've been able to successfully migrate to backups targeting the three datastores that I have and that's working great. The issue now is with the tape backups. I'm wondering if there's anything I can do to speed this up.

I have created three different GFS pools (one for each datastore) and have created one tape backups job per datastore each pointing to their respective GFS pool. The problem I'm having now is that two of the three jobs are idle saying that there are no GFS candidates available and the one job that is running has been running for about right hours now and it's only able 25% of the way through (granted, there's like 12.6 TB worth of data in there but both my repo are hooked up to a 10GbE network). Just wondering if there any work that can be done preemptively to minimize the amount of time this is taking? Right now I basically have another tape drive that's just sitting doing nothing. Would be nice to put it to work. That's kind of why I created independent backups jobs and pools since I know GFS tape jobs won't do parallel processing

Shestakov
Veeam Software
Posts: 6082
Liked: 524 times
Joined: May 21, 2014 11:03 am
Full Name: Nikita Shestakov
Location: Prague
Contact:

Re: changing of backups design

Post by Shestakov » Jan 15, 2018 11:18 am

Do you want to have 3 copies of same backup set on different media pools or you want to distribute backups among the pools?
Thanks!

lravelo
Influencer
Posts: 16
Liked: 2 times
Joined: Dec 28, 2017 8:04 pm
Full Name: Laz Ravelo
Location: Doral, FL
Contact:

Re: changing of backups design

Post by lravelo » Jan 15, 2018 11:58 am

What I was really aiming for was just to finish the tape backups job as fast as possible. While reading the documentation, I noticed that GFS pools don't do parallel processing so I'll always have an idle tape drive which doesn't work for me so I created three GFS pools (one for each datastore that is backed up) in order to have at least two tape backups jobs running concurrently.

EDIT:

So I logged on this morning to check the status of the backups. The first one took 24 hours to back up a little over 4TB. The second one has been "idle" for almost 14 hours and has been actually running for over 7 hours and is only at 51%. The last job was stuck on idle for 24 hours and just started building the full backup map about 6.5 hours ago and still isn't done.

lravelo
Influencer
Posts: 16
Liked: 2 times
Joined: Dec 28, 2017 8:04 pm
Full Name: Laz Ravelo
Location: Doral, FL
Contact:

Re: changing of backups design

Post by lravelo » Jan 15, 2018 9:58 pm

OK so I think this is one of the culprits for the issue I'm having right now:

When Veeam Backup & Replication executes a GFS job, it performs the following operations:

At 00:00 of the day set in the GFS job schedule the GFS job starts and checks periodically if the source job created a backup:

- If the source job creates a full backup, the GFS job copies it.
- If the source job creates an incremental backup, the GFS job synthesizes a virtual full backup.
- If no backup appears in 24 hours, the GFS job looks for the most recent restore point available. If it is a full backup, the GFS job copies it. If it is an increment, the GFS job uses it to synthesize a virtual full backup.
Specifically the second item on that list. Seems like I either need to move to reverse incrementals or run a full backup prior to the the tape job. Any recommendations? The full backups size for each datastore is 3.3 TB, 5.26 TB, and 4.65 TB respectively.

Shestakov
Veeam Software
Posts: 6082
Liked: 524 times
Joined: May 21, 2014 11:03 am
Full Name: Nikita Shestakov
Location: Prague
Contact:

Re: changing of backups design

Post by Shestakov » Jan 19, 2018 9:16 pm

What I was really aiming for was just to finish the tape backups job as fast as possible. While reading the documentation, I noticed that GFS pools don't do parallel processing so I'll always have an idle tape drive which doesn't work for me so I created three GFS pools (one for each datastore that is backed up) in order to have at least two tape backups jobs running concurrently.
Got it. That makes sense to split the objects between the tape jobs. Just make sure there are more or less equal amount of data written on each media pool.
Seems like I either need to move to reverse incrementals or run a full backup prior to the the tape job. Any recommendations?
Synthetic full is created if source job is on forever forward incremental mode. What backup mode do you use now?
Thanks!

lravelo
Influencer
Posts: 16
Liked: 2 times
Joined: Dec 28, 2017 8:04 pm
Full Name: Laz Ravelo
Location: Doral, FL
Contact:

Re: changing of backups design

Post by lravelo » Jan 19, 2018 9:44 pm

Right now I use forever forward incrementals. I have some wiggle room in the backups window though so I can change it if the tape backup duration will shorten

Shestakov
Veeam Software
Posts: 6082
Liked: 524 times
Joined: May 21, 2014 11:03 am
Full Name: Nikita Shestakov
Location: Prague
Contact:

Re: changing of backups design

Post by Shestakov » Jan 20, 2018 7:57 am

Good. So let's give it a try.

lravelo
Influencer
Posts: 16
Liked: 2 times
Joined: Dec 28, 2017 8:04 pm
Full Name: Laz Ravelo
Location: Doral, FL
Contact:

Re: changing of backups design

Post by lravelo » Feb 04, 2018 2:55 pm

Ok so after a couple of weeks of testing different methods, I've narrowed it down to having to run staggered active full backups prior to the GFS tape backup job. So far I can get all jobs to run within a 30 hour window during the weekends so that's doable for me. The reverse increments took too long as my storage repo couldn't handle the random IO as well as the sequential. So far it looks like this is the approach that I'll be taking.

Shestakov
Veeam Software
Posts: 6082
Liked: 524 times
Joined: May 21, 2014 11:03 am
Full Name: Nikita Shestakov
Location: Prague
Contact:

Re: changing of backups design

Post by Shestakov » Feb 05, 2018 11:45 am

Glad the goal os achieved. Thanks for updating!

Post Reply

Who is online

Users browsing this forum: Bing [Bot] and 51 guests