If you're vault is running in a policy, check to see if the client is still
listed.
After the upgrade, the client feild was blank had to use bpadm to enter the
server name in the policy because our nbsl daemon was freaking out periodically.
The ease of the upgrade depends on many things. The type of servers you have,
number of clients, etc.
You'll want to look at the HCL find out if your hardware meets the minimum
requirements for NBU 7.x.
Windows 2000 is no longer supported, neither are several 32 Bit OS's.
It seems most eveyone
Geeks? Ha! if you only knew. . .
The purpose of SLP is a hugh concept one that you need to understand. This is
a great step towards Tiering your storage - or whatever you might like. Sounds
like more confusion? . . . wait there's more.
A Storage Lifecycle Policy is a pre-defined
Hello,
Define the translationsin the /etc/hosts file on the Master, Media the client
if you are not using DNS to resolve these for you.
+--
|This was sent by rick.br...@publix.com via Backup Central.
|Forward SPAM to
Hello,
Your question needs to be answered by this question:
When a DR occurs you need to recover the data. Can it be done in the timeline
the business allows?
The business area's recovery timeframe needs to dictate the backup methology.
Nevermind the schedules, retentions or even the speed of
Hello,
I would recommend having identical hardware for your windows servers, then on
the primary NBU server, run it on mirrored internal disks.
If one of the disks fails, you can still run on the other. In the event the
primary server fails, you should be able to remove one of the disks and
You may have a failed NBU daemon. Suggest checking all the NBU services and
possibly cycle the services.
+--
|This was sent by ivxbr...@gmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
Hello Felix,
All I can tell you is you have to start somewhere and work from there.
Try to utilize the checkpoint features where you can for the WAN based backups.
I don't know of anyone having a document listing how they have their backup
infrastructure setup. Too many variables and most
Just a guess here but could it be the master server can't handle the
forwad-slash?
I've see this happen on some mixed systems where the Unix master server wasn't
able to handle the Windows directory path to restore data NBU was able to
backup. This was an NBU 6.5.2 thing and has been fixed in
Please check your exclude list for anything like *tmplog.
+--
|This was sent by ivxbr...@gmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
10 matches
Mail list logo
