• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Migrate vol in akfiler7
 

Migrate vol in akfiler7

on

  • 320 views

 

Statistics

Views

Total Views
320
Views on SlideShare
320
Embed Views
0

Actions

Likes
0
Downloads
11
Comments
0

0 Embeds 0

No embeds

Accessibility

Upload Details

Uploaded via as Microsoft Word

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Migrate vol in akfiler7 Migrate vol in akfiler7 Document Transcript

    • Migrate vol for caseshare Inform process team mgr Mobarh. big01> snapmirror The following commands are available; for more information type "snapmirror help <command>" abort migrate release store break nvlogs resume throttle resync update destinations off help on retrieve initialize quiesce use status big01> big01> big01> big01> big01> snapmirror status Snapmirror is on. Source Destination State Lag Status big01:CASESHARE_JPM004 big01:CASESHARE_JPM004new Snapmirrored 00:08:40 Transferring (1868 KB done) big01> snapmirror status Snapmirror is on. Source Destination State Lag Status big01:CASESHARE_JPM004 big01:CASESHARE_JPM004new Snapmirrored 00:01:31 Idle type "snapmirror help <command>" abort migrate release store
    • break nvlogs destinations resume resync off help on initialize quiesce throttle update retrieve use status big01> cifs shares -delete JPM004 big01> snapmirror migrate big01:CASESHARE_JPM004 big01:CASESHARE_JPM004new negotiating with destination.... This SnapMirror migration will take local source volume: CASESHARE_JPM004 and complete a final transfer to destination: big01:CASESHARE_JPM004new using the interface named big01 After that, open NFS filehandles on the source will migrate to the destination and any NFS filehandles open on the destination will be made stale. Clients will only see the migrated NFS filehandles if the destination is reachable at the same IP addresss as the source. The migrate process will not take care of renaming or exporting the destination volume. As a result of this process, the source volume: CASESHARE_JPM004 will be made restricted, and NFS service to this filer will be stopped
    • during the transfer. CIFS service on the source volume will be terminated and CIFS will have to be set up on the destination. Are you sure you want to do this? y performing final transfer from big01:CASESHARE_JPM004 to CASESHARE_JPM004new.... (monitor progress with "snapmirror status") transfer from big01:CASESHARE_JPM004 to CASESHARE_JPM004new successful starting nfs filehandle migration from CASESHARE_JPM004 to CASESHARE_JPM004new Volume 'CASESHARE_JPM004' is now restricted. Updating the old fsid 1623730247 with new fsid -1954019814: start time 1912615568 Volume CASESHARE_JPM004 has had its FSID changed from 0x60c82847 to 0x8b88061a. source volume CASESHARE_JPM004 made restricted source nfs filehandles invalidated Updating the old fsid -1970984683 with new fsid 1623730247: start time 1912675040 Volume CASESHARE_JPM004new has had its FSID changed from 0x8a852915 to 0x60c82847. destination big01:CASESHARE_JPM004new confirms migration Mon Mar 14 12:14:40 PDT [big01: snapmirror.migrate.complete:notice]: SnapMirror migrate from big01:CASESHARE_JPM004 to big01:CASESHARE_JPM004new complete. migration complete big01> Mon Mar 14 12:14:41 PDT [big01: snapmirror.migrate.complete:notice]: SnapMirror migrate from big01:CASESHARE_JPM004 to big01:CASESHARE_JPM004new complete. big01> vol rename CASESHARE_JPM004 z_CASESHARE_JPM004_to_be_destroy_by_Mar_28_2011 exportfs [Line 2]: NFS not licensed; local volume /vol/CASESHARE_JPM004new not exported Renaming volume CASESHARE_JPM004 (fsid 8b88061a) to z_CASESHARE_JPM004_to_be_destroy_by_Mar_28_2011: start time 1912753033
    • Renaming volume CASESHARE_JPM004 (fsid 8b88061a) to z_CASESHARE_JPM004_to_be_destroy_by_Mar_28_2011: start time 1912753242 Renaming volume CASESHARE_JPM004 (fsid 8b88061a) to z_CASESHARE_JPM004_to_be_destroy_by_Mar_28_2011: start time 1912753483 'CASESHARE_JPM004' renamed to 'z_CASESHARE_JPM004_to_be_destroy_by_Mar_28_2011' big01> vol rename CASESHARE_JPM004new CASESHARE_JPM004 Renaming volume CASESHARE_JPM004new (fsid 60c82847) to CASESHARE_JPM004: start time 1912781313 Renaming volume CASESHARE_JPM004new (fsid 60c82847) to CASESHARE_JPM004: start time 1912781454 Renaming volume CASESHARE_JPM004new (fsid 60c82847) to CASESHARE_JPM004: start time 1912781589 'CASESHARE_JPM004new' renamed to 'CASESHARE_JPM004' big01> cifs shares -add JPM004 /vol/CASESHARE_JPM004 "Caseshare for JPM004" Warning: ignoring unknown share option: Caseshare for JPM004. big01> cifs shares -add JPM004 /vol/CASESHARE_JPM004 There is already a share named JPM004. big01> cifs shares JPM004 Name ---JPM004 Mount Point ----------- Description ----------- /vol/CASESHARE_JPM004 everyone / Full Control Log into sdptools02 sdpdpJPM004 Try write a file into it. Call case owner, process team Mgr Mobarsh