Purpose	A file-history archive holds frequent snapshots of a managed volumes configuration and (typically) its metadata. You can use the archive command to make the current snapshot rule send its configuration/metadata snapshots to a pre-configured file-history archive. After the snapshot rule starts sending this data to the archive, you can later query the archive for the volumes state at different times. These queries are useful for finding the back-end locations of the volumes files on different dates, as the volume migrates them from filer to filer. Use no archive to stop sending any snapshots to a file-history archive. This disables any record keeping by the current snapshot rule.
Mode	gbl-ns-vol-snap
Security Role(s)	storage-engineer or crypto-officer
Syntax	archive archive-name no archive   archive-name (1-64 characters) identifies the file-history archive where this rule should copy its configuration/metadata snapshots.
Default(s)	no archive
Guidelines	You can use show file-history archive for a list of archives on this ARX, and you can use show file-history archive ... contents to see the volume configuration and metadata that the archive holds. Only volume configuration and volume metadata are copied to a file-history archive; a snapshot rule does not copy any client files or directories. Use the contents command to control the information that is gathered by this snapshot rule.
Sample	bstnA(gbl-ns-vol-snap[access~/G~daily])# archive betaArchive uses the file-history archive named betaArchive to store configuration and metadata snapshots for the access~/G volume.
Related Commands	namespace -> volume -> snapshot rule contents file-history archive show file-history archive show file-history archive ... contents

Purpose	A file-history archive holds daily snapshots of a managed volumes configuration and (typically) its metadata. You create a snapshot rule in the volume that snapshots this information and then sends the snapshot to the volumes archive. A file-history archive resides on an external filer. In case of an issue with copying the snapshot to the archive filer, you can use the cancel snapshot archive command to cancel the copy operation.
Mode	priv-exec
Security Role(s)	crypto-officer, storage-engineer, or backup-operator
Syntax	cancel snapshot archive namespace ns volume path rule rule-name   ns (1-30 characters) is the namespace where a snapshot archive is in progress. path (1-1024 characters) identifies the specific volume, and rule-name (1-1024 characters) is the snapshot rule.
Default(s)	None
Guidelines	The CLI prompts for confirmation before canceling the archive operation; enter yes to proceed. This cancels the archiving process, not the snapshot process. Use this command to resolve an issue between the ARX and the filer behind the archives location.
Sample	bstnA# cancel snapshot archive namespace medarcv volume /rcrds rule rcrdsArchive   Confirming this command will cause all archiving operations in namespace 'medarcv' volume '/rcrds' associated with rule 'rcrdsArchive' to be cancelled. Proceed? [yes/no] yes cancels the archive operation for the rcrdsArchive rule.
Related Commands	namespace -> volume -> snapshot rule file-history archive location

Purpose	A file-history archive is where one or more managed volumes store their configuration and metadata snapshots. The managed volumes may store up to seven-years worth of snapshots, possibly taken on a daily basis. This is useful for querying past states of a managed volume, so that you can find file locations as they migrate between the volumes back-end filers. As time goes on, you can use the clear file-history archive command to remove older snapshots that are no-longer needed.
Modes	priv-exec
Security Role(s)	crypto-officer, storage-engineer, or backup-operator
Syntax	clear file-history archive name [metadata-only] [namespace ns volume vol]   name (1-64 characters) identifies a particular file-history archive. This is the particular archive from which you will clear some (or all) file-history records. metadata-only (optional) indicates that you want to delete volume metadata only, not the volume configuration. Volume metadata consumes much more space than the configuration, and it supports the show file-history virtual-service command for seeking file locations. That command would no longer be supported, but you can still use the show virtual path-history command to query the front-end service names of various times. If you omit this option, both metadata and configuration are deleted and neither query is supported. namespace ns (optional, 1-30 characters) focuses on archive records from the given namespace. volume vol (required after the namespace option, 1-1024 characters) narrows the focus to the archive records for a single volume.
Syntax: One Date	clear file-history archive name [metadata-only] date date ...   name is the file-history archive, as described above. metadata-only (optional) is also described above. date date (mm/dd/yyyy, such as 06/05/2009, or today) is a specific date for the file-history records to be cleared. ... represents the namespace and volume options described above.
Syntax: Contents During a Range of Dates	clear file-history archive name [metadata-only] start-date s-date ... clear file-history archive name [metadata-only] end-date e-date ... clear ... [metadata-only] start-date s-date end-date e-date ...   name and metadata-only are described above. start-date s-date (mm/dd/yyyy, such as 03/02/2009) is the beginning of the date range. If you provide no end-date (as shown in the first line above), the end date is today. end-date e-date (mm/dd/yyyy, such as 11/12/2009) is the end of the date range. If you provide no start-date (as shown in the second line above), the start is the date of the first snapshot in the file-history archive(s). ... at the end of each syntax line represents the namespace and volume options described above.
Syntax: Contents During a Time Leading Up to a Date	clear file-history archive name [metadata-only] count {days|weeks|quarters|months|years} before e-date ...   name and metadata-only are described above. count (1-100) is the number of days, weeks, or whatever time unit you choose next. days|weeks|quarters|months|years chooses the time unit. For example, 2 weeks, 3 quarters, or 7 months. before e-date (mm/dd/yyyy, such as 09/30/2009, or today) is the end of the time period. ... at the end of each syntax line represents the namespace and volume options described above.
Guidelines	The CLI prompts for confirmation before clearing any records from the archive filer; enter yes to proceed. Before you use this command, you can use show file-history archive ... contents to list the file-history records on the archive.
Sample	bstnA# clear file-history archive fileRecordsMed date 01/07/2009   WARNING: Confirming this command removes all archived metadata and volume configuration data dated between '01/07/2009' and '01/07/2009' inclusive from archive 'fileRecordsMed'.   Proceed? [yes/no] yes clears all the file-history records from the fileRecordsMed archive that were recorded on January 7.
Related Commands	file-history archive show file-history archive ... contents

