Windows backup

[Paul Harms]

Yesterday I tried to backup a Windows client but I encountered a 
major error. I  am using Retrospect 4.2 on a PM 7100/66 and doing 
client backups (Mac/Win) via TCP/IP. I have sucessfully backed up two 
other Windows clients both operating on Windows98. However I tried 
last nite to backup a Windows95 client (I first ran the Microsoft 
Socket Patch as outlined in the manual) which started out OK until 
about half way through when Retrospect gave a "lost communication" 
error. The Windows client was not in use and when I went to check it, 
the screen was in DOS mode and displayed something like "trouble 
writing file to C disk" I had no option other than to force restart 
it and eventually I got it back to normal. Any ideas what may cause 
this.

TIA
-- 
Paul Harms,
Mac/Scanner Operator,
Toronto,  CANADA


--
--
To subscribe:[EMAIL PROTECTED]
To unsubscribe:  [EMAIL PROTECTED]
Archives:
Problems?:   [EMAIL PROTECTED]

What is the security in Retrospect?

[Maurice Volaski]

Some users here have asked about how secure Retrospect is.

Specific points of concern are how secure is security code password 
that is stored by the Retrospect client and as well by the Retrospect 
server (for scripted operation)? Why are the passwords displayed in 
clear text when they are first setup in the client?

How secure is the data that is being backed as it passes over the 
network? For example, if I choose to have DES encryption on the tape, 
is that DES implemented on the server as data is about to be written 
to the tape or has the data already been DES encrypted on the client 
side? I assume it can't be the latter since if the password to the 
tape is being used as the key, the client only has the security code, 
not the tape password.

Anyone running Retrospect with a security code to a client could back 
up it to take data off and then alter this data and then return the 
altered data to the client. Aside from this security code and 
blocking the TCP ports that Retrospect uses (via a router/firewall), 
are there any other ways to prevent an unauthorized copy of 
Retrospect from engaging in backup and retrieval? For example, what 
about the client knowing the IP identify of the server and rejecting 
any server not having that IP address?
-- 
--
Maurice Volaski, [EMAIL PROTECTED]
Computing Support, Rose F. Kennedy Center
Albert Einstein College of Medicine of Yeshiva University


--
--
To subscribe:[EMAIL PROTECTED]
To unsubscribe:  [EMAIL PROTECTED]
Archives:
Problems?:   [EMAIL PROTECTED]

Re: Autoloader Oddity

[Eric Ullman]

Naming the tapes ahead of time may or may not work, depending on the state
of the autoloader and when the media request occurs. There is a flaw in
Retrospect's logic when choosing tapes from a loader. This is a complex
issue, so please read this carefully.

Also, we consider this a bug, and we will correct this behavior in future
releases of both Mac and Windows products.


RETROSPECT, AUTOLOADERS, AND ERASED MEDIA

If all tapes are known then Retrospect does not use the properly pre-named
tape if it's erased and instead uses the first or last blank one.

In both Mac & Windows products, Retrospect will always use the pre-named
tape if it has to search the loader for tape names, regardless of whether
the pre-named tape is erased or has Retrospect data on it. However, if the
tape names are known (already scanned), Retrospect will use the pre-named
tape if it's got Retrospect data on it but will use the first (Mac
Retrospect) or last (Win Retrospect) erased/unnamed tape if the pre-named
tape is erased.


EXAMPLES

In the following scenarios, there are 3 tapes in the loader slots in this
order: erased tape/no name, erased or non-erased tape/pre-named, erased
tape/no name.

We run a scripted backup to these tapes in two loader states: 1) tapes are
scanned and known (i.e., tape names are displayed in the UI); 2) tapes are
not scanned and are unknown (i.e., tapes names display "?" or "Unknown").

(On the Mac, Retrospect will almost always have to search all the tapes
since memory of the tape names is not retained after re-launching.)

