I have a client who wants to secure only some personnel files, but not
everything, so anyone on the staff can restore their own files should they
need to. But the secured files could only be restored using a password. It
sounds like Retrospects security applies to the entire Backup Set or the
Retr
How feasible is it to backup a remote office over a DSL line? A client has
a backup server at their main office and a remote site with 3 Macs. Each
office has DSL. Assuming we can get through the firewalls, and get static
IPs at the remote site, is it just a matter of entering the remote IPs in
> How feasible is it to backup a remote office over a DSL line? A
> client has
> a backup server at their main office and a remote site with 3 Macs. Each
> office has DSL. Assuming we can get through the firewalls, and get static
> IPs at the remote site, is it just a matter of entering the re
Retrospect Gurus:
In patching some Retro.Startup Extensions so that Retrospect will function
automatically behind the "BlackWatch" password-protected screen saver, I
find that although Retrospect 4.2 is in use on every target machine, the
Extension can vary anywhere from (and between) version 3.0
I get this error quite a bit but it is intermittent? One night backups may
work fine and the next night I may get this error on one of my volumes?
We are using a central backup server with an HP Surestore 818 Library
attached. The backup server is a 600Mhz NT4 Server with 256MB of RAM and
plenty
On 11/7/00 8:00 AM, [EMAIL PROTECTED] thus spake:
>How feasible is it to backup a remote office over a DSL line? A client has
>a backup server at their main office and a remote site with 3 Macs. Each
>office has DSL. Assuming we can get through the firewalls, and get static
>IPs at the remote
On 11/7/00 7:52 AM, [EMAIL PROTECTED] thus spake:
>I have a client who wants to secure only some personnel files, but not
>everything, so anyone on the staff can restore their own files should they
>need to. But the secured files could only be restored using a password. It
>sounds like Retrospect
> >I do it, but it's slow.
> >
> >I think the best way to accomplish the task would be to do a
> duplicate from
> >the source drive to a local drive, and then back up the local drive.
>
> If the slow speed is a result of the connection speed, this won't
> save time will it?
Because it's so slow,
On 11/7/00 3:26 PM, [EMAIL PROTECTED] thus spake:
>
>(BTW -- if it were me with three computers, I would probably put a tape
>drive on one of the computers and have the reports sent to me via email so I
>could monitor the status of the backups. I just do this with one computer --
>mine -- with a