Purpose	A file-history archive holds daily snapshots of a managed volumes configuration and (typically) its metadata. You can use the contents command to choose the contents of this rules snapshots: client-visible files, volume-configuration data, and/or volume metadata. Use no contents to eliminate one or more types of data from the current rules snapshots.
Mode	gbl-ns-vol-snap
Security Role(s)	storage-engineer or crypto-officer
Syntax	contents {user-data | volume-config [metadata]} no contents {user-data | volume-config}   user-data | volume-config [metadata] is a required choice. user-data represents files and directories that are visible to clients. This causes the rule to create snapshots on the volumes storage filers. volume-config represents a configuration file that describes this volume. This option only applies to a managed volume. This does not result in any snapshots unless you also choose the metadata option. The volume configuration can support queries with the show virtual path-history command, but not the show file-history virtual-service command. metadata (optional) includes the managed volumes metadata along with its configuration. This causes the rule to take a snapshot at the filer behind the volumes metadata share. The metadata occupies more disk space than the volume configuration, but it also supports file-specific queries with the show file-history virtual-service command.
Default(s)	contents user-data
Guidelines	A snapshot rule typically includes volume configuration/metadata or user data, not both. If the rule is designed for backing up client data, the default is sufficient. If the rule sends its data to a file-history archive, the contents are usually limited to volume configuration and metadata. A snapshot rule, if dedicated to volume configuration and metadata, deletes its metadata snapshot as soon as the snapshot is successfully copied to the archive filer. That is, the snapshot rule removes the snapshot from the filer behind the metadata share, and it removes all records of the snapshot from the ARX database. This conserves space on the metadata filer; the snapshot is not required after its contents are safely in the archive. For a snapshot rule that contains all forms of data, user-data and volume-config, the rule adheres to its retain count for all of its snapshots. This includes the snapshots in the volumes filer shares as well as the volumes metadata snapshots. The snapshot remove command can remove all of the rules filer snapshots, including those on the volumes metadata filer.
Sample	bstnA(gbl-ns-vol-snap[wwmed~/var~a])# contents volume-config metadata causes the a snapshot rule to keep the volumes configuration and metadata in its snapshots.   bstnA(gbl-ns-vol-snap[wwmed~/var~a])# no contents user-data stops the a snapshot rule from taking snapshots on its user-data filers.
Related Commands	namespace -> volume -> snapshot rule archive file-history archive

Purpose	Use the optional description command to set a descriptive string for the current file-history archive. A file-history archive is where managed volumes can store file-location records over a long period of time. Use the no form of the command to delete the description.
Mode	gbl-archive
Security Role(s)	storage-engineer or crypto-officer
Syntax	description text no description   text (1-255 characters) is your description. Surround the text with quotation marks () if it contains any spaces.
Default(s)	no description
Guidelines	This description appears in the output of the show file-history archive command.
Sample	bstnA(gbl-archive[flArch])# description archives for Med Cos specifies a description for the current file-history archive.
Related Commands	file-history archive show file-history archive

Purpose	Over time, a file may migrate through multiple shares in a managed volume. You can use the file-tracking facility to track these migrations. The file-history archive command creates (or edits) a storage depot for file-location records. A single file-history archive can hold these records for multiple managed volumes. Use the no form of the command to remove the configuration for a file-history archive from the ARX database.
Modes	gbl
Security Role(s)	storage-engineer or crypto-officer
Syntax	file-history archive name no file-history archive name   name (1-64 characters) is a name you choose for the file-history archive.
Default(s)	None
Guidelines	The CLI requests confirmation before creating the new archive object; enter yes to confirm. This places you into gbl-archive mode, where you use the location command to establish the filer share or ARX volume where the archive resides. You can also enter an optional archive description (gbl-archive) in this mode. You can create up to 24 file-history-archive objects on the ARX. The file-history records in an archive are snapshots, or point-in-time copies, of a managed volumes metadata and configuration. To keep these records for a particular managed volume, you create a snapshot rule in the volume. The contents of the snapshot rule are the volumes configuration and metadata instead of (or in addition to) client files and directories; use the contents command to set these options. Then use the archive command to send copies of the volume data to this archive. After one or more snapshot rules post their snapshots in a file-history archive, you can query the archive for file or directory locations at the time of each snapshot. Use the show file-history archive command to list all file-history archives, and use show file-history archive ... contents to list their contents (that is, their snapshots of volume configuration and metadata). To find which client-visible services existed at a time in the past, use the show virtual path-history command. The show file-history virtual-service command shows the locations of client files and/or directories on a given date or a range of dates. You can use these commands to find the location of a file on a date when it was backed up, and to find the location of the same file today.
Samples	bstnA(gbl)# file-history archive flArch This will create a new archive.   Create archive 'flArch'? [yes/no] yes bstnA(gbl-archive[flArch])# ... instantiates a new file-history archive named flArch.   bstnA(gbl)# no file-history archive betaArchive bstnA(gbl)# ... removes a file-history archive.
Related Commands	location description (gbl-archive) snapshot rule contents archive show file-history archive show virtual path-history show file-history virtual-service