Retrospect for Windows 5.11
All known tapes w/ non-erased, pre-named tape: Uses the pre-named tape. All
known tapes w/ erased, pre-named tape: Uses the last erased tape found .

Unscanned tapes w/ non-erased, pre-named tape: Uses the pre-named tape.
Unscanned tapes w/ erased, pre-named tape: Uses the pre-named tape.

Retrospect for Macintosh 4.2
All known tapes w/ non-erased, pre-named tape: Uses the pre-named tape. All
known tapes w/ erased, pre-named tape: Uses the first erased tape found.

Unscanned tapes w/ non-erased, pre-named tape: Uses the pre-named tape.
Unscanned tapes w/ erased, pre-named tape: Uses the pre-named tape.


In a poor man's loader (two or more single cartridge tape drives),
Retrospect always chooses the pre-named tape whether it's erased or has
Retrospect data on it. If both are erased, the Mac & Windows product will
use the drive with the higher SCSI ID number.

I hope this sufficiently explains which piece of media Retrospect will
choose in various situations.

Best regards,

Eric Ullman
Dantz Development



Noah Eiger <[EMAIL PROTECTED]> wrote:

> Thanks for the tips. Does this mean that the method of "naming" the
> tapes ahead of time will NOT work? Does Retro look for an erased tape
> or an untitled tape?
> 
>> Hi Noah,
>> 
>> Retrospect will label erased tapes as it sees fit. If a tape is erased,
>> Retrospect ignores the tape's name. Retrospect will only look for a tape by
>> name once that tape has already been written to.
>> 
>> Your specific experience will differ if you are running a regular backup
>> script or a Backup Server script. Regular, scripted operations will ask for
>> tapes based on the specific scheduled operations you have set.
>> 
>> A Backup Server script, when instructed to use multiple backup sets, will
>> dynamically prioritize the media based on its own assessment of the
>> available backup sets. In an autoloader, when erased media is available,
>> Backup Server will assign the tapes to more than one backup set and rotate
>> between them automatically.
>> 
>> It's generally best to label the media *after* Retrospect decides what to
>> name each tape.
>> 
>> We also have a Backup Server FAQ which will should make its functionality
>> easier to understand.
>> 
>> http://www.dantz.com/index.php3?SCREEN=bscommonq
>> 
>> Best regards,
>> 
>> Eric Ullman
>> Dantz Development
>> 
>> 
>> Noah Eiger <[EMAIL PROTECTED]> wrote:
>> 
>>> Hello:
>>> 
>>> I have an HP DD3 Autoloader. It loads six tapes at a time.
>>> 
>>> Within Retrospect, I defined three storage sets (call them Moe,
>>> Larry, and Curly). I rotate them each week. At the start, I took 18
>>> blank tapes and labled them Moe1, Moe2,..., Larry1, Larry2, etc.
>>> 
>>> After several weeks, I got a message that it could not find Larry-6.
>>> Yet, the tape that I labeled Larry6 was in the drive.
>>> 
>>> When I asked Retrospect what it thought was in each slot of the
>>> autoloader (Configure>Devices), it said:
>>> 
>>> Slot 1: Larry-3
>>> Slot 2: Larry-2
>>> Slot 3: Larry-1
>>> Slot 4: Moe-4
>>> Slot 5: Larry-5
>>> Slot 6: Moe-1
>>> 
>>> It should look like:
>>> 
>>> Slot 1: Larry-1
>>> Slot 2: Larry-2
>>> Slot 3: Larry-3
>>> Slot 4: Larry-4
>>> Slot 5: Larry-5
>>> Slot 6: Larry-6
>>> 
>>> 
>>> Remember, these were blank tapes at the beginning of the week.
>>> 
>>> Any ideas?



--
--
To subscribe:[EMAIL PROTECTED]
To unsu

Re: Autoloader Oddity

[Noah Eiger]

Thanks for the tips. Does this mean that the method of "naming" the 
tapes ahead of time will NOT work? Does Retro look for an erased tape 
or an untitled tape?

