ADSM-L

AW: Renaming Filesystems

1997-05-22 04:03:49
Subject: AW: Renaming Filesystems
From: "Bartl, Michael" <michael.bartl AT ZENTRALE.ADAC DOT DE>
Date: Thu, 22 May 1997 09:03:49 +0100
First of all the ADSM-Server has a list of nodes. When a client backs up
data the server does not know anything about driveletters but only looks
at the drive label. If a drive label occurs to be new, a new filespace
is created.

When you have to rename a drive label, you need to rename the filespace
within the ADSM server at the same time (at least before the next
scheduled incremental backup).

When you link to a drive through your LAN there are two reasons for ADSM
to decide that the filespace is new:
1. The Filesystem type is not NTFS but RMT-NTFS (don't know if this is
enough for getting a new filespace)
2. The system creates a new volume name by adding the drive letter it is
mounted to.
    e.g. you mount the drive labelled "APOLLO_D" to drive letter "F:"
and get a filespace name "APOLLO_D_F:" when backing up with ADSM.

Regards,
  Michael
--
Michael H. Bartl, ADAC e.V. (IDL/PPO)
Michael H. Bartl, ADAC e.V. (IDL/PPO)
Tel.: (089) 7676-4063, Fax: (089) 7676-8161
EMail: Michael.Bartl AT Zentrale.ADAC DOT de

>----------
>Von:   dan thompson[SMTP:thompsod AT USAA DOT COM]
>Gesendet:      Mittwoch, 21. Mai 1997 17:24
>An:    ADSM-L AT VM.MARIST DOT EDU
>Betreff:       Re: Renaming Filesystems
>
>Dianne,
>
> We have successfully renamed filespaces on NT boxes before.  ADSM
>obviously does some sophisticated checking when deciding if a filespace is
>the same as one found previously.  For example, a cohort of mine attempted
>to remotely backup a drive by redirecting it to his workstation with the
>same drive letter as the drive on the server.  When a backup was started,
>it detected it as a different filespace.  Hopefully, someone can give you a
>specific answer.
>
>Good luck,
>
> Dan T.
>
>----------
>> From: Dianne Sharp <DSHARP AT CLEAR.CO DOT NZ>
>> To: ADSM-L AT VM.MARIST DOT EDU
>> Subject: Renaming Filesystems
>> Date: Tuesday, May 20, 1997 5:16 PM
>>
>> We recently upgraded one of our Netware 3.11 servers to Netware 4.11 and
>> re-organised some of the volumes, e.g. SYS1 became APPS.
>>
>> I used the ADSM Rename Filespace command on the server to rename
>> servername/SYS1: to servername/APPS:  However, when we did the first
>> incremental backup of the new server, all files under APPS appear to
>> have been backed up again, causing our backup to take over 15 hours.
>>
>> I thought by renaming the filespace, it would save us time, but this
>> doesn't appear to be the case.
>>
>> Can anyone shed any light on this for me please?
>>
>> Dianne Sharp
>> Operations Analyst
>> ISS CUSTOMER SUPPORT
>> Ext 4208
>
<Prev in Thread] Current Thread [Next in Thread>
  • AW: Renaming Filesystems, Bartl, Michael <=