Purpose	Use the find command to locate one files back-end filer and path. This finds a files location as of now, not from a previous time.
Mode	(any)
Security Role(s)	crypto-officer, storage-engineer, network-engineer, network-technician, or operator
Syntax	find host hostname-or-ip {nfs| cifs} share-name path path [verbose] hostname-or-ip identifies a virtual server by its external DNS hostname or Virtual-IP address. Use show virtual service for a list of all virtual servers and their Virtual IP addresses. (To look up DNS names at an external DNS server, you must first identify the server with the ip name-server command.) nfs | cifs is a required choice, determining the type of share that follows. share-name (1-4096 characters) is the name of the front-end share, as seen by clients. The show server-mapping command shows all front-end shares on the ARX, in the left column. path (1-4096 characters) is the virtual-file path within the front-end share. verbose (optional) adds the files NFS filehandles to the output.   find global-server fqdn {nfs| cifs} share-name path path [verbose] fqdn (1-255 characters) identifies a global server by its fully-qualified domain name (FQDN). Use show global service for a list of all global servers and their FQDNs. The remaining options are described above.   find namespace namespace path path [verbose] namespace (1-30 characters) identifies the namespace. Use show namespace for a list of all namespaces. path (1-4096 characters) is the virtual-file path within the namespace. This is the file path as seen by the client, starting with the volume path. verbose (optional) adds the files NFS filehandles to the output.
	find wins wins-name {nfs| cifs} share-name path path wins-name (1-255 characters) identifies a virtual server by its optional wins-name or one of its optional wins-alias names. The remaining options are described above.
Default(s)	None.
Guidelines	This command finds one files physical location. To find all file locations behind a namespace, use the nsck ... report metadata-only command. For files in multi-protocol (NFS and CIFS) namespaces, this shows the files physical location from an NFS point of view and a CIFS point of view. The output contains several fields to map the ARX-volume location of the file to the files physical location on the filer: Namespace identifies the namespace that contains the file. Logical Path shows the full path to the file from the clients perspective. This path starts from the root of the volume. NFS Physical Location is an NFS path to the physical file. This appears in ip-address:/path-to-file format. Managed Volume Path indicates that the path is on a direct volume, and the physical location is on an ARX managed-volume that is standing in as a filer. This field does not appear in the output unless it applies to this query. CIFS Physical Location is a CIFS path to the physical file. This appears in //ip-address/path-to-file format. If this is an NFS-only file in a multi-protocol (CIFS and NFS) volume, a message here indicates that the file has an inconsistent name. You can use the nsck ... report inconsistencies command to find all of the volumes inconsistent names. The verbose output shows two NFS filehandles for the file: Virtual File Handle is the filehandle that the ARX presents to clients. Physical File Handle is the filehandle that the server gave to the ARX. The filehandles may be incomplete for the find namespace command. Use one of the other versions (such as find host) for complete NFS filehandles. If there are any NFS symlinks (or symbolic links) in the path, they appear next. Each symlink in the path appears on one line, with a text arrow (->) pointing to the symlinks target file or directory. For example, a path of /myvol/dirA/Ydir/sub could show this entry, indicating that dirA is a symlink: /myvol/dirA -> /myvol/Xdir Each symlink path is fully resolved up to (and not including) the name of the symlink itself. For example, the above symlink indicates the real path for the dirA symlink, /myvol/Xdir. If sub was also a symlink, its entry starts with that real path, /myvol/Xdir, instead of the dirA name used in the path: /myvol/Xdir/Ydir/sub -> myvol/test/dir3 This second symlink entry shows the real path up to the sub symlink, and points to the real path for sub. The object is a symlink appears at the end if the final file or directory in the path is a symlink. This appears in the symlink-path -> real-object-path format shown above, where the symlink-path is a real path up to (but not including) the final name in the path.
Guidelines: File Tracking	This identifies a files location now; for a files location in the past, you can use file tracking. This can be useful for finding the correct filer-backup tape for a lost or compromised file. The file-tracking feature requires some configuration before you can make any file queries. Specifically, a managed volume requires a snapshot rule to regularly copy its configuration and metadata to a file-history archive. After some copies of metadata have been archived, you can use the show file-history virtual-service command to query file locations at different dates.
Samples	bstnA# find namespace wwmed path /acct/index.html   Namespace: wwmed Logical path: /acct/index.html NFS Physical location: 192.168.25.19:/exports/budget/index.html finds a file in a namespace.
bstnA# find host 192.168.25.14 nfs /claims path /stats/piechart.ppt   Namespace: insur Logical path: /claims/stats/piechart.ppt NFS Physical location: 192.168.25.21:/vol/vol1/NTFS_QTREE/insurance/stats/piechart.ppt CIFS Physical location: The file/directory on //192.168.25.21/insurance has an inconsistent name.
	finds a file behind a virtual server. The virtual server is exporting the file from a multi-protocol namespace, so it shows both NFS and CIFS locations for the file. This file has an inconsistent, NFS-only name.
