[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference turris::digital_unix

Title:	DIGITAL UNIX(FORMERLY KNOWN AS DEC OSF/1)
Notice:	Welcome to the Digital UNIX Conference
Moderator:	SMURF::DENHAM

Created:	Thu Mar 16 1995
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	10068
Total number of notes:	35879

8666.0. "wrong date of previous vdump (lev. 1)" by MUNICH::CUZUM () Fri Jan 31 1997 06:42

Hi folks,

could you please help me with this one?

Customer has Digital Unix V3.2g. Until now he made only vdumps of Level
0. On January, 23 at 12:00 o'clock he made his first vdump level 1 an
was astonished to see the date of last level 1 dump: 22.01 1:04 instead
of the begin of the epoch. (Last level 0 dump has been made on 22.01,
2:04 and this was saved correct in /etc/vdumpdates). After this first
level 1 dump was complete, we looked in the /etc/vdumpdates and we found
the correct date and time.
On January, 23 we started a new vdump level 0, which showed the as date
of the last vdump, level 0 'the begin of the epoch', although in
/etc/vdumpdates there was the correct date and time (22.01, 1:04). After
this level 0 vdump we started again a level 1 vdump. It showed as date of i
the last level 1 dump: 23.01, time_of_vdump0 - 1 hour, although in
/etc/vdumpdates we have the correct time of the last level 1 vdump. We
tried again a level 1 vdump and again it showed us the date of the last
level 0 dump and the time of the last level 0 dump minus 1 hour.

I have no possibility to test this here on v3.2g and I found no patches
or hints related to the problem. Does anyone know about this problem or
has anyone any ideas?

Regards,

Corina

T.R Title User Personal
Name Date Lines

8666.1 DECWET::DADDAMIO Design Twice, Code Once Mon Feb 03 1997 15:47 19

T.R	Title	User	Personal Name	Date	Lines
8666.1		DECWET::DADDAMIO	Design Twice, Code Once	`Mon Feb 03 1997 15:47`	19
	From the vdump man page: The vdump command backs up all files that are new or have changed since the latest backup date of all backup levels that are lower than the backup level being performed. If a backup level that is lower than the specified level does not exist, the vdump command initiates a level 0 backup. A level 0 backup, which is called the Epoch, backs up all files. >We tried again a level 1 vdump and again it showed us the date of the last >level 0 dump and the time of the last level 0 dump minus 1 hour. I'm not sure if you think the minus 1 hour is the problem or using the level 0 time is the problem. Using the level 0 time is explained by the manpage extract above. If you think it being off by 1 hour is the problem, then you should file a QAR. Please include printouts of the /etc/vdumpdates file and a cut and paste of the output of vdump instead of just writing a description as in .0.

    From the vdump man page:
    
    The vdump command backs up all files that are new or have changed
    since the latest backup date of all backup levels that are lower than the
    backup level being performed. If a backup level that is lower than the
    specified level does not exist, the vdump command initiates a level 0
    backup. A level 0 backup, which is called the Epoch, backs up all files.
    
    
    >We tried again a level 1 vdump and again it showed us the date of the last
    >level 0 dump and the time of the last level 0 dump minus 1 hour.
    
    I'm not sure if you think the minus 1 hour is the problem or using the
    level 0 time is the problem. Using the level 0 time is explained by the
    manpage extract above. If you think it being off by 1 hour is the
    problem, then you should file a QAR. Please include printouts of the
    /etc/vdumpdates file and a cut and paste of the output of vdump instead
    of just writing a description as in .0.