Hello,
for a couple years we are heavily using Solaris 10 zones.
So far we backup them using ufsdump/vxdump. We are investigating
Netbackup as a replacement for ufsdump/vxdump. Our home-made
backup scripts work more or less in the following way:
1. For all zones:
1.1 zlogin zone
We are only just starting to do this, but we did some testing and our plan
is:
Very small servers:
Install NetBackup Standard Client in the Global Zone and backup all file
systems from there - can only be done if there are no applications like
Oracle in the non-global zones.
Medium servers:
A little late to this party but here's another version.
#!/bin/ksh
PATH=$PATH:/usr/openv/netbackup/bin:/usr/openv/netbackup/bin/admincmd
echo Client \t OS Level \t Release
echo =\t =\t ===
for c in `bpplclients -allunique
Note on Marks script, the command does not show the fourth position on
the version 6.5.3.1 all I am getting is 6.5.3.
Not that there is anything wrong with Marks script, its just that the
command does not show fourth position.
From:
It does for 6.0 versions...
Release
===
6.0.0.0.4.4
6.0.0.0.4.4
6.0.0.0.4.4
6.5.0
6.5.0
5.1.0
By the way - the formatting is slightly off due to long Linux OS Levels
(for my RHEL systems) and also the Release column was a bit short for
those 6.0 versions so I modified it
You'll need to add the -A to the end of the bpgetconfig command to get
all information. Note this is only available with -g or -s and not
-M.
That will include all of the dot release information and give you
6.5.3.1 in an additional field called Patch Level. It will also give
you more useful
Ah. Let's see. Change thusly...
#!/bin/ksh
PATH=$PATH:/usr/openv/netbackup/bin:/usr/openv/netbackup/bin/admincmd
echo Client \t OS Level \t Release
echo =\t =\t ===
for c in `bpplclients -allunique -noheader | awk '{print
Very nice Donald.
From: Donaldson, Mark [mailto:mark.donald...@staples.com]
Sent: Wednesday, June 10, 2009 11:31 AM
To: Judy Hinchcliffe; sreynol...@semprautilities.com; ewi...@ewilts.org
Cc: veritas-bu@mailman.eng.auburn.edu
Subject: RE:
Last version? I found an old NT client using v4.5 it didn't populate
the Patch field. This is a fix.
-Mark
#!/bin/ksh
PATH=$PATH:/usr/openv/netbackup/bin:/usr/openv/netbackup/bin/admincmd
echo Client \t OS Level\t Release
echo =\t
Page 71 of the Device Config Guide references this obliquely.
I can't find a technote, but I am working on getting one written as I've
answered this question a fair number of times internally.
I got a private follow-up note explaining to me why a person might want to
do this. It went something
Can anyone tell me how to set this up in Netbackup?
+--
|This was sent by dber...@cucbc.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--
Does anyone know how to keep more job history in the activity monitor in
6.5.3 ?
I've looked through the settings of the master server and can't find
anything that jumps out at me.
Thanks in advance,
Mark Glazerman
Enterprise Storage Administrator
Spartech Corporation
Desk:
http://www.letmegooglethatforyou.com/?q=netbackup+more+job+history+activity+monitor
On Wed, Jun 10, 2009 at 4:24 PM, Mark Glazerman mark.glazer...@spartech.com
wrote:
Does anyone know how to keep more job history in the activity monitor in
6.5.3 ?
I’ve looked through the settings of the
Bp.conf
KEEP_JOBS_HOURS = 168
KEEP_JOBS_SUCCESSFUL_HOURS = 168
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Mark
Glazerman
Sent: Wednesday, June 10, 2009 4:25 PM
To: veritas-bu
Subject:
It's controlled by two lines in your bp.conf file on your master server:
KEEP_JOBS_HOURS = 192
KEEP_JOBS_SUCCESSFUL_HOURS = 192
I keep 9 days with mine.
-M
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On
NB recurses by default. It's hard to stop.
You'd have to do this by using an exclude file on the client, I suspect.
If your filelist includes:
/top/dir_to_backup
You might try to exclude
/top/dir_to_backup/*/
That might do it. I've never tried it, though. Make sure the trailing
slash is
Guys,
I would love to seek your assistance and opinions on this setup. I have two SQL
server nodes clustered using Microsoft Cluster. Version of DB and OS is SQL
2007 and Windows Ent 2008 x64.
On each node, there are two DB instance, DB A and DB B, DB A will be active on
Node 1 and DB B will
On Wed, Jun 10, 2009 at 10:10 PM, Mark .. polyfuze_4...@yahoo.com wrote:
I would love to seek your assistance and opinions on this setup. I have two
SQL server nodes clustered using Microsoft Cluster. Version of DB and OS is
SQL 2007 and Windows Ent 2008 x64.
On each node, there are two DB
Will it continue to backup if one of the node failed?
--- On Wed, 6/10/09, Ed Wilts ewi...@ewilts.org wrote:
From: Ed Wilts ewi...@ewilts.org
Subject: Re: [Veritas-bu] NBU media server cluster
To: Mark .. polyfuze_4...@yahoo.com
Cc: VERITAS-BU@mailman.eng.auburn.edu
Date: Wednesday, June 10,
On Wed, Jun 10, 2009 at 10:31 PM, Mark .. polyfuze_4...@yahoo.com wrote:
Will it continue to backup if one of the node failed?
No - the backup will abort but NetBackup will automatically restart failed
jobs. Your job log may show a stream start, fail, and then try 2 will pick
up the job on
Mark
Best way is to have a virtual name configured for the cluster
(SQLVirtualDB) that can be seen across the cluster.
NetBackup can be configured (using the SQL online backup) to perform the
backup job to this VSN.
I do this quite often here.
Simon
From:
Have to agree with Ed partly on this.
I sometimes find if the cluster fails (and its extremeley rare) I may
end with a status 2 or status 6. Depending on how the window is
configured and the number of retries and the frequency, will determine
if the backup attempts again.
Simon
22 matches
Mail list logo