bstnA# find global-server ac1.MEDARCH.ORG nfs /claims path /stats/piechart.ppt   Namespace: insur Logical path: /claims/stats/piechart.ppt NFS Physical location: 192.168.25.21:/vol/vol1/NTFS_QTREE/insurance/stats/piechart.ppt CIFS Physical location: The file/directory on //192.168.25.21/insurance has an inconsistent name.
	finds the same file behind its global server.
bstnA# find global-server insur.medarch.org cifs CLAIMS path /index.html verbose   Namespace: insur Logical path: /claims/index.html NFS Physical location: 192.168.25.21:/vol/vol1/NTFS_QTREE/insurance/index.html CIFS Physical location: The file/directory on //192.168.25.21/insurance has an inconsistent name.   NFSv3 Virtual File Handle (32 bytes): 0x0000000114000000010000000000070000000000000000000000000f00000000 Physical File Handle (32 bytes): 0x92660a0074e7b00020000000000202c09254ed00a58c004840000000bb438000
	provides a verbose display for another file behind the same global server.
bstnA# find global-server insur.medarch.org cifs CLAIMS path /common/reagentLists/stats/acmeIns.txt   Namespace: insur Logical path: /claims/common/reagentLists/stats/acmeIns.txt NFS Physical location: 192.168.25.21:/vol/vol1/NTFS_QTREE/insurance/stats/acmeIns.txt CIFS Physical location: //192.168.25.21/insurance/stats/acmeIns.txt   The following symlinks were dereferenced to find this path: /claims/common/reagentLists -> /claims/specs /claims/specs/stats -> /claims/stats
	finds another file behind the same global server, where the logical path contains two symlinks.
Related Commands	nsck ... report metadata-only

Purpose	Use the location command to identify the filer or ARX volume to be used for the current file-history archive. A file-history archive is where managed volumes can store file-location records over a long period of time. This is the specific storage location for those file-location records. Use the no form of the command to disconnect from the location and disable any file-tracking queries against it.
Mode	gbl-archive
Security Role(s)	storage-engineer or crypto-officer
Syntax	location filer name {nfs3 | nfs3tcp} share [path path] location filer name cifs share proxy-user proxy [path path] location namespace ns volume vol-path [path path] no location   name (1-64 characters) is external-filer name for this archives back-end filer. This is the filers name from the ARX configuration, which may or may not match the actual host name of the filer. nfs3 | nfs3tcp chooses the file-access protocol for this location. This is a required choice between NFSv3 over UDP (nfs3) or NFSv3 over TCP (nfs3tcp). share (1-64 characters) is the name of the back-end export or share. path (optional, 1-1024 characters) is a specific sub path in the back-end share (or ARX volume) where file-location records should be stored. We recommend a path that is hidden from most clients. proxy (for a CIFS filer, 1-32 characters) is the proxy-user configuration that the ARX uses as its identity when writing to or reading from the back-end-CIFS share. This requires read and write permissions, but does not necessarily need to belong to the Backup Operators group on the filer.   ns (1-30 characters) identifies a namespace on this ARX. vol-path (1-1024 characters) identifies a volume in the namespace above. If you use this syntax to place the file-history archive in a managed volume, you can use migration policies to balance the file-history records among multiple back-end filers.
Default(s)	no location
Guidelines	This command determines the physical location for the current file-history archive. Choose a filer or ARX volume with enough storage space for up to 7 years of file-history records. Each file-history record is a snapshot of the volumes configuration (and, typically, its metadata). Use the snapshot rule command to create a snapshot rule for each desired volume, then use the contents command to determine whether or not metadata is included in the volumes snapshots. Multiple managed volumes can share the same file-history archive. The schedule (gbl-ns-vol-...snap) for each volumes snapshot rule determines the frequency of these records, and the amount of space required over 7 years. For a current reading on the disk space consumed in the archive, you can use the show file-history archive ... contents command.
Guidelines: Archive Directory Structure	The snapshot rules create the following directory structure in the location filers share and path: /acopia_file_history /ARX-name-ARX-GUID /yyyy /mm /dd /namespace-name /volume-name /namespace-name /volume-name /dd ... /mm ... /yyyy ...
Guidelines: Client Exposure to the Archive	The only clients who should access this acopia_file_history structure are management personnel who understand its purpose. Uninformed clients may accidentally delete important archive records. Choose a location that is inaccessible to most clients. If you use a managed volume as your archive location, use a hidden directory for this data, or dedicate the entire volume to file-history archives and only export/share it to management clients (using export (gbl-cifs) or export (gbl-nfs)).
Guidelines: Moving the Location	For cases where the filer location is running low on disk space, you can use the no location command to stop all archive writes to the filer. You can then enter a new location command to identify the replacement filer or volume. To preserve all of your current file-history records at the new location, move the acopia_file_history directory from the former location to the new one.
Samples	bstnA(gbl-archive[fileRecordsMed])# location filer fs4 cifs arx_file_archv proxy-user repCred sets the location for the fileRecordsMed archive to a CIFS share on a back-end filer.   bstnA(gbl-archive[flArch])# location namespace wwmed volume /acct path fileArch sets the location for the flArch archive to a path in an ARX volume, wwmed~/acct.
Related Commands	file-history archive show file-history archive ... contents contents

