| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1568.1 | | KITCHE::schott | Eric R. Schott USG Product Management | Wed Aug 28 1996 20:54 | 9 |
| 1568.2 | tried nsr patches ?? | NETRIX::"[email protected]" | david nield | Thu Aug 29 1996 07:41 | 40 |
| 1568.3 | DECsafe/DECnsr functionnality lack... | BACHUS::DEVOS | Manu Devos DEC/SI Brussels 856-7539 | Fri Aug 30 1996 02:53 | 19 |
| 1568.4 | Senior Unix Consultant | NETRIX::"[email protected]" | Jim Buttafuoco | Thu Oct 10 1996 12:22 | 12 |
| 1568.5 | | BACHUS::DEVOS | Manu Devos DEC/SI Brussels 856-7539 | Mon Oct 14 1996 08:38 | 7 |
| 1568.6 | Another solution? | CHEFS::TIMMIS_J | | Tue Feb 04 1997 09:56 | 37 |
| I am running a similar scenario and have the same problem.
Digital UNIX 3.2G NSR 3.2a ASE 1.3
The solution in .4 sounds good, BUT after reading all of note 1234 is
it a supported solution?
An alternative solution I am testing is to backup cluster hosts as
follows:
On each server, in a cron script create and mount advfs clones of all the
file systems associated with the service running on the server.
I then use NSR to backup the Cluster Host specifying all the clones as
save sets plus clones of any file systems that can failover
The cloned file sets would be unmounted and removed after the backup.
In the case of a failover occuring while the cloned filesets were
mounted, the ASE stop scripts would unmount the cloned filesets
(after ensuring the filesystems are not being used via lsof).
Any resulting backup failure would be re-run.
The main problem I see with this is that not all filesets within an
advFS domain are defined in the Disk Service i.e. the cloned filesets
are not in the Disk service. ASE documentation states that all
filesets within an advFS domain should be included within a disk
service, which I am assuming is to ensure successful failover -- is
this correct?
Is this feasable and/or supported?
What are you recommendations between this and .4?
Thanks in advance for any help
Jane Timmis
|
| 1568.7 | | XIRTLU::schott | Eric R. Schott USG Product Management | Tue Feb 04 1997 12:55 | 6 |
| Hi
You would have to check with the nsr folks...my understanding is
that they were patching to be able to determine that a clone is
part of an ase service correctly....
|
| 1568.8 | An ASE problem? | CHEFS::TIMMIS_J | | Tue Feb 04 1997 18:20 | 15 |
| Thanks for your prompt reply.
I don't believe it is an nsr problem but an ASE problem, in that file
systems cannot be added to a Disk Service automatically while the
service is running.
For an immediate solution, can anyone state whether under ASE the
following are supported:
i. umount a filesystem that is not being used but is
part of an ASE Disk service
ii. create a cloned file system outside ASE on an advFS domain that is
part of an ASE Disk service, ensuring that the cloned file system
is unmounted as part of ASE stop scripts.
Thanks again for any help
|
| 1568.9 | | KITCHE::schott | Eric R. Schott USG Product Management | Thu Feb 06 1997 07:44 | 30 |
| >
> I don't believe it is an nsr problem but an ASE problem, in that file
> systems cannot be added to a Disk Service automatically while the
> service is running.
File systems can not be added to the service definition of
a running service without doing the modify (which stops and
restarts the service).
Clones should be able to be added/removed, with the assumption that
mount, dismounting, creating and deleting of clones must be done
by other scripts (ie ASE does not do this for you).
User defined scripts may be one method of handling the above.
Adding and removing of disks to a service currently (V1.4a and earlier
releases) requires the service modification (and start/stop). We plan
to allow this to be online in V1.5 release (in future).
>
> For an immediate solution, can anyone state whether under ASE the
> following are supported:
> i. umount a filesystem that is not being used but is
> part of an ASE Disk service
> ii. create a cloned file system outside ASE on an advFS domain that is
> part of an ASE Disk service, ensuring that the cloned file system
> is unmounted as part of ASE stop scripts.
>
> Thanks again for any help
|
| 1568.10 | See NETWORKER notefile... | BACHUS::DEVOS | Manu Devos DEC/SI Brussels 856-7539 | Fri Feb 07 1997 08:47 | 11 |
| Hi,
Just to close this thread, the ASE service ADVFS clone filesystems are
NOW (DECNSR 4.2A + Patch 1,2,3,4 or DECNSR V4.2B + patch 1) correctly
recognised as ASE service filesystems. The still pending problem is the
command "savefs" which must have the "-F" parameter and the
undocumented/reserved for engineering parameter "-c client" argument to
accept and save the cloned filesystem.
Regards, Manu.
|