It is inherently faster than the old brick level because it uses a more recent and more efficient API, but again a lot depends on your individual installation.
How much performance improvement you will get is like subjective, and depends on a lot of the same things that affected the old brick...
Document level backup has been around for a while - even in 11.5 it is called the premium exchange agent. Backup speeds, especially brick/document level are highly subjective and it's impossible to guess without trying your own installation.
One advantage document level has over the old brick...
Generally agents are BACKWARD compatible, but you'll not be able to use newer versions of agents with an older server version - it is almost certainly why you are getting errors.
HP don't support libraries off the external SCSI port of their SMARTArray/RAID cards, you'll need to invest in a separate SCSI card.
Incidentally - if it's on a SAN, why not connect the library to the SAN via the fibre?
Secondly, ARCserve has built in Shadow Copy Support IIRC - although not...
OS sees two drives (correctly) and 2 libraries (which could
be considered correctly as the library is attached through 2
different scsi controllers)"
Therein lies your problem, if the OS is seeing two libraries, then so will ARCserve. It's really up to your failover software to manage the...
Plus the SAN Primary and distributeds need to be able to communicate to negotiate device locks so you need to consider this on the SAN zoning side too.
Drivers are not required so it is pointless installing them unless you are using StorPort drivers for the HBA.
Does the OS see two drives or one?
Is persistant binding used by the HBA?
Have you tried deleting the tape engine config reg hive and re-running device configuration?
see the end of...
By all means use the forum for help, but play fair and first help yourself by taking the time to read the detailed help PDF documents on the installation CD.
Not using brick level backup - brick level backup is automatically excluded for full system backups and is documented as such in the activity log. Dependant on the exchange version you can either restore the mailstore to a recovery group, or setup a temporary server with the same details...
It's really hard to see what the problem might be, being as the media use rules depend on the type of rotation that you use. For example the media rules in global options have zero effect if you are running any rotation - they are hard-set by the rotation itself.
Media pool issues are...
Simply blank the tapes and use an asterisk (*) as the tape name in the backup job - the tapes will be formatted with the date and time of the backup job when it runs.
Encryption is CPU intensive IIRC by enabling encryption, you asking for 162-bit triple-DES.
See these FAQs for more information:
http://supportconnect.ca.com/sc/redir.jsp?reqPage=search&searchID=FAQ343737
http://supportconnect.ca.com/sc/redir.jsp?reqPage=search&searchID=FAQ343744
You can try...
Nick, it really would depend on your backup strategy and rotation, and a little understanding of relational databases helps here too.
Maintenance, whether it be SQL or ARCserve's own database will only trim what has passed the prune retention time (by default 30 days), but the prune job doesn't...
*.tmp are auto-excluded by design anyway by ARCServe if I recall correctly. What I suspect you are referring to is files backed up as part of the system state/registry to which filters do not and cannot be applied.
I'm taking a guess this is the sort of thing you maybe stumbling across in the...
No, it is the exact opposite. Using catalog.DB means that detail information is NOT automatically merged to the database after a backup, but is held ready in case it is needed.
This has benefits in that :
1 Your DB doesn't get unwieldingly large - which is VERY easy these days especially if...
Dave, the DR option is essentially intended to restore the server to the same server hardware, whilst going from a G1 to a G3 may not seem a big deal, DR as you are finding may well have problems handling it.
I would suggest that you try manually loading the appropriate SCSI driver for the G3...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.