Purpose	Over time, a file may migrate through multiple shares in a managed volume. You can set up a managed volume to periodically record its file locations on a file-history archive. Later, you can use commands to query the archive for the location of a file on a given date or dates. The show file-history archive command lists the archives on this ARX, their configurations, and the managed volumes that use them.
Modes	(any)
Security Role(s)	crypto-officer, storage-engineer, network-engineer, network-technician, or operator
Syntax	show file-history archive show file-history archive name [namespace ns volume vol]   name (optional, 1-64 characters) identifies a particular file-history archive. This invokes a detailed view of the archive, including its configuration and the volumes that use it. If you omit this option, the output is a list of all file-history archives on the ARX. namespace ns (optional, 1-30 characters) focuses on archive records from the given namespace. volume vol (required after the namespace option, 1-1024 characters) narrows the focus to the archive records for a single volume.
Guidelines	You can use this command to list the current file-history archives on the ARX, or to show the configuration of a particular archive. Before you can list any archives, you must use the file-history archive command to create an archive, and the location command to choose the archives home filer. The related show file-history archive ... contents command shows the archives contents. The archive gets its contents from one or more snapshot rules in one or more managed volumes. By showing the contents, you can learn how much disk space the archive is using on its back-end filer or ARX volume.
Guidelines: Summary Output	The summary version of the command lists all file-history archives in a table. The table contains one row per archive with the following fields: Archive Name is the name of the archive, defined by the file-history archive command. Description offers a short description for the archive. You can set or change this with the description (gbl-archive) command.
Guidelines: Detailed Output	If you identify a particular archive in the command, the output contains configuration details for that archive: Name is the name of the archive, defined by the file-history archive command. Location is the archives home filer or home volume. You can use the location command to change this. Description offers a short description for the archive. You can set or change this with the description (gbl-archive) command. Path is the path under the above location where the archive resides. The location command controls this. Protocol is CIFS or NFS. This is the file-access protocol that the ARX uses to copy files to the archive. For an archive on an external filer, the location command controls this. For an archive on a managed volume, this is controlled by the volumes namespace configuration. Proxy User is the name of the ARXs proxy-user credentials for accessing the archive filer or managed volume. After the name of the proxy-user configuration, the windows-domain (gbl-proxy-user) and user (gbl-proxy-user) appears in parentheses. Status is Online for an archive that is currently usable. FreeSpace shows the current free space on the archive. In use by is the title for a table of snapshot rules that add to this archive. The table contains one row per snapshot rule: Namespace is the namespace that contains the snapshot rule. Volume identifies the managed volume for this rule. Snapshot Rule is the name of the snapshot rule that has written to this archive.
Samples	bstnA(gbl)# show file-history archive lists all the file-history archives on the ARX. See Figure 31.1 for sample output.   bstnA(gbl)# show file-history archive fileRecordsMed shows details about a particular file-history archive. See Figure 31.2 for sample output.
Related Commands	file-history archive show file-history archive ... contents

