That's what we use, also a central bank, (Canada). Don't have as many remote
sites to deal with like the original poster to deal with though so not really
appropriate unless you bring all those arrays back centrally.
How I'd see it working is that you'd have client-side dedupe enabled on all
Hi all,
I am pretty new to NetBackup and we are right now building a new Testing
Environment.
It uses NetBackup Version 6.5.6
It includes 3 Servers:
Master Server: svrtfa025 Alias: svrtbm11
Media Server: svrtfa024 Alias: svrtbk11
Media Server: svrtfa023 Alias: svrtbk12
I did add the
May of you are probably like why would you do this? We have a pretty small
environment with only 2 clients. Most of the remote clients I rsync the data
to a local server from there we backup to disk.
Questions. Currently have 6.5.2 running on solaris .. does anyone have any
insight to this
May of you are probably like why would you do this? We have a pretty small
environment with only 2 clients. Most of the remote clients I rsync the data to
a local server from there we backup to disk.
Second reason is I've had quite a fair bit of issues with solaris and it
doesn't help I not
Gidday, I'm a bit confused by the Symantec documentation ... I've the
enterprise client and I want to backup the full vmdk volumes of all my
virtualised servers ... but only non-RDM mapped volumes.
If I use ALL_LOCAL_DRIVES will that include RDM volumes? The documentation
appears to say that
You can perform below steps to achieve this:
1. First take a catalog backup on solaris master server and save the DR file in
safe place
2. Build a windows master server with same hostname and ipaddress as for
solaris one and DO NOT PUT ON NETWORK
3. Detach the any devices directly attached to
I do not think that it is so easy.
If you done it yourself, then ok. But Symantec sells this service verrr
expencive.
I think that, at least, you have to change all catalog files from LF that
UNIX systems use to CR/LF for windows.
This is a blog from someone that has done the opposite.
