I've got all the individual posts dating back to 6/23/99.
Brad.
-Original Message-
From: Gene Kubicki [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 21, 2000 4:26 PM
To: [EMAIL PROTECTED]
Subject: VXA drives
I bought a VXA drive from Ecrix 2 days ago, very easy to set up with
I'll second that emotion.
It is darn near a *daily* battle to keep my BackupExec backups running on my
NT servers. From BackupExec hanging to it not liking the tapes I just erased
for the night's round of backups, it's a pain.
Retrospect is a little better. I created the scripts a long time
I hope Retro will be able to tell a CLIENT to do something (like run a batch
file). That would be REALLY helpful if I could turn off virus software to
speed the client up...
Brad.
-Original Message-
From: Craig Isaacs [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 28, 2000 9:33 PM
It's ALL good. Give us everything. ;-)
Brad.
-Original Message-
From: Craig Isaacs [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 29, 2000 3:04 PM
To: retro-talk
Subject: RE: Backing up FileMaker Pro 5 on a PC
I hope Retro will be able to tell a CLIENT to do something (like
I can assure you it works (or should).
I've got 3 BW G3-450s running Retro 4.2 with the ADK (1.6? 1.7?) that
supports HP's DLT Library (autoloader). The libraries are attached to
Adaptec PCI (duh!) PowerDomain 2940UWs.
It works flawlessly, and has for about 8 months so far.
I hav had a LOT of
Oops. Make that 2930UWs.
Brad.
--
--
To subscribe:[EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives:http://list.working-dogs.com/lists/retro-talk/
Problems?: [EMAIL PROTECTED]
You're gonna have to stop the Exchange services, I'm certain.
But, like anything, if you did perform a "cold" backup of
Exchange/SQL/Oracle/etc, you would be able to back it up successfully.
Mind you, I have not done this, since BackupExec lets me do a "hot" backup
of Exchange and SQL.
Brad.
Yup.
If the machine has a dial-up adapter listed (or remote access services) in
the networking control panel, it apparently is the case that the Retrospect
install chooses not to bind itself to the proper NIC.
Solution: Uninstall Retrospect. Uninstall the offending networking piece.
Install
To the best of my knowledge, the ONLY time you have to worry about IP
addresses is if and only if you used the machines' ip addresses to add them
to the retrospect client database.
If you added machines to the database by IP NAME or using Retrospect's
client browser, then you're OK.
One additional note:
Encryption and compression both take time and each takes more time as the
amount of encryption or compression increases.
So, backup performance will suffer if you choose to encrypting and/or
compress your backups. How much will depend on CPU speed(s), since both
processes
Retrospect has an option to export a report after each backup job.
After each night's backup jobs, Retrospect exports the backup report to
tab-delimited files. The IP addresses of the clients are in the report, in
one of the last columns.
Each morning, I've got a scheduled batch file (on NT)
Ideally, I'd like to know what files get updated, where the files go, and
any changes made to the registry.
That way, I could update their client software (by copying files and
importing registry keys) when the user logs into my NT domain. Then, I just
stop and restart the Retrospect Client
Is a reboot *really* necessary?
Or, can the service be stopped and restarted for full effect?
On initial installs, simply starting the newly installed service works...
Brad.
The guy who likes to automate and/or use the CLI for just about everything.
"The admin with the flattest butt wins."
"Native" is the actual amount of data that the tape can theoretically store,
before compression. A 12.0 Gig file should fit on a 12.0 Gig capacity tape.
Suppose you are able to take a 16.0 Gig file and compress it down (using
PKZIP or whatever) to 12.0 Gigs. Now that 16.0 Gig file can fit on the
Just FYI.
Just a couple notes for the list (and Dantz).
1. Attaching a Compaq DLT tape library to a Compaq ProLiant 6500 server's
built-in SCSI adapter doesn't work with BackupExec. I haven't tried it with
Retrospect, but would expect similar results. BackupExec couldn't talk
reliably talk to
I see this on Retrospect 5.15 with a Compaq server and a Compaq AIT loader
using the built-in SCSI port.
I do not see this on Retrospect 5.15 with a Compaq server and a Compaq AIT
loader using an Adaptec 2940UW.
Check your SCSI bus for errors (controller, cable, and device).
Brad.
Hi, All!
Well, I did some digging.
It IS possible to install (or uninstall) Retrospect Client 5.15 silently.
1. Using WinZip (or similar), extract the files contained in "CLIENT
SETUP.EXE" to a folder.
In this folder will be 10 files, one of them will be "SETUP.EXE".
2. In your C:\WINNT
It could be half-duplex vs full-duplex on the 100Mb connections.
If one switch port is trying to talk at full-duplex, but the other side of
the connection (other switch's port) is trying to talk half-duplex, then
performance drops dramatically.
If the switches are configurable (managed), ensure
Suppose the first client of the night meets the threshold value, so Backup
Server starts a backup.
30 seconds into the backup, the client's CPU-sucking OpenGL screen saver and
a virus scan both kick in.
Now, all your other clients are piled up behind this (now slow) client.
It's not perfect,
Does the solution have "RISC" as part of it?
;-)
Brad.
-Original Message-
From: Craig Isaacs [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 03, 2001 4:23 PM
To: retro-talk
Subject: Faster catalog matching (was RE: Anyone used Retrospect on
medium-large systems?)
- with a lot
Well, that's not *entirely* true. Retrospect scales with some difficulty,
though I'm learning to work around some of its shortcomings, and ranting
about some others.
I have about 1000 clients, currently being backed up by 3 Macs.
I am converting the 3 Mac servers into 4 NT servers, not because
Here's a message I posted on 11/9/00...
Upon re-reading what I wrote, I'd like to amend #2 by stating that the
server in question was a DL580, not a DL380.
Anyway, try a different SCSI adapter, rather than using Compaq's built-in
SCSI adapter.
--- begin old message -
Just FYI.
Adding by IP NAME is OK, too.
I'd avoid adding clients by IP ADDRESS if at all possible.
Brad.
-Original Message-
From: Irena Solomon [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 02, 2001 11:18 AM
To: retro-talk
Subject: Re: Client IP changes
Hi John,
If you let Retrospect find
Here's my 2c...
I was running Retro 4.2 on an 8100 without problem.
After I upgraded to Retro 4.3, I started getting asserts pretty frequently,
complaining that the catalog was out of synch, IIRC.
I replaced the RAM in the 8100 and the problem went away.
Brad.
-Original Message-
24 matches
Mail list logo