>Hi Noah,
>
>Retrospect will label erased tapes as it sees fit. If a tape is erased,
>Retrospect ignores the tape's name. Retrospect will only look for a tape by
>name once that tape has already been written to.
>
>Your specific experience will differ if you are running a regular backup
>script or a Backup Server script. Regular, scripted operations will ask for
>tapes based on the specific scheduled operations you have set.
>
>A Backup Server script, when instructed to use multiple backup sets, will
>dynamically prioritize the media based on its own assessment of the
>available backup sets. In an autoloader, when erased media is available,
>Backup Server will assign the tapes to more than one backup set and rotate
>between them automatically.
>
>It's generally best to label the media *after* Retrospect decides what to
>name each tape.
>
>We also have a Backup Server FAQ which will should make its functionality
>easier to understand.
>
>http://www.dantz.com/index.php3?SCREEN=bscommonq
>
>Best regards,
>
>Eric Ullman
>Dantz Development
>
>
>Noah Eiger <[EMAIL PROTECTED]> wrote:
>
>>  Hello:
>>
>>  I have an HP DD3 Autoloader. It loads six tapes at a time.
>>
>>  Within Retrospect, I defined three storage sets (call them Moe,
>>  Larry, and Curly). I rotate them each week. At the start, I took 18
>>  blank tapes and labled them Moe1, Moe2,..., Larry1, Larry2, etc.
>>
>>  After several weeks, I got a message that it could not find Larry-6.
>>  Yet, the tape that I labeled Larry6 was in the drive.
>>
>>  When I asked Retrospect what it thought was in each slot of the
>>  autoloader (Configure>Devices), it said:
>>
>>  Slot 1: Larry-3
>>  Slot 2: Larry-2
>>  Slot 3: Larry-1
>>  Slot 4: Moe-4
>>  Slot 5: Larry-5
>>  Slot 6: Moe-1
>>
>>  It should look like:
>>
>>  Slot 1: Larry-1
>>  Slot 2: Larry-2
>>  Slot 3: Larry-3
>>  Slot 4: Larry-4
>>  Slot 5: Larry-5
>>  Slot 6: Larry-6
>>
>>
>>  Remember, these were blank tapes at the beginning of the week.
>>
>>  Any ideas?
>
>
>
>--
>--
>To subscribe:[EMAIL PROTECTED]
>To unsubscribe:  [EMAIL PROTECTED]
>Archives:
>Problems?:   [EMAIL PROTECTED]

-- 




Noah M. Eiger
Manager of Information Systems
Mother Jones Magazine / Foundation for National Progress
[EMAIL PROTECTED]
415-665-6637 x.204
http://www.motherjones.com




--
--
To subscribe:[EMAIL PROTECTED]
To unsubscribe:  [EMAIL PROTECTED]
Archives:
Problems?:   [EMAIL PROTECTED]

Re: out of Sync

[Matthew Tevenan]

Bad backup set header errors indicate Retrospect encountered a missing or
damaged file header, which contains information such as the file's name and
size.

We troubleshoot these as we do any other hardware-related error, by trying
to pinpoint the source. The first place to look is the media itself. Try
another tape. Does that one give the error as well? Does this error occur on
all tapes? If so, move on to other device troubleshooting.

Update SCSI card drivers if this is not the native SCSI bus. Take any other
devices off the SCSI chain. Try a backup. Does this work?

Use a cleaning tape to clean the drive's heads.

Try a different cable from the Mac to the tape drive.

Try a different terminator on the back of the drive. If the drive is
actively terminated, turn active termination off and put a physical
terminator on the back of the drive.

Try the drive on another Mac.

If you still get these errors after trying all these steps, the problem is
with your drive. The purpose of this troubleshooting is to pinpoint what
variable is causing the errors, and at the end, the only variable left is
the drive itself.

If you have further questions, please feel free to contact our European
support team:

For support in English:
(from the UK) 0800 169 77 64
(outside of the UK) +33 1 40 29 11 08

