Anonymous_User Absent Member.
Absent Member.
2381 views

backout.tts now not on SYS volume

After troubles with backout.tts and deleting it from SYS (see Deleting the
BACKOUT.TTS file. - TID10019826
http://support.novell.com/cgi-bin/search/searchtid.cgi?10019826.htm )
backout.tts resides on another (not SYS) volume - KVIT.
And when server boot volume KVIT mounted first when TTS enabled .
How I can return backout.tts on volume SYS?

Best regards,
Peter Voronov

Labels (2)
0 Likes
3 Replies
Anonymous_User Absent Member.
Absent Member.

Re: backout.tts now not on SYS volume

Backout.tts resides on each volume which has TTS enabled and some TTS
transactions that are not yet committed. Presumably KVIT had this file
there all along and you only just noticed. If you don't need it you
could delete it too.
--
Andrew C Taubman
Novell Support Forums Volunteer SysOp
http://support.novell.com/forums
(Sorry, support is not provided via e-mail)

Opinions expressed above are not
necessarily those of Novell Inc.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: backout.tts now not on SYS volume

> Backout.tts resides on each volume which has TTS enabled and some TTS
> transactions that are not yet committed. Presumably KVIT had this file
> there all along and you only just noticed. If you don't need it you
> could delete it too.
> --

I am sorry.
This is Netware 6.0 system with traditional volumes only.
And usually backout.tts is recides on SYS colume, are not?

Best regards,
Peter Voronov
P.S. Sorry for my bad English.

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: backout.tts now not on SYS volume

>usually backout.tts is recides on SYS volume,

SYS will have this file if there are TTS transactions uncommitted on
SYS, yes. If there are uncommitted TTS transactions on KVIT then it will
have one also.
--
Andrew C Taubman
Novell Support Forums Volunteer SysOp
http://support.novell.com/forums
(Sorry, support is not provided via e-mail)

Opinions expressed above are not
necessarily those of Novell Inc.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.