You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/azacsnap-release-notes.md
+12-8Lines changed: 12 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
12
12
ms.workload: storage
13
13
ms.tgt_pltfrm: na
14
14
ms.topic: conceptual
15
-
ms.date: 05/27/2021
15
+
ms.date: 02/20/2022
16
16
ms.author: phjensen
17
17
---
18
18
@@ -22,14 +22,20 @@ This page lists major changes made to AzAcSnap to provide new functionality or r
22
22
23
23
## Feb-2022
24
24
25
+
### AzAcSnap v5.1 Preview (Build: 20220220.55340)
26
+
27
+
AzAcSnap v5.1 Preview (Build: 20220220.55340) has been released with the following fixes and improvements:
28
+
29
+
- Resolved failure in matching `--dbsid` command line option with `sid` entry in the JSON configuration file for Oracle databases when using the `-c restore` command.
30
+
31
+
Download the [latest release of the Preview installer](https://aka.ms/azacsnap-preview-installer) and read about the new features and how to use the [AzAcSnap Preview](azacsnap-preview.md).
32
+
25
33
### AzAcSnap v5.1 Preview (Build: 20220203.77807)
26
34
27
35
AzAcSnap v5.1 Preview (Build: 20220203.77807) has been released with the following fixes and improvements:
28
36
29
37
- Minor update to resolve STDOUT buffer limitations. Now the list of Oracle table files put into archive-mode is sent to an external file rather than output in the main AzAcSnap log file. The external file is in the same location and basename as the log file, but with a ".protected-tables" extension (output filename detailed in the AzAcSnap log file). It is overwritten each time `azacsnap` runs.
30
38
31
-
For details on the preview features and how to use them go to [AzAcSnap Preview](azacsnap-preview.md).
32
-
33
39
## Jan-2022
34
40
35
41
### AzAcSnap v5.1 Preview (Build: 20220125.85030)
@@ -41,16 +47,14 @@ AzAcSnap v5.1 Preview (Build: 20220125.85030) has been released with the followi
41
47
- Azure Managed Disk
42
48
- RunBefore and RunAfter capability
43
49
44
-
For details on the preview features and how to use them go to [AzAcSnap Preview](azacsnap-preview.md).
45
-
46
50
## Aug-2021
47
51
48
52
### AzAcSnap v5.0.2 (Build: 20210827.19086) - Patch update to v5.0.1
49
53
50
54
AzAcSnap v5.0.2 (Build: 20210827.19086) is provided as a patch update to the v5.0 branch with the following fixes and improvements:
51
55
52
-
- Ignore `ssh` 255 exit codes. In some cases the `ssh` command, which is used to communicate with storage on Azure Large Instance, would emit an exit code of 255 when there were no errors or execution failures (refer `man ssh` "EXIT STATUS") - subsequently AzAcSnap would trap this as a failure and abort. With this update additional verification is done to validate correct execution, this includes parsing `ssh` STDOUT and STDERR for errors in addition to traditional exit code checks.
53
-
- Fix the installer's check for the location of the hdbuserstore. The installer would check for the existence of an incorrect source directory for the hdbuserstore for the user running the install - this is fixed to check for `~/.hdb`. This is applicable to systems (for example, Azure Large Instance) where the hdbuserstore was pre-configured for the `root` user before installing `azacsnap`.
56
+
- Ignore `ssh` 255 exit codes. In some cases the `ssh` command, which is used to communicate with storage on Azure Large Instance, would emit an exit code of 255 when there were no errors or execution failures (refer `man ssh` "EXIT STATUS") - then AzAcSnap would trap this exit code as a failure and abort. With this update extra verification is done to validate correct execution, this includes parsing `ssh` STDOUT and STDERR for errors in addition to traditional exit code checks.
57
+
- Fix the installer's check for the location of the hdbuserstore. The installer would check for the existence of an incorrect source directory for the hdbuserstore for the user running the install - this is fixed to check for `~/.hdb`. This fix is applicable to systems (for example, Azure Large Instance) where the hdbuserstore was pre-configured for the `root` user before installing `azacsnap`.
54
58
- Installer now shows the version it will install/extract (if the installer is run without any arguments).
55
59
56
60
Download the [latest release](https://aka.ms/azacsnapinstaller) of the installer and review how to [get started](azacsnap-get-started.md).
@@ -61,7 +65,7 @@ Download the [latest release](https://aka.ms/azacsnapinstaller) of the installer
61
65
62
66
AzAcSnap v5.0.1 (Build: 20210524.14837) is provided as a patch update to the v5.0 branch with the following fixes and improvements:
63
67
64
-
- Improved exit code handling. In some cases an exit code of 0 (zero) was emitted, even when there was an execution failure and it should have been non-zero. Exit codes should now only be zero on successfully running `azacsnap` to completion and non-zero in case of any failure.
68
+
- Improved exit code handling. In some cases AzAcSnap would emit an exit code of 0 (zero), even after an execution failure when the exit code should have been non-zero. Exit codes should now only be zero on successfully running `azacsnap` to completion and non-zero if there is any failure.
65
69
- AzAcSnap's internal error handling has been extended to capture and emit the exit code of the external commands run by AzAcSnap.
0 commit comments