Purpose	Over time, a file may migrate through multiple shares in a managed volume. You can set up a managed volume to periodically record its file locations on a file-history archive. Later, you can use commands to query the archive for the location of a file on a given date or dates. The show file-history archive ... contents command lists the file-history records stored in a particular file-history archive, and shows the amount of disk space that the records occupy.
Modes	(any)
Security Role(s)	crypto-officer, storage-engineer, or backup-operator
Syntax: Contents on One Date	show file-history archive name contents date date [namespace ns volume vol] [report prefix]   name (1-64 characters) is the file-history archive. contents is a required keyword. date date (mm/dd/yyyy, such as 05/06/2009, or today) is the date for your query. namespace ns (optional, 1-30 characters) focuses on archive records from the given namespace. volume vol (required after the namespace option, 1-1024 characters) narrows the focus to the archive records for a single volume. report prefix sends the output to a report file with the given prefix (1-255 characters). The report name is prefix_archive-name_mmddyyyyHHMM.rpt, where archive name is all or the name you provide in the next option, and the rest is the time the report was created. The exact report name appears at the CLI prompt after you type the command.
Syntax: Contents During a Range of Dates	show file-history archive name contents start-date s-date ... show file-history archive name contents end-date e-date ... show ... contents start-date s-date end-date e-date ...   start-date s-date (mm/dd/yyyy, such as 05/06/2009) is the beginning of the date range. If you provide no end-date (as shown in the first line above), the end date is today. end-date e-date (mm/dd/yyyy, such as 01/12/2009) is the end of the date range. If you provide no start-date (as shown in the second line above), the start is the date of the first snapshot in the file-history archive(s). ... at the end of each syntax line represents the namespace, volume, and report options described above.
Syntax: Contents During a Time Leading Up to a Date	show file-history archive name contents count {days|weeks|quarters|months|years} before e-date ...   count (1-100) is the number of days, weeks, or whatever time unit you choose next. days|weeks|quarters|months|years chooses the time unit. For example, 3 weeks, 2 quarters, or 5 months. before e-date (mm/dd/yyyy, such as 09/04/2009) is the end of the time period. ... at the end of each syntax line represents the namespace, volume, and report options described above.
Guidelines	You can use this command to list the snapshots on a file-history archive. Before you can list any archive contents, you must use the file-history archive command to create an archive, and the location command to choose the archives home filer or ARX volume. The archive gets its contents from one or more snapshot rules in one or more managed volumes. A volumes snapshot rule contributes to a file-history archive through the following options: the rule must choose the volumes configuration (and possibly its metadata) with the contents command, and must identify the file-history archive with the archive command. As time goes on, the metadata snapshots on the archive filer occupy progressively-more disk space. You can use this command to assess the consumed space, and you can use the clear file-history archive command to remove old snapshots from the archive filer. For a list of all file-history archives, use show file-history archive.
Guidelines: Output	The output of the archives contents contains three tables. Query Parameters displays all of your command-line choices with the following fields: Archive, Start date, End date, Namespace, and Volume. Switch shows the hostname and the GUID for the ARX that writes to this archive. It is possible for multiple ARXes to use the same archive filer. You can also see the GUID at the top of the output for show running-config. The next table lists the individual archive records. Each record appears in one row, with the following information: Archive Date/Time is the time stamp when the snapshot rule copied the volume configuration (and possibly the volume metadata) into the archive. Namespace:Volume identifies the managed volume for this file-history record. Snapshot Rule is the name of the snapshot rule that created the record. Config shows the size of the volume-configuration file. Metadata shows the size of the volume metadata. This is blank if the snapshot rules contents did not include metadata snapshots. Without this, you cannot make the show file-history virtual-service query against this file-history record. Summary shows the total disk space consumed by these records: total metadata space, total configuration space, and a grand total. You can use this as a guideline to determine the disk space you could reclaim with the clear file-history archive command.
Sample	bstnA(gbl)# show file-history archive fileRecordsMed contents end-date today shows all of the file-history records in the fileRecordsMed archive, from the first up to todays. See Figure 31.3 for sample output.
Related Commands	file-history archive show file-history archive clear file-history archive

