Nope. You verified what I believed to be the case. Although the
documentation suggests otherwise, and something that the original poster is
experiencing does as well, it's nice to see that it works as I thought it
should -- at least somewhere. ;)
Thanks.
-Original Message-
From:
Have a look at NetBackup Admin Guide I under the topic 'Media Type
Mappings tab' and below that section called 'Default and allowable media
types'. You will have to change the default (GUI or vm.conf). This
however will only work for new media. You will have to change existing,
unassigned media
Hi
I am getting the following:
18:03:22 INF - Skipping Backup Exec backup having backup set number 180.
Unsupported file system type :47
18:03:22 INF - Skipping Backup Exec backup having backup set number 181.
Unsupported file system type :59
18:03:32 INF - Skipping Backup Exec backup having
I'm currently running NBU 5.0 MP7 On Solaris 9 on an E220R
End goal is to get to NBU 6.5.4 on Solaris 10 on a new T5220.
Network based clients, mix of Win200, Win2003, Solaris 8
My upgrade path is going to be as follows. Does anyone see any issues
with this?
Build Sol10 on new box
Install NBU
Dave,
I would recommend installing your new server at 5.0MP7 and switching over
to it. Our upgrade path for new hardware has been to install NBU on the
new server, then copy a tarball of /usr/openv over and untar it on the new
server. Then swap IPs, hostnames, cabling, etc. and you're done. It
Thanks guys. Pretty much what i thought of doing.
I just need to clarify after upgrade to 6.5.4 if i need sol8 patches.
I then need to work out all the steps to install MSEO. Knightmare.
Cheers
rusty.ma...@sungard.com wrote:
Dave,
I would recommend installing your new server at 5.0MP7
There is a case open with Symantec about this issue, and I am told an EEB will
be made available soon.
You are not supposed to have to keep a full around, but once the full expires a
new full is taken automagically.
QuoteSo it appears I need to keep the Full backup around even though the
Yeh, I'm not crazy! Or at least about this one.
Thanks Jim H
From another JimH
-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Jim H
Sent: Wednesday, July 08, 2009 8:59 AM
To:
Just wanted to follow up with the solution on this. Blat was having
problems parsing the information passed to it and using the quotes already
in place around the subject variable, and thus failed. Removing the quotes
resolved the issue and mail is working. Blat version is 2.6.2, build Feb
25
I am getting the following:
18:03:22 INF - Skipping Backup Exec backup having backup set
number 180.
Unsupported file system type :47
18:03:22 INF - Skipping Backup Exec backup having backup set
number 181.
Unsupported file system type :59
18:03:32 INF - Skipping Backup Exec backup
Is there anybody use IBM TS3310? Can Netbackup use its path failover license?
My OS is Solaris 10 - Sparc.
Thanks,
Koping
+--
|This was sent by kopingw...@gmail.com via Backup Central.
|Forward SPAM to
I have a TS3310 but and have a failover license. I have never had had
the primary drive die so I have don't know if it works or not.
-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of KPwang
Sent: Wednesday,
There is a case open with Symantec about this issue, and I am told
an EEB will be made available soon.
You are not supposed to have to keep a full around,
No. You _must_ have a full plus subsequent TIR and diffs or cincs
to synthesize a new full, but it does not matter how the full was
As I stated in a previous post.
The issue here may not be Synthetic Backups.
An unsheduled Full backup(not synthetic) runs the next day !!!after I expire
the original full!!! The original Full was run manually. Using Calendar
based with no date to start.
Remember this was just a test to see
14 matches
Mail list logo
