How are your filers setup to point to the drives?
I ask because you mentioned storage unit group which is a shared
scenario.
Sounds like you have multiple STUs in a Storage Unit Group, and you have
the filers policies pointing to the group.
Have you tried pointing the policies to the specific
Hello All
I'm moving a master/media server to a new machine. I'm trying to use the
procedure in this technote: http://seer.support.veritas.com/docs/266720.htm
But I keep getting:
2bpmedia: INITIATING: version NetBackup 5.1 created: 0
2bpmedia: client/server handshaking failed
client/server
I had this same issue trying to do a year-end catalog backup to send
offsite for 7 years. Turns out that I could not specify a specific media
ID, and I couldn't run the command to copy one of my catalog media IDs
either. The only way I could make it work was to manually reconfigure the
I was just curious about retention schedules that everyone has out
there. I know they vary according to what kinds of laws you have,
however, I was wondering about just any general backup.
We currently have the following:
Incrementals - 2 weeks
Full-weekly - 5 weeks
Full-monthly - 1 year
Profile A (most windows and some Unix):
Incrementals - 2 weeks
Fulls - 3 Weeks
Profile B (some windows)
Same as A
Plus:
Monthly Full - 1 Year
Profile C (Most Unix)
Incrementals - 7 weeks
Weekly Fulls - 9 weeks
Monthly Fulls - Infinite
-Original Message-
From: [EMAIL PROTECTED]
Hi!
Im using Netbackup 6.0 MP1 with SQL Server client to
run a weekly job to backup and truncate SQL database logs. The backup job runs
successfully but the logs are still growing. Are there any known issues with
the Netbackup SQL client piece where it would not truncate the logs?
Incremental - Onsite - 2 Weeks
Full Weekly - Offsite 3 Months
Full Monthly - Offsite 1 year
Databases (including the above)
Full Weekly - Onsite 2 months
Email (including the above)
Full Monthly - Offsite 5 years
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Title: RE: [Veritas-bu] Retention Schedules
It depends on the nature of the data. Our OS backup only keeps 1 month for incr, and 3 months for full. For data backups, each business unit will give us the requirement, so it depends.
-Original Message-
From: [EMAIL PROTECTED]
This may not work - file locking on Linux/unix is very different than the NT
world.
exclude the database files by excluding either the directory they live in or
the default extension, for example: *.dbf for oracle.
-M
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Excludes life on the client in the ../netbackup directory as files, not
in a registry-like file.
Create
/usr/openv/netbackup/exclude_list.policyname with the excluded patterns
within on each client.
-M
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]On
Title: RE: [Veritas-bu] Retention Schedules
We backup over 60 TB per weekand had to
setretention standards to make the best use of our tape drives and
tapes:
Prod OS and Application : Weekly Cumulative
Incrementals Retention : 2 weeks
Monthly Full Retention: 3 months, 6 months or 1 year
Thanks to all, both on and off list who pointed out my error. I've been
successfully avoiding some Oracle db files with Busy File option, but I
am going to test the exclude_list option.
Thanks,
Jason
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
bpmedia -movedb is designed to move mediadb files between media servers in
the same environment. I'm not sure it'll work to move to a new master. The
new master may have to start life as a media server to the original master,
then be converted. Still, this is probably more complicated than
bplist -C client -k policy
-t 13 -s 2/5/2006 -e 2/10/2006 -S master media server -l -R /$PATH
bplist -C client
bplist -C client -k policy
All commands above return EXIT
STATUS 227: no entity was found even though successfull backups ran
across the first command's specified date range and over
Hi All,
We are getting partial backup (1) from one of our
media server (Windows 2000). We want to backup this client using Open file using
VSP as our client is windows 2000 and cannot implement microsoft
VSS.
Secondly is it important to specify cache size ?
for example my drive size is 10 gb
I have a couple questions regarding a 4.5 FP6 to 5.1 MP4 upgrade on our AIX
5.1 master server.
Are new licence keys required?
Will I need to make any licence changes or additions during the upgrade
process? (I am not adding any new products).
One of the first steps of the 4.5 to 5.1 upgrade for
On Mon, Feb 13, 2006 at 03:01:17PM +0100, [EMAIL PROTECTED] wrote:
I'm moving a master/media server to a new machine. I'm trying to use the
procedure in this technote: http://seer.support.veritas.com/docs/266720.htm
Does the new host have the same hostname and IP address? If not, moving
the
This is what I do:
Host propertiesMaster Serverclient
attributes. Select client then Windows Open File Backup tab. Set snapshot
provider to User Veritas Volume Snapshot Provider. Set Snapshot error control
to disable snapshot and continue.
Host propertiesclientsclient
nameWindows
This isn't really NBU related, but figured someone
here could help out.
We need to start doing system configuration backups
to local DAT drives on our HP9000 machines. We've got 2 machines with
slightly older DAT4 drives, and one brand-new machine with a DAT72 drive.
To ensure
We have several Redhat LInux servers (AS 3) use Veritas Netbackup client to
backup file systems. I checked /usr/openv/netbackup/logs/bpbkar/log.
file and it did NOT show detail backup information like :
03:10:18.082 [6439] 4 bpbkar: INF - Compression: 25%
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You also need to make VERBOSE = 5 in the bp.conf file on the client.
Peter DrakeUnderkoffler
Xinupro, LLC
617-834-2352
bbb bb wrote:
We have several Redhat LInux servers (AS 3) use Veritas Netbackup client
to backup file systems. I checked
[EMAIL PROTECTED] wrote:
bplist -C client -k policy -t 13 -s 2/5/2006 -e 2/10/2006 -S master
media server -l -R /$PATH
I recommend using the first bplist command with a pathname of /. That
way, you can see all of the paths in the database in the event that
you're specifying the path
22 matches
Mail list logo