Purpose	Managed volumes migrate files between back-end filers according to your policy settings. This can create a challenge for sites that use data-protection devices to back-up their data; if such a device backs up files from Filer A that later migrate to Filer B, you would create a metadata inconsistency in the managed volume if you restored the files back to Filer A. This command, along with some archiving commands, finds the filer location for any file on any date. You can use a snapshot rule to record a managed volumes configuration and metadata to a file-history archive, and later use the show file-history virtual-service command to query that archive. The output from this command shows the filer locations for a file or directory on any given date or date range.
Modes	(any)
Security Role(s)	crypto-officer, storage-engineer, backup-operator, or operator
Syntax	show file-history virtual-service fe-service fe-share time-frame {[file file-name [path dir-path]]} [options]   fe-service (1-1024 characters) is the name of an ARX service used by clients. This is a front-end service created by either the cifs or nfs commands. You can use the show virtual path-history command to find the services that existed on an earlier date, and the paths from those services to your filer shares; service-to-filer mappings may change over time. This can also be the VIP (from the virtual server command), a wins-name, or a wins-alias that existed at the time. fe-share (1-1024 characters) identifies a particular front-end share in the above service. This is created by either the export (gbl-cifs) or export (gbl-nfs) commands, which export storage from an ARX volume to ARX clients. As above, you may need to use the show virtual path-history command to find the shares that existed at the time you are querying. For NFS shares, this is case-sensitive (so that /vol/aShare is different from /vol/ASHARE), but this is not case-sensitive for CIFS shares. time-frame is a date or range of dates. The output shows the file or directory locations as of these dates. The options are: date {today | date} for file locations on a specific date. Enter the date in mm/dd/yyyy format. start-date date for file locations after the given date. end-date date for file locations before the given date. start-date date-1 end-date date-2 for file locations between two dates. count {days|weeks|quarters|months|years} before date for file locations for a time leading up to a date. The count (1-100) is the number of days, weeks, or other time-unit leading up to the date.
Syntax (Cont.)	[file [file-name] [path dir-path] is a required choice: you can choose a file name, a directory path, or both. file-name (1-1024 characters) specifies the name of one or more files. You can use special wildmat characters (such as * for zero or more characters, ? for any single character, [a-z] for any lowercase character, or [^0-9] for any character except a number) for a group of similar files. dir-path specifies the name of one or more directories. Use forward slashes (/) for this path, even for CIFS shares. As with the file-name, you can use special wildmat characters to specify a group of paths. If you omit this, the path is the root of the volume. options (all optional) are various search and output options that you can apply to any form of this command. If you use more than one of them, they must be in this order: recurse searches all directories in the volume or path. Without this option, the command only searches the root of the volume or path. case-sensitive makes the search case-sensitive, so that a search for *.DOC does not match the myfile.doc file anymore. By default, *.DOC matches myfile.doc, yourfile.Doc, herFile.DOC, or any other case combination for the .doc extension. verbose adds more detail to the output. For a search with only a path, this cause the output to show all of the files inside all of the matching directories. report prefix sends the output to a report file with the given prefix (1-255 characters). The report name is prefix_archive-name_mmddyyyyHHMM.rpt, where archive name is all or the name you provide in the next option, and the rest is the time the report was created. The exact report name appears at the CLI prompt after you type the command. archive archive-name identifies a particular file-history archive to be searched.
Guidelines	You can use this command to find file/directory locations at different times, typically to identify a backup tape for a lost file or directory. Before you can find any archived files or directories, you must use the file-history archive command to create an archive, and the location command to choose the archives home (either an external filer or an ARX volume). The archive gets its file-history records from one or more managed volumes. Each managed volume requires a snapshot rule to send its configuration and metadata to the archive filer. The snapshot rule contributes to a file-history archive through the following options: the rule must choose the volumes configuration and its metadata with the contents command, and must identify the file-history archive with the archive command. This command finds file locations from the time when a file-history record was copied to a file-history archive. To find the location of a file now, use the find command or the nsck ... report metadata-only command. To restore a file to a managed volume, copy it from its backup tape to a staging area on the back-end filer. The staging area is a directory that is outside any imported volume. You can mount both the staging area and the ARX service as a client, then copy the file(s) from the staging area to the volume. Alternatively, you can use the restore data command to automatically move the file(s) from the staging area to the volume.
Guidelines: Output	The output contains a table showing the parameters of your query, followed by some configuration information for the file-history archive and ARX service, and then a separate table for each archive record containing one of the chosen files. Query Parameters contains several fields to summarize your command-line options: Virtual Server, Export, Start date, End date, File Name, Path, Archive, Case Sensitive, Recursive, and Verbose. The next two fields identify the archive and its host ARX. These fields and the tables below only appear if the operation found at least one of the selected files or directories: Archive is the name of the file-history archive containing these records. Hosting Switch identifies this ARX by its hostname and by its GUID (also shown in the output of show running-config).
Guidelines: Output (Cont.)	The final series of tables contains the found files and/or directories. Each table shows a single matching file in one archive record: Archive Date/Time is the specific time for the current file-location record. Global Server is the global server that clients use to access the chosen files. WINS Name and WINS Aliases are aliases that clients may use to access the service. You can set these with the wins-name and wins-alias commands. Dynamic DNS Names are service names that are registered at the local dynamic-DNS servers (typically, Windows DCs). You can use the dynamic-dns command to add a new dynamic-DNS name for this service. VIP is the virtual-IP address used by clients to access this ARX service, set by the virtual server command. Namespace is the ARX namespace that held the file at the above time. Volume Path identifies the files volume. File Server(s) shows the single filer that held the file at the time, or the series of filers that may have held the directory. Each filer has three fields to describe the exact location of the file or directory: Shared Path is the path to the file or directory as seen from the network. This starts with the filers CIFS-share name or NFS-export name. Physical Path identifies the exact, file-system path to the file or directory. This path is the one that could be used to find a backup on an external data-protection device. The ARX accesses the filers CLI to get the correct physical-path information. The external-filer configuration on the ARX must have the proper filer-type and proxy-user (gbl-filer) for this access. Otherwise, this path is a best guess: for an NFS share, it uses the back-end-export path identified in the filer command; for a CIFS share, it sends a path query to the filer, requiring the namespaces proxy-user (gbl-ns) to be in the Administrators group. File Name is the name of the file or directory. Symlink Name appears instead of File Name if the file or directory is a symlink. This is the name of the symlink itself, not the symlinks target. You must retrieve the symlink from a backup tape to discover its target.
Samples	bstnA(gbl)# show file-history virtual-service ac1.medarch.org labs date 04/23/2009 file index.html   shows the location of a file named index.html in the ac1.medarch.org~labs share. The files location is as of a particular date, April 23. See Figure 31.4 for sample output.   bstnA# show file-history virtual-service ac1.medarch.org ARCHIVES date today path planA recurse   shows the location of all directories named planA in the ac1.medarch.org~ARCHIVES share. These directories are in the given locations as of today. See Figure 31.5 for sample output.
Related Commands	show virtual path-history file-history archive find restore data

Purpose	Service and volume configurations change over time, possibly making it difficult to make a proper file-tracking query about an earlier date. To make a query about file locations as of six-months ago, you must first know which ARX services existed at the time, and the paths from those client-visible services to the back-end filers and their file-systems. This is known as the path history of your ARX. From any mode, you can use the show virtual path-history command to list the front-end services, namespaces, and volumes from a given date or range of dates.
Modes	(any)
Security Role(s)	crypto-officer, storage-engineer, or backup-operator
Syntax: One Date	show virtual path-history date date [report prefix] [archive arch-name] [verbose]   date (mm/dd/yyyy, such as 11/12/2009, or today) is the exact date for the query. report prefix (optional, 1-1024 characters) sends the output to a report file. Each report has a unique name in the following format: prefix_archive_yyyymmddHHMM.rpt where the prefix is part of this option, the archive is all or a specific arch-name (see below), and yyyymmddHHMM is the time the report was created. For example, fRec_all_200903031200.rpt could be the name for one report with the fRec prefix. archive arch-name (optional, 1-64 characters) focuses on path history from a single file-history archive. verbose (optional) expands the output with additional details.
Syntax: A Range of Dates	show virtual path-history start-date s-date ... show virtual path-history end-date e-date ... show virtual path-history start-date s-date end-date e-date ...   start-date s-date (mm/dd/yyyy, such as 05/06/2009) is the beginning of the date range. If you provide no end-date (as shown in the first line above), the end date is today. end-date e-date (mm/dd/yyyy, such as 10/24/2009) is the end of the date range. If you provide no start-date (as shown in the second line above), the start is the date of the first snapshot in the file-history archive(s). ... represents the report, archive, and verbose options described above.
Syntax: Time Leading Up to a Date	show virtual path-history count {days|weeks|quarters|months|years} before e-date ...   count (1-100) is the number of days, weeks, or whatever time unit you choose next. days|weeks|quarters|months|years chooses the time unit. For example, 2 weeks, 5 days, or 6 months. before e-date (mm/dd/yyyy, such as 03/02/2009) is the end of the time period. ... represents the report, archive, and verbose options described above.
Guidelines	You can use this command to find ARX-service and storage configurations at different times, typically to prepare for using the show file-history virtual-service command. Before you can find any volume-configuration information, you must use the file-history archive command to create an archive, and the location command to choose the archives home (an ARX volume or an external filer). The archive gets its volume-configuration records from one or more managed volumes. Each managed volume requires a snapshot rule to send its volume configuration to the archive filer. The snapshot rule contributes to a file-history archive through the following options: the rule must choose the volumes configuration with the contents command, and must identify the file-history archive with the archive command. The output contains a table with the chosen date range followed by one table per matching file-history record. Query Parameters contains several fields to summarize your command-line options: Start date, End date, Archive, and Verbose.
	As of date is the heading for every file-history record in your date range. If more than one volume sends its records to this archive, you may see more than one record with the same date. The next series of fields describes the configuration for the archive and the service: Archive is the name of the file-history archive containing this record. Hosting Switch identifies this ARX by its hostname. Global Server is the global server that clients use to access the Volume, below. WINS Name and WINS Alias are aliases that clients may use to access the service. You can set these with the wins-name and wins-alias commands. Dynamic DNS Names are service names that are registered at the local dynamic-DNS servers (typically, Windows DCs). You can use the dynamic-dns command to add a new dynamic-DNS name for this service. VIP is the virtual-IP address used by clients to access this ARX service, set by the virtual server command. Namespace is the ARX namespace to which this record applies. Volume identifies the volume for this file-history record.
Guidelines (Cont.)	A table of the volumes shares appears next. This shows the back-end shares that were included in the volume when the record was created. Each row shows one share, with the following fields: Share is the ARX name of the share. Shared Path is the filers network-accessible path for the above share. The volume imported the filer share through this path, and used the shares storage for client files and directories when the record was created. -> Physical Path is the actual file-system path on the filer. An external data-recovery application uses file-system paths to identify the files that it has backed up. You can use this to identify the backup files that apply to the volume as of this particular date. The verbose option adds the filers IP address to the end of this output. The ARX accesses the filers CLI to get the correct physical-path information. The external-filer configuration on the ARX must have the proper filer-type and proxy-user (gbl-filer) for this access. Otherwise, this path is a best guess: for an NFS share, it uses the back-end-export path identified in the filer command; for a CIFS share, it sends a path query to the filer, requiring the namespaces proxy-user (gbl-ns) to be in the Administrators group.
	The final table shows the exports that were used by the ARXs clients when the record was taken. Each row contains one client-visible export of the above volume, with the following fields: Export is the exported name of the managed volume, or one of its sub paths. Relative Virtual Path is the managed-volume path that clients saw as the root of the above Export.
Sample	bstnA(gbl)# show virtual path-history end-date 06/05/2009 report pathsTilJune verbose Generating report: pathsTilJune_all_200901260629.rpt   shows all path histories up to June 5, including verbose details, and sends them to a report.
Related Commands	file-history archive show file-history virtual-service