Veritas-bu

[Veritas-bu] Restore priority

2001-10-11 12:38:50
Subject: [Veritas-bu] Restore priority
From: kevin.v.vapiwala AT ssmb DOT com (Vapiwala, Kevin V [IT])
Date: Thu, 11 Oct 2001 12:38:50 -0400
Gotcha! I guess I sort of misread your original reply. You're right, my
suggesiton would work only if you're not using SSO.

-----Original Message-----
From: Gregg Yurchak [mailto:gyurchak AT veritas DOT com]
Sent: Thursday, October 11, 2001 12:30 PM
To: Vapiwala, Kevin V [IT]; 'Jason Ahrens'; Veritas BU
Subject: RE: [Veritas-bu] Restore priority


What I'm implying is if you do have SSO and all media servers see all the
drives, this isn't going to work (leaving one drive out of the storage
unit).  You've got serverA, serverB, serverC, each with it's own storage
unit, stuA, stuB, and stuC respectively.  You've got a total of 10 drives,
seen by all three machines.  So you try and leave a drive out of each
storage unit, and define each with 9 instead of 10.

Backups start.  serverA uses 9 drives, because that's all it can.  serverB
comes along and says hey, I can use up to 9 drives, and here's one free, so
I'll use it.  This is true however you work it.  The only way to get it to
work would be to put just three drives in each storage unit, which would
always leave one free.  This quickly becomes rather obscene as media servers
increase.

Even if stuB and stuC have 1 drive each in their storage unit(say they're
SAN Media Servers only backing themselves up), stuA can't have more than 7
drives.

Getting tricky still doesn't work.  People have tried to define all 10
drives on serverA, and only put 9 in it's storage unit.  Then they only let
serverB and serverC see one drive each (again, to use a drastic example).
The problem here is you've got good odds, but if the first 9 drives serverA
uses doesn't include the two physical ones defined on serverB or serverC, as
soon as they start a backup you lose the reserved drive.  Additionally, if
serverB or serverC start a backup before serverA starts all his, you lose
the reserved drive.

Thanks,
Gregg Yurchak
VERITAS Consultant
Biloxi, MS
gregg AT veritas DOT com
Office: 1.228.822.9810
Cell:    1.228.324.6939




-----Original Message-----
From: Vapiwala, Kevin V [IT] [mailto:kevin.v.vapiwala AT ssmb DOT com]
Sent: Thursday, October 11, 2001 9:17 AM
To: 'Gregg Yurchak'; 'Jason Ahrens'; Veritas BU
Subject: RE: [Veritas-bu] Restore priority


I don't think you need SSO to set the storage unit to have a free tape drive
for restores. We;ve implemented that on all of our 9710s and we run 9 drives
for backups and have a free one for restores.

-----Original Message-----
From: Gregg Yurchak [mailto:gyurchak AT veritas DOT com]
Sent: Thursday, October 11, 2001 11:38 AM
To: Vapiwala, Kevin V [IT]; 'Jason Ahrens'; Veritas BU
Subject: RE: [Veritas-bu] Restore priority


This only works if you're not using SSO, which many people are know.  Or if
you are sharing drives, you have to really seriously limit the amount seen
by each server.

Thanks,
Gregg Yurchak
VERITAS Consultant
Biloxi, MS
gregg AT veritas DOT com
Office: 1.228.822.9810
Cell:    1.228.324.6939




-----Original Message-----
From: Vapiwala, Kevin V [IT] [mailto:kevin.v.vapiwala AT ssmb DOT com]
Sent: Thursday, October 11, 2001 7:30 AM
To: 'Jason Ahrens'; Veritas BU
Subject: RE: [Veritas-bu] Restore priority


Why not just set your Storage Unit Properties to one less drive then you
have on your Storage Unit, that way you have a driver free at all times for
a restore.

-----Original Message-----
From: Jason Ahrens [mailto:AhrensJ AT psi DOT ca]
Sent: Thursday, October 11, 2001 9:40 AM
To: Veritas BU
Subject: [Veritas-bu] Restore priority


Yesterday night, we had a system go down. The system was rebuilt and a
restore was started to bring back the data.

The restore was started just minutes after the backup window opened. This
means taht the queue was full of backup jobs. It also appeared that the
restore did not take priority over the backups, and it would have taken
hours to wait for the queue to clear. This was not acceptable and we ended
up killing all the backup jobs so the restore could happen, and requeued all
the backups.

I'm thinking there has to be a better way.

How can I instruct NetBackup to consider restores at a higher priority than
backups, so that when the first free drive and required tape becomes free,
the restore will occur. I would't ask that backups in progress are
halted/suspended for the restore, just that the restore go to the top of the
queue.

Thanks

Jason

--
Jason Ahrens
Systems Administrator/Backup Specialist
PSINet Limited
http://www.psi.ca
The Internet SuperCarrier

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

<Prev in Thread] Current Thread [Next in Thread>