For support in German:
(from Germany) 0800 180 21 21
(from outside Germany) +33 1 40 29 11 08

Regards,

Matthew
Technical Support Specialist
Dantz Development Corporation
925.253.3050 
[EMAIL PROTECTED]

> From: [EMAIL PROTECTED] (Dantz)
> Reply-To: "retro-talk" <[EMAIL PROTECTED]>
> Date: Tue, 09 May 2000 16:13:27 +0200
> To: [EMAIL PROTECTED]
> Subject: out of Sync
> 
> Dear fellow listreaders
> 
> I hope you will be able to help me with input regarding a back-up problem.
> My server want me to resync my catalog on my storage set, but when doing
> so nothing happens except in the log were retrospect add's 11.000 lines
> saying : 
> 
> Bad Backup set heder found (0x20202020 at 145.950.778).
> Bad Backup set heder found (0x20202020 at 145.951.290).
> Bad Backup set heder found (0x20202020 at 145.951.802).
> Bad Backup set heder found (0x20202020 at 145.952.314).
> Bad Backup set heder found (0x20202020 at 145.952.826).
> 
> an keeps going on for another 11.000 lines.
> 
> I'm using a AIT 25-50 GB drive with an 16 k chip tape.
> 
> Any comments or ideas would be greatly appreciated.
> 
> Kind regards,
> TSM/Jesper Greve
> 
> Telefon:  +45 4583 1222
> Telefax:  +45 4583 1322
> E-mail:   mailto:[EMAIL PROTECTED]
> Internet: http://www.tsm.dk/



--
--
To subscribe:[EMAIL PROTECTED]
To unsubscribe:  [EMAIL PROTECTED]
Archives:
Problems?:   [EMAIL PROTECTED]

out of Sync

[Dantz]

Dear fellow listreaders

I hope you will be able to help me with input regarding a back-up problem.
My server want me to resync my catalog on my storage set, but when doing
so nothing happens except in the log were retrospect add's 11.000 lines
saying : 

Bad Backup set heder found (0x20202020 at 145.950.778).
Bad Backup set heder found (0x20202020 at 145.951.290).
Bad Backup set heder found (0x20202020 at 145.951.802).
Bad Backup set heder found (0x20202020 at 145.952.314).
Bad Backup set heder found (0x20202020 at 145.952.826).

an keeps going on for another 11.000 lines.

I'm using a AIT 25-50 GB drive with an 16 k chip tape.

Any comments or ideas would be greatly appreciated.

Kind regards,
TSM/Jesper Greve

Telefon:  +45 4583 1222
Telefax:  +45 4583 1322 
E-mail:   mailto:[EMAIL PROTECTED] 
Internet: http://www.tsm.dk/




--
--
To subscribe:[EMAIL PROTECTED]
To unsubscribe:  [EMAIL PROTECTED]
Archives:
Problems?:   [EMAIL PROTECTED]

Re: Solution ->[SOT?] Retrospect causing ASIP crash?

[Radu-Dan Sabau]

Hello, Eric Zylstra ([EMAIL PROTECTED]). On 4.5.2000 22:21 you
wrote:

>Retrospect will cause ASIP to choke when it tries backing up files
>with corrupt resources.  If you find any such files with corrupt
>resources, try to repair them with ResEdit and/or trash them.  The
>crashes aren't always triggered immediately, either.  It can take a
>number of minutes after the backup completes.

This is EXACTLY my experience. However, I hope Dantz will come out with a
solution for this - we have file servers with 100'000+ files on them and
I just simply can't stand this coming in the morning and finding a server
freezed after the night backup for just a &%ç*! file sporting a corrupt
resfork, nor can I spend my whole day looking for corrupt files on our
servers.

-- R. Sabau


--
--
To subscribe:[EMAIL PROTECTED]
To unsubscribe:  [EMAIL PROTECTED]
Archives:
Problems?:   [EMAIL PROTECTED]