- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: Unable to verify data on DDS-3
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2008 07:16 AM
07-14-2008 07:16 AM
Re: Unable to verify data on DDS-3
tar -cvB -C /mtms . -C /mtmsdb . -C /mtmsdb1 . -C /mtmsdb2/mtmsdb1
The AUTOBACKUP uses:
tar cvB -C /mtmsdb1 . -C /mtmsdb2/mtmsdb1
Whats the difference between -cvB and cvB?
Thanks,
Phil.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2008 11:07 AM
07-14-2008 11:07 AM
Re: Unable to verify data on DDS-3
mtmsadm 6559 6601 0.0 20:05:08 ttyp1 0:00.01 grep rmt0
regards,
Phil.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2008 10:37 PM
07-14-2008 10:37 PM
Re: Unable to verify data on DDS-3
[quote]
Mon Jul 14 19:50:00 BST 2008 Start of CRON processing
mTMS backup procedure: /mtmsdb/recovery.log renewal
Recovery file /mtmsdb/recovery.log will be moved to /mtmsdb/LOG07141950.LOG
Backup Successful
Previous /mtmsdb/recovery.log now in /mtmsdb/LOG07141950.LOG
New /mtmsdb/recovery.log now created
Backup of Database Complete ..You May Resume Normal MTMS operations now .
Mon Jul 14 21:16:10 BST 2008 End of CRON processing
[/quote]
I ran: tar tvf /dev/rmt0h to verfy data has been written to the tape. The final few entries are below:
[quote]
-rw-rw-r-- 1000/1000 344064 Jul 14 12:05:25 2008 ./DSACCA.idx
-rw-rw-r-- 1000/1000 1316864 Jul 14 12:05:25 2008 ./DSACCA.dat
drwxrwxr-x 1003/1000 0 Sep 25 15:28:59 2007 .
-rwxrw-rw- 1000/1000 2315800576 Jul 14 14:07:47 2008 ./DSCLED.dat
-rwxrw-rw- 1000/1000 697363456 Jul 14 14:07:47 2008 ./DSCLED.idx
[/quote]
As you can see the files have a last modified date = to yesterday July 14.
I will monitor this evening as I only have 1 previous good backup (there may just be an issue with the Weekly?).
Many thanks for keeping pace with this post.
Phil.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2008 12:28 AM
07-15-2008 12:28 AM
Solutionapearently at 19:07 the process was not yet accessing the tapeunit, so the grep for rmt only returned your own grep-command.
the first line of the mail confirms this:
"Mon Jul 14 19:50:00 BST 2008 Start of CRON processing"
which matches this enry in the crontab of user mtms :
"50 19 * * 1-4 /mtms/bin/Nightly.jcl > /mtms/tmp/cron.out"
wich in turn starts "/mtms/bin/AUTOBACKUP"
as i stated before a "#" normally denotes a comment in shell scripts, but the filenames ending with ".jcl" and other commands within these scripts suggest you are using a script-environment other than sh or ksh wich DOES reads and interprets the lines starting with "#"
in the weekly script all lines adressing mail are "#"-ed, in the autobackup they are not!
so maybe it does run, but doesn't mail!
the difference between -cvB and cvB is "historical". originally "-" was used to specify options on commands.
in later tru64 versions the options can be specified without this character.
see attached note from "man tar".
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2008 02:06 AM
07-15-2008 02:06 AM
Re: Unable to verify data on DDS-3
Many Thanks,
Phil.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2008 02:10 AM
07-15-2008 02:10 AM
Re: Unable to verify data on DDS-3
my hat will change as this will tip me over the edge from baseball-cap to graduate-cap.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2008 02:18 AM
07-15-2008 02:18 AM
Re: Unable to verify data on DDS-3
Well deserved I am sure.
Kind Regards,
Phil.
- « Previous
-
- 1
- 2
- Next »